Mail Index

• Thread Index

• Compile error of latest hotfix release of btrfs
  • From: Tarkan Erimer
• Re: Compile error of latest hotfix release of btrfs
  • From: yanhai zhu
• [PATCH]several insignificant cleanups
  • From: yanhai zhu
• Re: [PATCH]several insignificant cleanups
  • From: yanhai zhu
• Re: Compile error of latest hotfix release of btrfs
  • From: Tarkan Erimer
• Re: Compile error of latest hotfix release of btrfs
  • From: yanhai zhu
• [PATCH] Fix call to blkdev_issue_discard
  • From: Diego Calleja
• Re: File System Performance results
  • From: Steven Pratt
• Re: File System Performance results
  • From: Chris Mason
• Re: Compile error of latest hotfix release of btrfs
  • From: Avi Kivity
• Re: Compressed Filesystem
  • From: Chris Samuel
• Btrfs Conf call
  • From: Chris Mason
• [PATCH] Add a missing return pointer check
  • From: yanhai zhu
• Systemtap script
  • From: Josef Bacik
• Checksum and transform layering
  • From: Gregory Maxwell
• Re: Checksum and transform layering
  • From: Claudio Martins
• [PATCH] Check kthread_should_stop() before schedule() in worker_loop
  • From: yanhai zhu
• Re: Checksum and transform layering
  • From: Gregory Maxwell
• Re: Checksum and transform layering
  • From: Xavier Nicollet
• Re: Checksum and transform layering
  • From: Gregory Maxwell
• Re: Checksum and transform layering
  • From: Gregory Maxwell
• Re: Checksum and transform layering
  • From: Florian Weimer
• Re: Checksum and transform layering
  • From: Tracy Reed
• New compression fixes pushed out
  • From: Chris Mason
• oops: csum failed ino
  • From: Martin Bürger
• Re: oops: csum failed ino
  • From: Chris Mason
• Re: oops: csum failed ino
  • From: Martin Bürger
• [PATCH] Fix csum error for compressed data
  • From: Yan Zheng
• Re: [PATCH] Fix csum error for compressed data
  • From: Chris Mason
• Re: File System Performance results
  • From: Chris Mason
• Re: [PATCH] Fix csum error for compressed data
  • From: Martin Bürger
• Re: [PATCH] Fix csum error for compressed data
  • From: Chris Mason
• Re: [PATCH] Fix csum error for compressed data
  • From: Martin Bürger
• Re: [PATCH] Fix csum error for compressed data
  • From: Yan Zheng
• [PATCH 1/2] mount ro and remount support
  • From: Yan Zheng
• [PATCH 2/2] Seed device support
  • From: Yan Zheng
• [PATCH] update btrfs-progs for seed device support
  • From: Yan Zheng
• Re: [PATCH] Fix csum error for compressed data
  • From: Martin Bürger
• [PATCH] batch extent inserts/updates/deletions on the extent root
  • From: Josef Bacik
• Re: [PATCH] Fix csum error for compressed data
  • From: Chris Mason
• [PATCH] Fix race in btrfs_mark_extent_written
  • From: Yan Zheng
• Kernel oops when running bonnie++ on btrfs
  • From: Lee Trager
• Regression/functional test suite?
  • From: Tracy Reed
• Re: Kernel oops when running bonnie++ on btrfs
  • From: Josef Bacik
• Re: Regression/functional test suite?
  • From: Eric Whitney
• Re: Kernel oops when running bonnie++ on btrfs
  • From: Lee Trager
• Re: [PATCH] btrfs: allow clone of an arbitrary file range
  • From: Chris Mason
• Re: Kernel oops when running bonnie++ on btrfs
  • From: Martin Bürger
• Re: Kernel oops when running bonnie++ on btrfs
  • From: Chris Mason
• Re: Kernel oops when running bonnie++ on btrfs
  • From: Martin Bürger
• Re: Kernel oops when running bonnie++ on btrfs
  • From: Josef Bacik
• Re: [PATCH] btrfs: allow clone of an arbitrary file range
  • From: Sage Weil
• Re: Kernel oops when running bonnie++ on btrfs
  • From: Lee Trager
• [PATCH] fix free space leak
  • From: Josef Bacik
• [PATCH] btrfsck open_ctree sanity check
  • From: hyl
• Re: [PATCH] fix free space leak
  • From: Mitch Harder (aka DontPanic)
• Re: [PATCH] fix free space leak
  • From: Lee Trager
• [PATH]Some fix for batching extent insert.
  • From: Liu Hui
• [DEBUG PATCH] for anybody who gets a panic due to ENOSPC
  • From: Josef Bacik
• Re: [DEBUG PATCH] for anybody who gets a panic due to ENOSPC
  • From: Lee Trager
• Re: [DEBUG PATCH] for anybody who gets a panic due to ENOSPC
  • From: Mitch Harder (aka DontPanic)
• Re: [DEBUG PATCH] for anybody who gets a panic due to ENOSPC
  • From: Mitch Harder (aka DontPanic)
• Re: [PATH]Some fix for batching extent insert.
  • From: Chris Mason
• Re: [PATH]Some fix for batching extent insert.
  • From: Chris Mason
• Re: [PATH]Some fix for batching extent insert.
  • From: yanhai zhu
• Re: [PATH]Some fix for batching extent insert.
  • From: Chris Mason
• Re: [DEBUG PATCH] for anybody who gets a panic due to ENOSPC
  • From: Josef Bacik
• New disk format pushed out to btrfs-unstable
  • From: Chris Mason
• Re: New disk format pushed out to btrfs-unstable
  • From: Chris Mason
• Btrfs Conf call
  • From: Chris Mason
• [PATCH] Btrfs image tool
  • From: Yan Zheng
• Re: [DEBUG PATCH] for anybody who gets a panic due to ENOSPC
  • From: Lee Trager
• Re: [DEBUG PATCH] for anybody who gets a panic due to ENOSPC
  • From: Josef Bacik
• [PATCH] fix free space accounting when unpinning extents
  • From: Josef Bacik
• Re: [PATCH] fix free space accounting when unpinning extents
  • From: Chris Mason
• btrfs thinks its full
  • From: Lee Trager
• Re: btrfs thinks its full
  • From: Josef Bacik
• [PATCH] Drop dirty roots created by log replay immediately when mount -o ro
  • From: Yan Zheng
• Re: btrfs thinks its full
  • From: Lee Trager
• [PATH]Fix cow semantic in run_delalloc_nocow()
  • From: Liu Hui
• Re: btrfs thinks its full
  • From: Josef Bacik
• Unstable trees updated to 2.6.28-rc5
  • From: Chris Mason
• Btrfs trees for linux-next
  • From: Chris Mason
• Re: [PATH]Fix cow semantic in run_delalloc_nocow()
  • From: Yan Zheng
• Re: [PATH]Fix cow semantic in run_delalloc_nocow()
  • From: Liu Hui
• "possible circular locking dependency detected"
  • From: Diego Calleja
• Re: "possible circular locking dependency detected"
  • From: Josef Bacik
• Re: [PATH]Fix cow semantic in run_delalloc_nocow()
  • From: Chris Mason
• [PATCH] updated fix for lockdep warnings with alloc_mutex and pinned_mutex
  • From: Josef Bacik
• [PATCH] btrfs: make things static and include the right headers
  • From: Christoph Hellwig
• [PATCH] btrfs: sparse lock verification annotations for wait_on_state
  • From: Christoph Hellwig
• [PATCH] btrfs: fix shadowed variable declarations
  • From: Christoph Hellwig
• [PATCH] btrfs: clean up btrfs_ioctl a little bit
  • From: Christoph Hellwig
• [PATCH] btrfs: pass void __user * to btrfs_ioctl_clone_range
  • From: Christoph Hellwig
• [PATCH] add support for compat flags to btrfs
  • From: Josef Bacik
• [PATCH] btrfs-progs: add support for compat flags
  • From: Josef Bacik
• [PATCH] btrfs: corret fmode_t annotations
  • From: Christoph Hellwig
• [PATCH] fix panic on error during mount
  • From: Josef Bacik
• WARNING: at fs/btrfs/extent_io.c:3546 write_extent_buffer()
  • From: Alexander Beregalov
• Re: WARNING: at fs/btrfs/extent_io.c:3546 write_extent_buffer()
  • From: Chris Mason
• Re: WARNING: at fs/btrfs/extent_io.c:3546 write_extent_buffer()
  • From: Alexander Beregalov
• Re: [PATCH] Btrfs image tool
  • From: Alexander Beregalov
• [PATCH] btrfs: fix printk format warnings
  • From: Alexander Beregalov
• Re: [PATCH] btrfs: fix printk format warnings
  • From: Miguel Sousa Filipe
• Re: [PATCH]Fix cow semantic in run_delalloc_nocow()
  • From: Liu Hui
• Re: [PATCH]Fix cow semantic in run_delalloc_nocow()
  • From: Chris Mason
• [PATCH] add support for multiple csum algorithms
  • From: Josef Bacik
• [PATCH] btrfs-progs: support for different csum algorithims
  • From: Josef Bacik
• [PATCH] btrfs: remove unneeded btrfs_start_delalloc_inodes call
  • From: Sage Weil
• [PATCH] btrfs: remove unneeded total_trans
  • From: Sage Weil
• Re: [PATCH] Btrfs image tool
  • From: yanhai zhu
• compile error on Ubuntu 8.10
  • From: Gabor MICSKO
• Seed device questions
  • From: Jonas Bonn
• Re: Seed device questions
  • From: Yan Zheng
• Re: compile error on Ubuntu 8.10
  • From: Chris Samuel
• Re: compile error on Ubuntu 8.10
  • From: Gabor MICSKO
• Supported Kernels
  • From: Lee Trager
• Re: Partial allocation
  • From: Oliver Mattos
• Weak Allocation
  • From: Oliver Mattos
• New disk format pushed out
  • From: Chris Mason
• Partial Allocation
  • From: Oliver Mattos
• Re: Partial Allocation
  • From: Chris Mason
• No btrfs conf call today
  • From: Chris Mason
• Re: Partial Allocation
  • From: Josef Bacik
• [PATCH]Fix for map_private_extent_buffer to handle extent which is not page alignment
  • From: Liu Hui
• Re: [PATCH]Fix for map_private_extent_buffer to handle extent which is not page alignment
  • From: Liu Hui
• Re: [PATCH]Fix for map_private_extent_buffer to handle extent which is not page alignment
  • From: Liu Hui
• PROBLEM: oops when running fsstress against compressed btrfs filesystem
  • From: Eric Whitney
• PROBLEM: oops on attempt to mount badly formed filesystem
  • From: Eric Whitney
• Re: PROBLEM: oops on attempt to mount badly formed filesystem
  • From: Niraj kumar
• mailing december 2008
  • From: mailing
• btrfs: Problem with multi device mounting
  • From: Niraj kumar
• Re: btrfs: Problem with multi device mounting
  • From: Yan Zheng
• Re: btrfs: Problem with multi device mounting
  • From: Niraj Kumar
• No space left on device
  • From: Gabor MICSKO
• Re: No space left on device
  • From: dcg
• New disk format pushed out
  • From: Chris Mason
• Re: Checksum and transform layering
  • From: Chris Mason
• Re: New disk format pushed out
  • From: Gabor MICSKO
• Re: New disk format pushed out
  • From: Chris Mason
• Re: New disk format pushed out
  • From: Chris Mason
• Selective Compression/Encryption
  • From: Lee Trager
• Re: Selective Compression/Encryption
  • From: Miguel Figueiredo Mascarenhas Sousa Filipe
• Re: Selective Compression/Encryption
  • From: Chris Mason
• btrfs and hotplug, auto-assembly, auto-setup, ...
  • From: Kay Sievers
• Re: Selective Compression/Encryption
  • From: Lee Trager
• Re: Selective Compression/Encryption
  • From: Lee Trager
• Re: Selective Compression/Encryption
  • From: Joshua J. Berry
• Re: Selective Compression/Encryption
  • From: jim owens
• Re: Selective Compression/Encryption
  • From: Miguel Figueiredo Mascarenhas Sousa Filipe
• Data De-duplication
  • From: Oliver Mattos
• Re: Selective Compression/Encryption
  • From: Diego Calleja
• Re: Selective Compression/Encryption
  • From: jim owens
• Re: Selective Compression/Encryption
  • From: calin
• RE: Selective Compression/Encryption
  • From: Mattos, Oliver
• Re: Selective Compression/Encryption
  • From: Jeremy Sanders
• Re: Data De-duplication
  • From: Miguel Figueiredo Mascarenhas Sousa Filipe
• Re: Selective Compression/Encryption
  • From: Miguel Figueiredo Mascarenhas Sousa Filipe
• Re: Selective Compression/Encryption
  • From: Miguel Figueiredo Mascarenhas Sousa Filipe
• Re: Data De-duplication
  • From: Chris Mason
• Re: Data De-duplication
  • From: seth huang
• Re: Selective Compression/Encryption
  • From: Chris Mason
• Re: Selective Compression/Encryption
  • From: Chris Mason
• btrfs with selinux
  • From: jim owens
• Re: Data De-duplication
  • From: Oliver Mattos
• Re: Selective Compression/Encryption
  • From: Christoph Hellwig
• Re: Selective Compression/Encryption
  • From: Linda Knippers
• Re: Selective Compression/Encryption
  • From: Joshua J. Berry
• Re: Data De-duplication
  • From: Oliver Mattos
• Re: Data De-duplication
  • From: Ray Van Dolson
• Re: Data De-duplication
  • From: Oliver Mattos
• Re: Data De-duplication
  • From: Tracy Reed
• Re: Data De-duplication
  • From: Oliver Mattos
• Re: Data De-duplication
  • From: Ray Van Dolson
• Re: Data De-duplication
  • From: Oliver Mattos
• Re: btrfs and hotplug, auto-assembly, auto-setup, ...
  • From: Chris Mason
• Re: New disk format pushed out
  • From: Chris Mason
• Re: btrfs and hotplug, auto-assembly, auto-setup, ...
  • From: Kay Sievers
• Re: Btrfs trees for linux-next
  • From: Chris Mason
• Re: Btrfs trees for linux-next
  • From: Stephen Rothwell
• Re: Data De-duplication
  • From: Oliver Mattos
• Re: Data De-duplication
  • From: Ray Van Dolson
• Re: Btrfs trees for linux-next
  • From: Andrew Morton
• Re: Btrfs trees for linux-next
  • From: Stephen Rothwell
• Re: Data De-duplication
  • From: Oliver Mattos
• Auto-sparseifying
  • From: Oliver Mattos
• Re: btrfs and hotplug, auto-assembly, auto-setup, ...
  • From: Chris Mason
• Re: Auto-sparseifying
  • From: jim owens
• Re: Btrfs trees for linux-next
  • From: Chris Mason
• Re: Auto-sparseifying
  • From: Chris Mason
• Re: Data De-duplication
  • From: Chris Mason
• [PATCH] btrfs: mnt_drop_write in ioctl_trans_end
  • From: Sage Weil
• Re: Selective Compression/Encryption
  • From: Lee Trager
• Re: Selective Compression/Encryption
  • From: Chris Mason
• Re: PROBLEM: oops when running fsstress against compressed btrfs filesystem
  • From: Chris Mason
• Re: PROBLEM: oops when running fsstress against compressed btrfs filesystem
  • From: Chris Mason
• [PATCH] fix wrong value returned from btrfs_listxattr when buffer is too small
  • From: Yehuda Sadeh Weinraub
• daily snapshots ?
  • From: devzero
• Re: Data De-duplication
  • From: Chris Samuel
• Re: daily snapshots ?
  • From: devzero
• Re: Data De-duplication
  • From: Omen Wild
• Re: PROBLEM: oops when running fsstress against compressed btrfs filesystem
  • From: Chris Mason
• sync-related lockdep warnings
  • From: Sage Weil
• Re: sync-related lockdep warnings
  • From: Chris Mason
• Btrfs standalone tree regenerated
  • From: Chris Mason
• Re: sync-related lockdep warnings
  • From: Chris Mason
• Re: Btrfs trees for linux-next
  • From: Andreas Dilger
• Re: Compressed Filesystem
  • From: devzero
• Stable btrfs available for kernel 2.6.28?
  • From: Joe Peterson
• Re: Btrfs trees for linux-next
  • From: Kay Sievers
• Re: Compressed Filesystem
  • From: Lee Trager
• Re: Compressed Filesystem
  • From: devzero
• Re: Stable btrfs available for kernel 2.6.28?
  • From: Chris Mason
• Re: Btrfs trees for linux-next
  • From: Chris Mason
• Re: Btrfs trees for linux-next
  • From: Kay Sievers
• Re: Compressed Filesystem
  • From: Lee Trager
• Re: Compressed Filesystem
  • From: Chris Mason
• More performance results
  • From: Steven Pratt
• Re: Compressed Filesystem
  • From: Lee Trager
• Re: Compressed Filesystem
  • From: devzero
• weird bash autocomplete issue
  • From: Roland
• Re: Compressed Filesystem
  • From: Roland
• Re: weird bash autocomplete issue
  • From: Kay Sievers
• Re: weird bash autocomplete issue
  • From: devzero
• kernel BUG: kernel bug caught at 55% mark of portage cache update
  • From: Thomas Harning
• Re: weird bash autocomplete issue
  • From: Kay Sievers
• Re: weird bash autocomplete issue
  • From: Kay Sievers
• Re: weird bash autocomplete issue
  • From: Roland
• Notes on support for multiple devices for a single filesystem
  • From: Christoph Hellwig
• Re: weird bash autocomplete issue
  • From: Kay Sievers
• Re: weird bash autocomplete issue
  • From: Chris Mason
• Btrfs conference call
  • From: Chris Mason
• Re: weird bash autocomplete issue
  • From: devzero
• Re: weird bash autocomplete issue
  • From: Kay Sievers
• Re: Btrfs conference call
  • From: Gabor MICSKO
• Re: Notes on support for multiple devices for a single filesystem
  • From: Kay Sievers
• Re: Notes on support for multiple devices for a single filesystem
  • From: Chris Mason
• Re: Notes on support for multiple devices for a single filesystem
  • From: Christoph Hellwig
• Re: [PATCH] fix wrong value returned from btrfs_listxattr when buffer is too small
  • From: Chris Mason
• Re: Notes on support for multiple devices for a single filesystem
  • From: Kay Sievers
• Re: sync-related lockdep warnings
  • From: Chris Mason
• compilation problem on last unstable
  • From: Michele Petrazzo
• Re: compilation problem on last unstable
  • From: Lee Trager
• Re: Notes on support for multiple devices for a single filesystem
  • From: Andrew Morton
• Re: Notes on support for multiple devices for a single filesystem
  • From: Chris Mason
• Re: Notes on support for multiple devices for a single filesystem
  • From: Kay Sievers
• Re: Notes on support for multiple devices for a single filesystem
  • From: Andreas Dilger
• Re: Notes on support for multiple devices for a single filesystem
  • From: Chris Mason
• Re: Notes on support for multiple devices for a single filesystem
  • From: Jeff Garzik
• Re: Notes on support for multiple devices for a single filesystem
  • From: Jeff Garzik
• Re: Notes on support for multiple devices for a single filesystem
  • From: Chris Mason
• Re: Notes on support for multiple devices for a single filesystem
  • From: Andreas Dilger
• Re: weird bash autocomplete issue
  • From: Kay Sievers
• Re: Notes on support for multiple devices for a single filesystem
  • From: Dave Kleikamp
• Re: weird bash autocomplete issue
  • From: Chris Mason
• BUG at fs/buffer.c:2925! when mounted USB-disk is disconnected
  • From: Kay Sievers
• Re: BUG at fs/buffer.c:2925! when mounted USB-disk is disconnected
  • From: Chris Mason
• Re: Compressed Filesystem
  • From: Chris Mason
• Re: Notes on support for multiple devices for a single filesystem
  • From: Bryan Henderson
• inode data not getting included in commits?
  • From: Sage Weil
• Re: [PATCH] fix wrong value returned from btrfs_listxattr when buffer is too small
  • From: Sage Weil
• Re: weird bash autocomplete issue
  • From: devzero
• Re: inode data not getting included in commits?
  • From: Yan Zheng
• Re: weird bash autocomplete issue
  • From: Kay Sievers
• Re: [PATCH] fix wrong value returned from btrfs_listxattr when buffer is too small
  • From: Chris Mason
• Re: inode data not getting included in commits?
  • From: Sage Weil
• Re: weird bash autocomplete issue
  • From: devzero
• Way to contribute?
  • From: Spyros Lyberis
• Re: inode data not getting included in commits?
  • From: Chris Mason
• Re: Way to contribute?
  • From: Chris Mason
• Re: kernel BUG: kernel bug caught at 55% mark of portage cache update
  • From: Chris Mason
• Re: kernel BUG: kernel bug caught at 55% mark of portage cache update
  • From: Chris Mason
• Re: kernel BUG: kernel bug caught at 55% mark of portage cache update
  • From: Julian Andres Klode
• Re: inode data not getting included in commits?
  • From: Sage Weil
• Re: Notes on support for multiple devices for a single filesystem
  • From: Bryan Henderson
• Re: inode data not getting included in commits?
  • From: Chris Mason
• Re: Notes on support for multiple devices for a single filesystem
  • From: Chris Mason
• Re: inode data not getting included in commits?
  • From: Sage Weil
• [PATCH 1/1] btrfs fiemap support
  • From: Yehuda Sadeh Weinraub
• [PATCH 1/1] ioctl to fetch csums of file extents
  • From: Yehuda Sadeh Weinraub
• Re: inode data not getting included in commits?
  • From: Chris Mason
• btrfs filesystem freeze
  • From: devzero
• Re: btrfs filesystem freeze
  • From: Yan Zheng
• Re: btrfs filesystem freeze
  • From: devzero
• Re: btrfs filesystem freeze
  • From: Yan Zheng
• Re: Notes on support for multiple devices for a single filesystem
  • From: Liu Hui
• Re: btrfs filesystem freeze
  • From: devzero
• [PATCH]Fix typo in clear_state_cb
  • From: Liu Hui
• [PATCH]Fix compile error in quick-test.c of btrfs progs
  • From: Liu Hui
• [PATCH] Btrfs: fix build errors of extent_io.c
  • From: Ryusuke Konishi
• multiple device usage
  • From: devzero
• Re: multiple device usage
  • From: Yan Zheng
• Re: multiple device usage
  • From: Chris Samuel
• Re: multiple device usage
  • From: Roland
• Re: multiple device usage
  • From: yanhai zhu
• [PATCH] Btrfs: check return of kmalloc in btrfs_control_ioctl
  • From: Shen Feng
• [PATCH] Btrfs: do not call kfree if kmalloc failed in btrfs_sysfs_add_super
  • From: Shen Feng
• [PATCH] Btrfs: fix a memory leak in btrfs_get_sb
  • From: Shen Feng
• Re: multiple device usage
  • From: Stephan von Krawczynski
• Re: multiple device usage
  • From: Chris Samuel
• Re: multiple device usage
  • From: Roland
• Re: multiple device usage
  • From: Yan Zheng
• Re: multiple device usage
  • From: Yan Zheng
• Re: multiple device usage
  • From: Chris Samuel
• Re: multiple device usage
  • From: Yan Zheng
• [PATCH]Btrfs:Fix discard semantic
  • From: Liu Hui
• [PATCH] always check btrfs_alloc_path() failure
  • From: Diego Calleja
• [PATCH] __must_check btrfs_alloc_path()
  • From: Diego Calleja
• A bug with multiple devices?
  • From: Shen Feng
• Re: A bug with multiple devices?
  • From: Chris Samuel
• Re: A bug with multiple devices?
  • From: Chris Samuel
• Re: A bug with multiple devices?
  • From: Yan Zheng
• Re: A bug with multiple devices?
  • From: Chris Samuel
• Re: A bug with multiple devices?
  • From: Chris Samuel
• Re: A bug with multiple devices?
  • From: Chris Mason
• Re: multiple device usage
  • From: Chris Mason
• Re: multiple device usage
  • From: Chris Mason
• Re: A bug with multiple devices?
  • From: Shen Feng
• Re: A bug with multiple devices?
  • From: Liu Hui
• Re: A bug with multiple devices?
  • From: Shen Feng
• Re: A bug with multiple devices?
  • From: Shen Feng
• [PATCH] Btrfs-progs: btrfs file system size should be bigger then 256m
  • From: Shen Feng
• [PATCH] Btrfs-progs: update BUG_ON and WARN_ON
  • From: Shen Feng
• Re: [PATCH] Btrfs-progs: btrfs file system size should be bigger then 256m
  • From: Lee Trager
• Re: [PATCH] Btrfs-progs: btrfs file system size should be bigger then 256m
  • From: Shen Feng
• Btrfs for mainline
  • From: Chris Mason
• Re: [PATCH] Btrfs-progs: btrfs file system size should be bigger then 256m
  • From: Zach Brown
• Re: Btrfs for mainline
  • From: Andrew Morton
• Re: Btrfs for mainline
  • From: Chris Mason
• Re: A bug with multiple devices?
  • From: Chris Samuel
• Re: multiple device usage
  • From: Chris Samuel