Linux BTRFS

• Thread Index

• Re: csum failed : d-raid0, m-raid1
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• [GIT PULL] Btrfs
  • From: Chris Mason <clm@xxxxxx>
• Re: [PATCH 3/4] btrfs: sysfs: introduce helper for syncing bits with sysfs files
  • From: David Sterba <dsterba@xxxxxxx>
• Re: csum failed : d-raid0, m-raid1
  • From: John Smith <lenovomi@xxxxxxxxx>
• csum failed : d-raid0, m-raid1
  • From: John Smith <lenovomi@xxxxxxxxx>
• Re: [PATCH 3/4] btrfs: sysfs: introduce helper for syncing bits with sysfs files
  • From: Chris Mason <clm@xxxxxx>
• Re: [PATCH 3/4] btrfs: sysfs: introduce helper for syncing bits with sysfs files
  • From: David Sterba <dsterba@xxxxxxx>
• Re: [PATCH 3/4] btrfs: sysfs: introduce helper for syncing bits with sysfs files
  • From: Filipe Manana <fdmanana@xxxxxxxxx>
• [PATCH 3/3] btrfs: drop null testing before destroy functions
  • From: Kinglong Mee <kinglongmee@xxxxxxxxx>
• [PATCH 2/3] btrfs: fix compile warning of uninitialized value
  • From: Kinglong Mee <kinglongmee@xxxxxxxxx>
• [PATCH 1/3] btrfs: fix memory leak of fs_info in block group cache
  • From: Kinglong Mee <kinglongmee@xxxxxxxxx>
• Re: [PATCH V10 00/12] Btrfs: Pre subpagesize-blocksize cleanups
  • From: David Sterba <dsterba@xxxxxxx>
• Re: RAID1 disk upgrade method
  • From: "Austin S. Hemmelgarn" <ahferroin7@xxxxxxxxx>
• [PATCH v3 22/22] btrfs-progs: Cleanup old btrfs-convert
  • From: Qu Wenruo <quwenruo@xxxxxxxxxxxxxx>
• [PATCH v3 16/22] btrfs-progs: convert: Introduce function to migrate reserved ranges
  • From: Qu Wenruo <quwenruo@xxxxxxxxxxxxxx>
• [PATCH v3 00/22] Btrfs-convert rework to support separate chunk type
  • From: Qu Wenruo <quwenruo@xxxxxxxxxxxxxx>
• [PATCH v3 10/22] btrfs-progs: Introduce function to initialize csum tree
  • From: Qu Wenruo <quwenruo@xxxxxxxxxxxxxx>
• [PATCH v3 12/22] btrfs-progs: Introduce function to create convert data chunks
  • From: Qu Wenruo <quwenruo@xxxxxxxxxxxxxx>
• [PATCH v3 20/22] btrfs-progs: Convert: Add support for rollback new convert behavior
  • From: Qu Wenruo <quwenruo@xxxxxxxxxxxxxx>
• [PATCH v3 19/22] btrfs-progs: Introduce do_convert_v2 function
  • From: Qu Wenruo <quwenruo@xxxxxxxxxxxxxx>
• [PATCH v3 06/22] btrfs-progs: Introduce function to setup temporary tree root
  • From: Qu Wenruo <quwenruo@xxxxxxxxxxxxxx>
• [PATCH v3 17/22] btrfs-progs: convert: Enhance record_file_blocks to handle reserved ranges
  • From: Qu Wenruo <quwenruo@xxxxxxxxxxxxxx>
• [PATCH v3 07/22] btrfs-progs: Introduce function to setup temporary chunk root
  • From: Qu Wenruo <quwenruo@xxxxxxxxxxxxxx>
• [PATCH v3 15/22] btrfs-progs: convert: Introduce new function to create converted image
  • From: Qu Wenruo <quwenruo@xxxxxxxxxxxxxx>
• [PATCH v3 18/22] btrfs-progs: convert: Introduce init_btrfs_v2 function.
  • From: Qu Wenruo <quwenruo@xxxxxxxxxxxxxx>
• [PATCH v3 21/22] btrfs-progs: convert: Strictly avoid meta or system chunk allocation
  • From: Qu Wenruo <quwenruo@xxxxxxxxxxxxxx>
• [PATCH v3 09/22] btrfs-progs: Introduce function to initialize fs tree
  • From: Qu Wenruo <quwenruo@xxxxxxxxxxxxxx>
• [PATCH v3 14/22] btrfs-progs: extent-tree: Enhance btrfs_record_file_extent
  • From: Qu Wenruo <quwenruo@xxxxxxxxxxxxxx>
• [PATCH v3 01/22] btrfs-progs: convert: Introduce functions to read used space
  • From: Qu Wenruo <quwenruo@xxxxxxxxxxxxxx>
• [PATCH v3 08/22] btrfs-progs: Introduce function to initialize device tree
  • From: Qu Wenruo <quwenruo@xxxxxxxxxxxxxx>
• [PATCH v3 03/22] btrfs-progs: convert: Introduce function to calculate the available space
  • From: Qu Wenruo <quwenruo@xxxxxxxxxxxxxx>
• [PATCH v3 13/22] btrfs-progs: extent-tree: Introduce function to find the first overlap extent.
  • From: Qu Wenruo <quwenruo@xxxxxxxxxxxxxx>
• [PATCH v3 02/22] btrfs-progs: convert: Introduce new function to remove reserved ranges
  • From: Qu Wenruo <quwenruo@xxxxxxxxxxxxxx>
• [PATCH v3 11/22] btrfs-progs: Introduce function to setup temporary extent tree
  • From: Qu Wenruo <quwenruo@xxxxxxxxxxxxxx>
• [PATCH v3 04/22] btrfs-progs: utils: Introduce new function for convert
  • From: Qu Wenruo <quwenruo@xxxxxxxxxxxxxx>
• [PATCH v3 05/22] btrfs-progs: Introduce function to setup temporary superblock
  • From: Qu Wenruo <quwenruo@xxxxxxxxxxxxxx>
• Re: [PATCH V7 0/3][PULL REQUEST] Unify 'norecovery' bahavior with other filesystems
  • From: Qu Wenruo <quwenruo@xxxxxxxxxxxxxx>
• Re: btrfs subvolume list -o does not behave as expected
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: RAID1 disk upgrade method
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: RAID1 disk upgrade method
  • From: Duncan <1i5t5.duncan@xxxxxxx>
• [PATCH 2/2 v2] Btrfs: remove no longer used function extent_read_full_page_nolock()
  • From: fdmanana@xxxxxxxxxx
• Re: btrfs subvolume list -o does not behave as expected
  • From: "Daniel E. Shub" <daniel.e.shub@xxxxxxxxx>
• Re: RAID1 disk upgrade method
  • From: "Austin S. Hemmelgarn" <ahferroin7@xxxxxxxxx>
• Re: RAID1 disk upgrade method
  • From: Sean Greenslade <sean@xxxxxxxxxxxxxxxxxx>
• [v2] Re: btrfs: remove open-coded swap() in backref.c:__merge_refs
  • From: Dave Jones <dsj@xxxxxx>
• btrfs: remove open-coded swap() in backref.c:__merge_refs
  • From: Dave Jones <dsj@xxxxxx>
• Re: RAID1 disk upgrade method
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: RAID1 disk upgrade method
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: RAID1 disk upgrade method
  • From: "Austin S. Hemmelgarn" <ahferroin7@xxxxxxxxx>
• Re: RAID1 disk upgrade method
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: RAID1 disk upgrade method
  • From: "Austin S. Hemmelgarn" <ahferroin7@xxxxxxxxx>
• Re: RAID1 disk upgrade method
  • From: Sean Greenslade <sean@xxxxxxxxxxxxxxxxxx>
• Re: [PATCH] Add support for RENAME_{EXCHANGE,WHITEOUT}
  • From: Dan Fuhry <dan@xxxxxxxxx>
• Re: RAID1 disk upgrade method
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• [PATCH] Add support for RENAME_{EXCHANGE,WHITEOUT}
  • From: Dan Fuhry <dan@xxxxxxxxx>
• Re: RAID1 disk upgrade method
  • From: Sean Greenslade <sean@xxxxxxxxxxxxxxxxxx>
• Re: [PATCH 1/2] btrfs: reada: limit max works count
  • From: Chris Mason <clm@xxxxxx>
• Re: RAID1 disk upgrade method
  • From: "Austin S. Hemmelgarn" <ahferroin7@xxxxxxxxx>
• Re: btrfs-progs 4.4 re-balance of RAID6 is very slow / limited to one cpu core?
  • From: "Austin S. Hemmelgarn" <ahferroin7@xxxxxxxxx>
• Re: [PATCH] btrfs-progs: doc: fix size suffix in mkfs.btrfs
  • From: David Sterba <dsterba@xxxxxxx>
• Re: [PATCH] btrfs-progs: doc: fix typo of some documents
  • From: David Sterba <dsterba@xxxxxxx>
• [PATCH] btrfs-progs: doc: fix size suffix in mkfs.btrfs
  • From: Tsutomu Itoh <t-itoh@xxxxxxxxxxxxxx>
• [PATCH] btrfs-progs: doc: fix typo of some documents
  • From: Tsutomu Itoh <t-itoh@xxxxxxxxxxxxxx>
• RE: [PATCH 1/2] btrfs: reada: limit max works count
  • From: Zhao Lei <zhaolei@xxxxxxxxxxxxxx>
• [PATCH] btrfs: reada: Ignore creating reada_extent for non-exist device
  • From: Zhao Lei <zhaolei@xxxxxxxxxxxxxx>
• Re: RAID1 disk upgrade method
  • From: Sean Greenslade <sean@xxxxxxxxxxxxxxxxxx>
• Re: Progress indicator when (slowly) mounting a btrfs filesystem?
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: btrfs subvolume list -o does not behave as expected
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: RAID1 disk upgrade method
  • From: Sean Greenslade <sean@xxxxxxxxxxxxxxxxxx>
• Re: btrfs-progs 4.4 re-balance of RAID6 is very slow / limited to one cpu core?
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• btrfs subvolume list -o does not behave as expected
  • From: "Daniel E. Shub" <daniel.e.shub@xxxxxxxxx>
• Re: Progress indicator when (slowly) mounting a btrfs filesystem?
  • From: bbrendon@xxxxxxxxx
• Re: btrfs-progs 4.4 re-balance of RAID6 is very slow / limited to one cpu core?
  • From: bbrendon@xxxxxxxxx
• [PATCH 2/2] Btrfs: remove no longer used function extent_read_full_page_nolock()
  • From: fdmanana@xxxxxxxxxx
• [PATCH 1/2] Btrfs: fix page reading in extent_same ioctl leading to csum errors
  • From: fdmanana@xxxxxxxxxx
• Re: btrfs-progs 4.4 re-balance of RAID6 is very slow / limited to one cpu core?
  • From: "Austin S. Hemmelgarn" <ahferroin7@xxxxxxxxx>
• Progress indicator when (slowly) mounting a btrfs filesystem?
  • From: Christian Rohmann <crohmann@xxxxxxxxxxxxx>
• Re: [PATCH v2] btrfs: sysfs: check initialization state before updating features
  • From: Chris Mason <clm@xxxxxx>
• [PATCH 1/4] btrfs: tests: switch to GFP_KERNEL
  • From: David Sterba <dsterba@xxxxxxxx>
• [PATCH 4/4] btrfs: add free space tree to the cow-only list
  • From: David Sterba <dsterba@xxxxxxxx>
• [PATCH 3/4] btrfs: add free space tree to lockdep classes
  • From: David Sterba <dsterba@xxxxxxxx>
• [PATCH 2/4] btrfs: tweak free space tree bitmap allocation
  • From: David Sterba <dsterba@xxxxxxxx>
• [PULL][PATCH 0/4] Minor fixes to free-space-tree patchset, for 4.5
  • From: David Sterba <dsterba@xxxxxxxx>
• [PATCH v2] btrfs: sysfs: check initialization state before updating features
  • From: David Sterba <dsterba@xxxxxxxx>
• Re: [PATCH] btrfs: sysfs: check initialization state before updating features
  • From: David Sterba <dsterba@xxxxxxx>
• Re: [PATCH] btrfs: sysfs: check initialization state before updating features
  • From: Holger Hoffstätte <holger.hoffstaette@xxxxxxxxxxxxxx>
• [PATCH] Btrfs: fix invalid page accesses in extent_same (dedup) ioctl
  • From: fdmanana@xxxxxxxxxx
• [PATCH] btrfs: sysfs: check initialization state before updating features
  • From: David Sterba <dsterba@xxxxxxxx>
• [PATCH] btrfs: remove redundant error check
  • From: Byongho Lee <bhlee.kernel@xxxxxxxxx>
• Re: btrfs-progs 4.4 re-balance of RAID6 is very slow / limited to one cpu core?
  • From: Christian Rohmann <crohmann@xxxxxxxxxxxxx>
• Re: test fail for btrfs: synchronize incompat feature bits with sysfs files
  • From: David Sterba <dsterba@xxxxxxx>
• Re: uknown issues - different sha256 hash - files corruption
  • From: Duncan <1i5t5.duncan@xxxxxxx>
• test fail for btrfs: synchronize incompat feature bits with sysfs files
  • From: Zhao Lei <zhaolei@xxxxxxxxxxxxxx>
• Re: Btrfs: add support for multiple csum algorithms
  • From: Liu Bo <bo.li.liu@xxxxxxxxxx>
• Re: [PATCH] Btrfs: check reserved when deciding to background flush
  • From: Liu Bo <bo.li.liu@xxxxxxxxxx>
• Re: Add my git tree for linux-next
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: [PATCH 4/4] btrfs: synchronize incompat feature bits with sysfs files
  • From: Chris Mason <clm@xxxxxx>
• Re: btrfs-progs 4.4 re-balance of RAID6 is very slow / limited to one cpu core?
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: btrfs-progs 4.4 re-balance of RAID6 is very slow / limited to one cpu core?
  • From: "Austin S. Hemmelgarn" <ahferroin7@xxxxxxxxx>
• Re: btrfs-progs 4.4 re-balance of RAID6 is very slow / limited to one cpu core?
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: btrfs-progs 4.4 re-balance of RAID6 is very slow / limited to one cpu core?
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: uknown issues - different sha256 hash - files corruption
  • From: John Smith <lenovomi@xxxxxxxxx>
• Re: uknown issues - different sha256 hash - files corruption
  • From: Duncan <1i5t5.duncan@xxxxxxx>
• [PATCH v2] btrfs: simplify expression in btrfs_calc_trans_metadata_size()
  • From: Byongho Lee <bhlee.kernel@xxxxxxxxx>
• re: Btrfs: add support for multiple csum algorithms
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Re: [PATCH] btrfs: cleanup unusable parameters from ctree.h
  • From: David Sterba <dsterba@xxxxxxx>
• Re: [PATCH] btrfs: simplify expression in btrfs_csum_bytes_to_leaves()
  • From: Byongho Lee <bhlee.kernel@xxxxxxxxx>
• Re: [PATCH v8 5/4] copy_file_range.2: New page documenting copy_file_range()
  • From: Anna Schumaker <Anna.Schumaker@xxxxxxxxxx>
• [PATCH] Btrfs: check reserved when deciding to background flush
  • From: Josef Bacik <jbacik@xxxxxx>
• Re: uknown issues - different sha256 hash - files corruption
  • From: John Smith <lenovomi@xxxxxxxxx>
• system not booting
  • From: "Benjamin Draxlbauer" <Benjamin10@xxxxxx>
• Re: [PATCH] Btrfs: fix error number in send.c
  • From: David Sterba <dsterba@xxxxxxx>
• Re: uknown issues - different sha256 hash - files corruption
  • From: John Smith <lenovomi@xxxxxxxxx>
• Re: uknown issues - different sha256 hash - files corruption
  • From: Patrik Lundquist <patrik.lundquist@xxxxxxxxx>
• Re: suspected BTRFS errors resulting in file system becoming unrecovable
  • From: "Austin S. Hemmelgarn" <ahferroin7@xxxxxxxxx>
• Re: uknown issues - different sha256 hash - files corruption
  • From: John Smith <lenovomi@xxxxxxxxx>
• Re: uknown issues - different sha256 hash - files corruption
  • From: John Smith <lenovomi@xxxxxxxxx>
• Re: uknown issues - different sha256 hash - files corruption
  • From: John Smith <lenovomi@xxxxxxxxx>
• Re: UBSAN: Undefined behaviour in fs/btrfs/inode.c:5845:10
  • From: Chris Bainbridge <chris.bainbridge@xxxxxxxxx>
• [PATCH v2 2/2] btrfs: reada: avoid undone reada extents in btrfs_reada_wait
  • From: Zhao Lei <zhaolei@xxxxxxxxxxxxxx>
• [PATCH v2 1/2] btrfs: reada: limit max works count
  • From: Zhao Lei <zhaolei@xxxxxxxxxxxxxx>
• Re: UBSAN: Undefined behaviour in fs/btrfs/inode.c:5845:10
  • From: Holger Hoffstätte <holger.hoffstaette@xxxxxxxxxxxxxx>
• Re: UBSAN: Undefined behaviour in fs/btrfs/inode.c:5845:10
  • From: David Sterba <dsterba@xxxxxxx>
• Re: Add my git tree for linux-next
  • From: David Sterba <dsterba@xxxxxxx>
• UBSAN: Undefined behaviour in fs/btrfs/inode.c:5845:10
  • From: Chris Bainbridge <chris.bainbridge@xxxxxxxxx>
• Re: Add my git tree for linux-next
  • From: David Sterba <dsterba@xxxxxxx>
• Re: [PATCH v8 5/4] copy_file_range.2: New page documenting copy_file_range()
  • From: "Michael Kerrisk (man-pages)" <mtk.manpages@xxxxxxxxx>
• RE: [PATCH 1/2] btrfs: reada: limit max works count
  • From: Zhao Lei <zhaolei@xxxxxxxxxxxxxx>
• Re: [PATCH] btrfs: simplify expression in btrfs_csum_bytes_to_leaves()
  • From: Stefan Behrens <sbehrens@xxxxxxxxxxxxxxxx>
• Re: btrfs-progs 4.4 re-balance of RAID6 is very slow / limited to one cpu core?
  • From: Christian Rohmann <crohmann@xxxxxxxxxxxxx>
• Re: [PATCH] btrfs: simplify expression in btrfs_csum_bytes_to_leaves()
  • From: Byongho Lee <bhlee.kernel@xxxxxxxxx>
• Re: [PATCH] btrfs: simplify expression in btrfs_csum_bytes_to_leaves()
  • From: Stefan Behrens <sbehrens@xxxxxxxxxxxxxxxx>
• [PATCH] btrfs: simplify expression in btrfs_csum_bytes_to_leaves()
  • From: Byongho Lee <bhlee.kernel@xxxxxxxxx>
• Re: btrfs-progs 4.4 re-balance of RAID6 is very slow / limited to one cpu core?
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: btrfs-progs 4.4 re-balance of RAID6 is very slow / limited to one cpu core?
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: Add my git tree for linux-next
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: BTRFS: bdev /dev/mapper/dshelf1 errs: wr 2970, rd 848, flush 0, corrupt 189, gen 0
  • From: Qu Wenruo <quwenruo@xxxxxxxxxxxxxx>
• Re: Add my git tree for linux-next
  • From: Chris Mason <clm@xxxxxx>
• Fwd: btrfs-progs 4.4 re-balance of RAID6 is very slow / limited to one cpu core?
  • From: Justin Brown <justin.brown@xxxxxxxxxxxx>
• Re: [PATCH, 4.5-rc2] Revert "btrfs: clear PF_NOFREEZE in cleaner_kthread()"
  • From: Chris Mason <clm@xxxxxx>
• Re: uknown issues - different sha256 hash - files corruption
  • From: John Smith <lenovomi@xxxxxxxxx>
• Re: Add my git tree for linux-next
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: suspected BTRFS errors resulting in file system becoming unrecovable
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: btrfs-progs 4.4 re-balance of RAID6 is very slow / limited to one cpu core?
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: uknown issues - different sha256 hash - files corruption
  • From: Henk Slager <eye1tm@xxxxxxxxx>
• Re: suspected BTRFS errors resulting in file system becoming unrecovable
  • From: Piotr Szymaniak <szarpaj@xxxxxxxxxxx>
• Re: suspected BTRFS errors resulting in file system becoming unrecovable
  • From: Piotr Szymaniak <szarpaj@xxxxxxxxxxx>
• Re: [PATCH v8 5/4] copy_file_range.2: New page documenting copy_file_range()
  • From: Anna Schumaker <Anna.Schumaker@xxxxxxxxxx>
• Re: 4.4.0: btrfs-send BUG_ON(sctx->cur_ino != sctx->cmp_key->objectid);
  • From: Marc MERLIN <marc@xxxxxxxxxxx>
• Re: suspected BTRFS errors resulting in file system becoming unrecovable
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: BTRFS: bdev /dev/mapper/dshelf1 errs: wr 2970, rd 848, flush 0, corrupt 189, gen 0
  • From: Marc MERLIN <marc@xxxxxxxxxxx>
• Re: suspected BTRFS errors resulting in file system becoming unrecovable
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: 4.4.0: btrfs-send BUG_ON(sctx->cur_ino != sctx->cmp_key->objectid);
  • From: Filipe Manana <fdmanana@xxxxxxxxx>
• Re: 4.4.0: btrfs-send BUG_ON(sctx->cur_ino != sctx->cmp_key->objectid);
  • From: Marc MERLIN <marc@xxxxxxxxxxx>
• Re: 4.4.0: btrfs-send BUG_ON(sctx->cur_ino != sctx->cmp_key->objectid);
  • From: Filipe Manana <fdmanana@xxxxxxxxx>
• Re: btrfs receive fails
  • From: Stephan Olbrich <stephan@xxxxxxxxxxxxx>
• Add my git tree for linux-next
  • From: David Sterba <dsterba@xxxxxxx>
• Re: uknown issues - different sha256 hash - files corruption
  • From: John Smith <lenovomi@xxxxxxxxx>
• Re: suspected BTRFS errors resulting in file system becoming unrecovable
  • From: "Austin S. Hemmelgarn" <ahferroin7@xxxxxxxxx>
• Re: suspected BTRFS errors resulting in file system becoming unrecovable
  • From: Patrik Lundquist <patrik.lundquist@xxxxxxxxx>
• [PATCH][btrfs-progs] Include file verification with convert-tests
  • From: "Lakshmipathi.G" <lakshmipathi.g@xxxxxxxxx>
• suspected BTRFS errors resulting in file system becoming unrecovable
  • From: WillIam Thorne <will.thorne@xxxxxx>
• 4.4.0: btrfs-send BUG_ON(sctx->cur_ino != sctx->cmp_key->objectid);
  • From: Marc MERLIN <marc@xxxxxxxxxxx>
• Re: Reproduced deadlock after upgrade from 3.18 to 4.1 or 4.3 (+ more info)
  • From: Roman Mamedov <rm@xxxxxxxxxxx>
• Re: [PATCH v8 5/4] copy_file_range.2: New page documenting copy_file_range()
  • From: "Michael Kerrisk (man-pages)" <mtk.manpages@xxxxxxxxx>
• Re: [PATCH, 4.5-rc2] Revert "btrfs: clear PF_NOFREEZE in cleaner_kthread()"
  • From: Jiri Kosina <jikos@xxxxxxxxxx>
• Re: btrfs receive fails
  • From: "Austin S. Hemmelgarn" <ahferroin7@xxxxxxxxx>
• Re: btrfs-progs 4.4 re-balance of RAID6 is very slow / limited to one cpu core?
  • From: Christian Rohmann <crohmann@xxxxxxxxxxxxx>
• [PATCH, 4.5-rc2] Revert "btrfs: clear PF_NOFREEZE in cleaner_kthread()"
  • From: David Sterba <dsterba@xxxxxxxx>
• Re: uknown issues - different sha256 hash - files corruption
  • From: Patrik Lundquist <patrik.lundquist@xxxxxxxxx>
• Re: Chicken-egg: uncorrectable checksum error prevents RAID1 rebalancing
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: Chicken-egg: uncorrectable checksum error prevents RAID1 rebalancing
  • From: Tom Hunt <tomdicksonhunt@xxxxxxxxx>
• Re: [PATCH] Btrfs: fix error number in send.c
  • From: Tsutomu Itoh <t-itoh@xxxxxxxxxxxxxx>
• Re: BTRFS: bdev /dev/mapper/dshelf1 errs: wr 2970, rd 848, flush 0, corrupt 189, gen 0
  • From: Qu Wenruo <quwenruo@xxxxxxxxxxxxxx>
• Re: Chicken-egg: uncorrectable checksum error prevents RAID1 rebalancing
  • From: Duncan <1i5t5.duncan@xxxxxxx>
• Re: Chicken-egg: uncorrectable checksum error prevents RAID1 rebalancing
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: uknown issues - different sha256 hash - files corruption
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: uknown issues - different sha256 hash - files corruption
  • From: Duncan <1i5t5.duncan@xxxxxxx>
• Re: uknown issues - different sha256 hash - files corruption
  • From: Patrik Lundquist <patrik.lundquist@xxxxxxxxx>
• Re: Chicken-egg: uncorrectable checksum error prevents RAID1 rebalancing
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: Chicken-egg: uncorrectable checksum error prevents RAID1 rebalancing
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: Chicken-egg: uncorrectable checksum error prevents RAID1 rebalancing
  • From: Tom Hunt <tomdicksonhunt@xxxxxxxxx>
• uknown issues - different sha256 hash - files corruption
  • From: John Smith <lenovomi@xxxxxxxxx>
• Re: Chicken-egg: uncorrectable checksum error prevents RAID1 rebalancing
  • From: Tom Hunt <tomdicksonhunt@xxxxxxxxx>
• Re: Chicken-egg: uncorrectable checksum error prevents RAID1 rebalancing
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: Chicken-egg: uncorrectable checksum error prevents RAID1 rebalancing
  • From: Tom Hunt <tomdicksonhunt@xxxxxxxxx>
• Re: Chicken-egg: uncorrectable checksum error prevents RAID1 rebalancing
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Chicken-egg: uncorrectable checksum error prevents RAID1 rebalancing
  • From: Tom Hunt <tomdicksonhunt@xxxxxxxxx>
• Re: Query about proposed dedup patches and behaviours
  • From: Duncan <1i5t5.duncan@xxxxxxx>
• bad metadata [5198686912512, 5198686916608) crossing stripe boundary
  • From: Henk Slager <eye1tm@xxxxxxxxx>
• Re: btrfs-progs 4.4 re-balance of RAID6 is very slow / limited to one cpu core?
  • From: Henk Slager <eye1tm@xxxxxxxxx>
• Re: [bug] btrfs send -e option always fails ERROR: unexpected EOF in stream.
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: [bug] btrfs send -e option always fails ERROR: unexpected EOF in stream.
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: RAID1 disk upgrade method
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: [bug] btrfs send -e option always fails ERROR: unexpected EOF in stream.
  • From: Hugo Mills <hugo@xxxxxxxxxxxxx>
• [bug] btrfs send -e option always fails ERROR: unexpected EOF in stream.
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: Bad metadata / Incorrect global backref count
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: "Some devices missing" only while not mounted
  • From: Konstantin Svist <fry.kun@xxxxxxxxx>
• Re: BTRFS: bdev /dev/mapper/dshelf1 errs: wr 2970, rd 848, flush 0, corrupt 189, gen 0
  • From: Marc MERLIN <marc@xxxxxxxxxxx>
• Re: Why is dedup inline, not delayed (as opposed to offline)? Explain like I'm five pls.
  • From: Mark Fasheh <mfasheh@xxxxxxx>
• Re: Query about proposed dedup patches and behaviours
  • From: Mark Fasheh <mfasheh@xxxxxxx>
• Re: RAID1 disk upgrade method
  • From: Sean Greenslade <sean@xxxxxxxxxxxxxxxxxx>
• Re: btrfs receive fails
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• btrfs receive fails
  • From: Stephan Olbrich <stephan@xxxxxxxxxxxxx>
• Re: BTRFS: bdev /dev/mapper/dshelf1 errs: wr 2970, rd 848, flush 0, corrupt 189, gen 0
  • From: Marc MERLIN <marc@xxxxxxxxxxx>
• Re: Out of space on small-ish partition, clobber and other methods haven't worked
  • From: Jerry Steinhauer <jerry.steinhauer@xxxxxxxxxxxxxx>
• Re: Why is dedup inline, not delayed (as opposed to offline)? Explain like I'm five pls.
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: [PATCH 8/9] vfs: hoist the btrfs deduplication ioctl to the vfs
  • From: "Darrick J. Wong" <darrick.wong@xxxxxxxxxx>
• Re: Interjection: autodefrag mount option aye, nae?
  • From: Kai Krakow <hurikhan77@xxxxxxxxx>
• Re: Recovery of a raid1 FS
  • From: Tom Hunt <tomdicksonhunt@xxxxxxxxx>
• [GIT PULL] Btrfs
  • From: Chris Mason <clm@xxxxxx>
• Re: Fwd: Unmountable fs after power outage
  • From: Hugo Mills <hugo@xxxxxxxxxxxxx>
• Fwd: Unmountable fs after power outage
  • From: Radek Sprta <radek.sprta@xxxxxxxxx>
• Re: RAID1 root filesystem - same device shows up twice in 'btrfs fi show'
  • From: Scott Talbert <swt@xxxxxxxxxx>
• Re: btrfs-progs 4.4 re-balance of RAID6 is very slow / limited to one cpu core?
  • From: Duncan <1i5t5.duncan@xxxxxxx>
• Re: RAID1 disk upgrade method
  • From: "Austin S. Hemmelgarn" <ahferroin7@xxxxxxxxx>
• Re: [PATCH 1/2] btrfs: reada: limit max works count
  • From: Chris Mason <clm@xxxxxx>
• Re: [PATCH] btrfs: async-thread: Fix a use-after-free error for trace
  • From: David Sterba <dsterba@xxxxxxx>
• Re: [PATCH] Btrfs: fix error number in send.c
  • From: David Sterba <dsterba@xxxxxxx>
• btrfs-progs 4.4 re-balance of RAID6 is very slow / limited to one cpu core?
  • From: Christian Rohmann <crohmann@xxxxxxxxxxxxx>
• RE: [PATCH 1/2] btrfs: reada: limit max works count
  • From: Zhao Lei <zhaolei@xxxxxxxxxxxxxx>
• [PATCH] [RFC] btrfs: reada: avoid undone reada extents in btrfs_reada_wait
  • From: Zhao Lei <zhaolei@xxxxxxxxxxxxxx>
• Re: Interjection: autodefrag mount option aye, nae?
  • From: "Austin S. Hemmelgarn" <ahferroin7@xxxxxxxxx>
• Re: Out of space on small-ish partition, clobber and other methods haven't worked
  • From: Jerry Steinhauer <jerry.steinhauer@xxxxxxxxxxxxxx>
• Re: Out of space on small-ish partition, clobber and other methods haven't worked
  • From: Duncan <1i5t5.duncan@xxxxxxx>
• Re: Kernel 4.4.0 intermittent ENOSPC during heavy data write and concurrent snapshotting
  • From: "Austin S. Hemmelgarn" <ahferroin7@xxxxxxxxx>
• Re: Why is dedup inline, not delayed (as opposed to offline)? Explain like I'm five pls.
  • From: Al <6401e46d@xxxxxxxxx>
• Bad metadata / Incorrect global backref count
  • From: Jeroen Asselman <jeroen@xxxxxxxxxxxx>
• Re: RAID1 disk upgrade method
  • From: Duncan <1i5t5.duncan@xxxxxxx>
• Re: "Some devices missing" only while not mounted
  • From: Anand Jain <anand.jain@xxxxxxxxxx>
• Re: RAID1 root filesystem - same device shows up twice in 'btrfs fi show'
  • From: Anand Jain <anand.jain@xxxxxxxxxx>
• Re: "Some devices missing" only while not mounted
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: RAID1 disk upgrade method
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: "Some devices missing" only while not mounted
  • From: Anand Jain <anand.jain@xxxxxxxxxx>
• RAID1 disk upgrade method
  • From: Sean Greenslade <sean@xxxxxxxxxxxxxxxxxx>
• Re: FS corruption when mounting non-degraded after mounting degraded
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: "Some devices missing" only while not mounted
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: "Some devices missing" only while not mounted
  • From: Konstantin Svist <fry.kun@xxxxxxxxx>
• Re: [PATCH] btrfs: async-thread: Fix a use-after-free error for trace
  • From: Chris Mason <clm@xxxxxx>
• [PATCH] btrfs: async-thread: Fix a use-after-free error for trace
  • From: Qu Wenruo <quwenruo@xxxxxxxxxxxxxx>
• Re: FS corruption when mounting non-degraded after mounting degraded
  • From: Rian Hunter <rian@xxxxxxxxx>
• Re: use-after-free in perf_trace_btrfs__work
  • From: Qu Wenruo <quwenruo@xxxxxxxxxxxxxx>
• [PATCH] Btrfs: fix error number in send.c
  • From: Tsutomu Itoh <t-itoh@xxxxxxxxxxxxxx>
• Re: FS corruption when mounting non-degraded after mounting degraded
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: "Some devices missing" only while not mounted
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: "Some devices missing" only while not mounted
  • From: Konstantin Svist <fry.kun@xxxxxxxxx>
• Re: FS corruption when mounting non-degraded after mounting degraded
  • From: Rian Hunter <rian@xxxxxxxxx>
• Re: "Some devices missing" only while not mounted
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: Interjection: autodefrag mount option aye, nae?
  • From: Kai Krakow <hurikhan77@xxxxxxxxx>
• RAID1 root filesystem - same device shows up twice in 'btrfs fi show'
  • From: Scott Talbert <swt@xxxxxxxxxx>
• "Some devices missing" only while not mounted
  • From: Konstantin Svist <fry.kun@xxxxxxxxx>
• Re: [PATCH] btrfs-progs: Makefile.in: Simplify/correct install-static
  • From: David Sterba <dsterba@xxxxxxx>
• [PATCH 4/4] btrfs: synchronize incompat feature bits with sysfs files
  • From: David Sterba <dsterba@xxxxxxxx>
• [PATCH 3/4] btrfs: sysfs: introduce helper for syncing bits with sysfs files
  • From: David Sterba <dsterba@xxxxxxxx>
• [PATCH 2/4] btrfs: sysfs: add free-space-tree bit attribute
  • From: David Sterba <dsterba@xxxxxxxx>
• [PATCH 1/4] btrfs: sysfs: fix typo in compat_ro attribute definition
  • From: David Sterba <dsterba@xxxxxxxx>
• [PULL][PATCH 0/4] Sysfs fixes to incompat bits
  • From: David Sterba <dsterba@xxxxxxxx>
• Re: Out of space on small-ish partition, clobber and other methods haven't worked
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: Why is dedup inline, not delayed (as opposed to offline)? Explain like I'm five pls.
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: FS corruption when mounting non-degraded after mounting degraded
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: use-after-free in perf_trace_btrfs__work
  • From: Chris Mason <clm@xxxxxx>
• Re: FS corruption when mounting non-degraded after mounting degraded
  • From: Rich Freeman <r-btrfs@xxxxxxxxxxxxxxxxxxxxx>
• [PATCH] btrfs-progs: Makefile.in: Simplify/correct install-static
  • From: Mike Gilbert <floppym@xxxxxxxxxx>
• Re: Why is dedup inline, not delayed (as opposed to offline)? Explain like I'm five pls.
  • From: Al <6401e46d@xxxxxxxxx>
• Re: [PATCH 1/2] btrfs: reada: limit max works count
  • From: Chris Mason <clm@xxxxxx>
• Re: Out of space on small-ish partition, clobber and other methods haven't worked
  • From: Duncan <1i5t5.duncan@xxxxxxx>
• [PATCH V13 12/14] Revert "btrfs: fix lockups from btrfs_clear_path_blocking"
  • From: Chandan Rajendra <chandan@xxxxxxxxxxxxxxxxxx>
• [PATCH V13 11/14] Btrfs: subpagesize-blocksize: Prevent writes to an extent buffer when PG_writeback flag is set.
  • From: Chandan Rajendra <chandan@xxxxxxxxxxxxxxxxxx>
• [PATCH V13 14/14] Btrfs: subpagesize-blocksize: extent_clear_unlock_delalloc: Prevent page from being unlocked more than once
  • From: Chandan Rajendra <chandan@xxxxxxxxxxxxxxxxxx>
• [PATCH V13 13/14] Btrfs: subpagesize-blocksize: Fix file defragmentation code
  • From: Chandan Rajendra <chandan@xxxxxxxxxxxxxxxxxx>
• [PATCH V13 06/14] Btrfs: subpagesize-blocksize: Write only dirty extent buffers belonging to a page
  • From: Chandan Rajendra <chandan@xxxxxxxxxxxxxxxxxx>
• [PATCH V13 10/14] Btrfs: subpagesize-blocksize: btrfs_punch_hole: Fix uptodate blocks check
  • From: Chandan Rajendra <chandan@xxxxxxxxxxxxxxxxxx>
• [PATCH V13 04/14] Btrfs: subpagesize-blocksize: Define extent_buffer_head.
  • From: Chandan Rajendra <chandan@xxxxxxxxxxxxxxxxxx>
• [PATCH V13 09/14] Btrfs: subpagesize-blocksize: Explicitly track I/O status of blocks of an ordered extent.
  • From: Chandan Rajendra <chandan@xxxxxxxxxxxxxxxxxx>
• [PATCH V13 05/14] Btrfs: subpagesize-blocksize: Read tree blocks whose size is < PAGE_SIZE.
  • From: Chandan Rajendra <chandan@xxxxxxxxxxxxxxxxxx>
• [PATCH V13 08/14] Btrfs: subpagesize-blocksize: Deal with partial ordered extent allocations.
  • From: Chandan Rajendra <chandan@xxxxxxxxxxxxxxxxxx>
• [PATCH V13 07/14] Btrfs: subpagesize-blocksize: Allow mounting filesystems where sectorsize != PAGE_SIZE
  • From: Chandan Rajendra <chandan@xxxxxxxxxxxxxxxxxx>
• [PATCH V13 03/14] Btrfs: subpagesize-blocksize: Make sure delalloc range intersects with the locked page's range
  • From: Chandan Rajendra <chandan@xxxxxxxxxxxxxxxxxx>
• [PATCH V13 02/14] Btrfs: subpagesize-blocksize: Fix whole page write
  • From: Chandan Rajendra <chandan@xxxxxxxxxxxxxxxxxx>
• [PATCH V13 01/14] Btrfs: subpagesize-blocksize: Fix whole page read.
  • From: Chandan Rajendra <chandan@xxxxxxxxxxxxxxxxxx>
• [PATCH V13 00/14] Btrfs: Subpagesize-blocksize: Allow I/O on blocks whose size is less than page size.
  • From: Chandan Rajendra <chandan@xxxxxxxxxxxxxxxxxx>
• [PATCH V10 04/12] Btrfs: fallocate: Work with sectorsized blocks
  • From: Chandan Rajendra <chandan@xxxxxxxxxxxxxxxxxx>
• [PATCH V10 11/12] Btrfs: Clean pte corresponding to page straddling i_size
  • From: Chandan Rajendra <chandan@xxxxxxxxxxxxxxxxxx>
• [PATCH V10 12/12] Btrfs: btrfs_ioctl_clone: Truncate complete page after performing clone operation
  • From: Chandan Rajendra <chandan@xxxxxxxxxxxxxxxxxx>
• [PATCH V10 08/12] Btrfs: btrfs_submit_direct_hook: Handle map_length < bio vector length
  • From: Chandan Rajendra <chandan@xxxxxxxxxxxxxxxxxx>
• [PATCH V10 10/12] Btrfs: Fix block size returned to user space
  • From: Chandan Rajendra <chandan@xxxxxxxxxxxxxxxxxx>
• [PATCH V10 07/12] Btrfs: Use (eb->start, seq) as search key for tree modification log
  • From: Chandan Rajendra <chandan@xxxxxxxxxxxxxxxxxx>
• [PATCH V10 09/12] Btrfs: Limit inline extents to root->sectorsize
  • From: Chandan Rajendra <chandan@xxxxxxxxxxxxxxxxxx>
• [PATCH V10 06/12] Btrfs: Search for all ordered extents that could span across a page
  • From: Chandan Rajendra <chandan@xxxxxxxxxxxxxxxxxx>
• [PATCH V10 03/12] Btrfs: Direct I/O read: Work on sectorsized blocks
  • From: Chandan Rajendra <chandan@xxxxxxxxxxxxxxxxxx>
• [PATCH V10 02/12] Btrfs: Compute and look up csums based on sectorsized blocks
  • From: Chandan Rajendra <chandan@xxxxxxxxxxxxxxxxxx>
• [PATCH V10 05/12] Btrfs: btrfs_page_mkwrite: Reserve space in sectorsized units
  • From: Chandan Rajendra <chandan@xxxxxxxxxxxxxxxxxx>
• [PATCH V10 01/12] Btrfs: __btrfs_buffered_write: Reserve/release extents aligned to block size
  • From: Chandan Rajendra <chandan@xxxxxxxxxxxxxxxxxx>
• [PATCH V10 00/12] Btrfs: Pre subpagesize-blocksize cleanups
  • From: Chandan Rajendra <chandan@xxxxxxxxxxxxxxxxxx>
• [PATCH] Btrfs: fix race between fsync and lockless direct IO writes
  • From: fdmanana@xxxxxxxxxx
• RE: [PATCH 1/2] btrfs: reada: limit max works count
  • From: Zhao Lei <zhaolei@xxxxxxxxxxxxxx>
• Re: Kernel 4.4.0 intermittent ENOSPC during heavy data write and concurrent snapshotting
  • From: Roman Mamedov <rm@xxxxxxxxxxx>
• Re: Why is dedup inline, not delayed (as opposed to offline)? Explain like I'm five pls.
  • From: Qu Wenruo <quwenruo@xxxxxxxxxxxxxx>
• Re: BTRFS: bdev /dev/mapper/dshelf1 errs: wr 2970, rd 848, flush 0, corrupt 189, gen 0
  • From: Marc MERLIN <marc@xxxxxxxxxxx>
• RE: [PATCH 1/3] btrfs: Continue write in case of can_not_nocow
  • From: Zhao Lei <zhaolei@xxxxxxxxxxxxxx>
• RE: [PATCH 1/2] btrfs: reada: limit max works count
  • From: Zhao Lei <zhaolei@xxxxxxxxxxxxxx>
• Re: Out of space on small-ish partition, clobber and other methods haven't worked
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• [PATCH 1/3] btrfs-progs: Import interval tree implemenation from Linux v4.0-rc7.
  • From: Mark Fasheh <mfasheh@xxxxxxx>
• [PATCH 3/3] btrfs-progs du: Calculate space shared by each directory arguments file set
  • From: Mark Fasheh <mfasheh@xxxxxxx>
• [PATCH 2/3] btrfs-progs: add 'du' command
  • From: Mark Fasheh <mfasheh@xxxxxxx>
• [PATCH] btrfs-progs: add 'du' command
  • From: Mark Fasheh <mfasheh@xxxxxxx>
• Out of space on small-ish partition, clobber and other methods haven't worked
  • From: Jerry Steinhauer <jerry.steinhauer@xxxxxxxxxxxxxx>
• Re: [PATCH 1/3] btrfs: Continue write in case of can_not_nocow
  • From: Filipe Manana <fdmanana@xxxxxxxxx>
• Re: Kernel 4.4.0 intermittent ENOSPC during heavy data write and concurrent snapshotting
  • From: Filipe Manana <fdmanana@xxxxxxxxx>
• Re: Kernel 4.4.0 KVM guest on Btrfs locks up on snapshotting
  • From: Paolo Bonzini <pbonzini@xxxxxxxxxx>
• Re: Kernel 4.4.0 KVM guest on Btrfs locks up on snapshotting
  • From: Roman Mamedov <rm@xxxxxxxxxxx>
• Re: Interjection: autodefrag mount option aye, nae?
  • From: Duncan <1i5t5.duncan@xxxxxxx>
• Re: Why is dedup inline, not delayed (as opposed to offline)? Explain like I'm five pls.
  • From: Duncan <1i5t5.duncan@xxxxxxx>
• Re: Btrfs progs release 4.4
  • From: David Sterba <dsterba@xxxxxxx>
• Re: [PATCH 1/2] btrfs: reada: limit max works count
  • From: Chris Mason <clm@xxxxxx>
• Re: Kernel 4.4.0 KVM guest on Btrfs locks up on snapshotting
  • From: Paolo Bonzini <pbonzini@xxxxxxxxxx>
• Re: Interjection: autodefrag mount option aye, nae?
  • From: "Austin S. Hemmelgarn" <ahferroin7@xxxxxxxxx>
• Interjection: autodefrag mount option aye, nae?
  • From: Al <6401e46d@xxxxxxxxx>
• Kernel 4.4.0 intermittent ENOSPC during heavy data write and concurrent snapshotting
  • From: Roman Mamedov <rm@xxxxxxxxxxx>
• Re: [PATCH 1/2] btrfs: reada: limit max works count
  • From: Chris Mason <clm@xxxxxx>
• Re: Why is dedup inline, not delayed (as opposed to offline)? Explain like I'm five pls.
  • From: Al <6401e46d@xxxxxxxxx>
• Re: Kernel 4.4.0 KVM guest on Btrfs locks up on snapshotting
  • From: Roman Mamedov <rm@xxxxxxxxxxx>
• Re: Why is dedup inline, not delayed (as opposed to offline)? Explain like I'm five pls.
  • From: Al <6401e46d@xxxxxxxxx>
• Re: Why is dedup inline, not delayed (as opposed to offline)? Explain like I'm five pls.
  • From: Al <6401e46d@xxxxxxxxx>
• Re: Why is dedup inline, not delayed (as opposed to offline)? Explain like I'm five pls.
  • From: Al <6401e46d@xxxxxxxxx>
• Re: raid1 vs raid5
  • From: Psalle <psalleetsile@xxxxxxxxx>
• Re: Kernel 4.4.0 KVM guest on Btrfs locks up on snapshotting
  • From: Roman Mamedov <rm@xxxxxxxxxxx>
• Re: Kernel 4.4.0 KVM guest on Btrfs locks up on snapshotting
  • From: Paolo Bonzini <pbonzini@xxxxxxxxxx>
• Re: Btrfs progs release 4.4
  • From: David Sterba <dsterba@xxxxxxx>
• Re: Why is dedup inline, not delayed (as opposed to offline)? Explain like I'm five pls.
  • From: Brendan Hide <brendan@xxxxxxxxxxxxxxxxx>
• Re: Kernel 4.4.0 KVM guest on Btrfs locks up on snapshotting
  • From: Paolo Bonzini <pbonzini@xxxxxxxxxx>
• Re: Kernel 4.4.0 KVM guest on Btrfs locks up on snapshotting
  • From: Roman Mamedov <rm@xxxxxxxxxxx>
• Re: [PATCH v4 05/18] btrfs: delayed-ref: Add support for atomic increasing extent ref
  • From: Qu Wenruo <quwenruo@xxxxxxxxxxxxxx>
• Re: Btrfs progs release 4.4
  • From: Qu Wenruo <quwenruo@xxxxxxxxxxxxxx>
• Re: Kernel 4.4.0 KVM guest on Btrfs locks up on snapshotting
  • From: Liu Bo <bo.li.liu@xxxxxxxxxx>
• Re: Kernel 4.4.0 KVM guest on Btrfs locks up on snapshotting
  • From: Roman Mamedov <rm@xxxxxxxxxxx>
• Re: Kernel 4.4.0 KVM guest on Btrfs locks up on snapshotting
  • From: Paolo Bonzini <pbonzini@xxxxxxxxxx>
• Kernel 4.4.0 KVM guest on Btrfs locks up on snapshotting
  • From: Roman Mamedov <rm@xxxxxxxxxxx>
• [PATCH][btrfs-progs] Add dump-csums for btrfs inspect-internal
  • From: "Lakshmipathi.G" <lakshmipathi.g@xxxxxxxxx>
• Re: Why is dedup inline, not delayed (as opposed to offline)? Explain like I'm five pls.
  • From: Duncan <1i5t5.duncan@xxxxxxx>
• Re: FS corruption when mounting non-degraded after mounting degraded
  • From: Duncan <1i5t5.duncan@xxxxxxx>
• Re: Why is dedup inline, not delayed (as opposed to offline)? Explain like I'm five pls.
  • From: "Austin S. Hemmelgarn" <ahferroin7@xxxxxxxxx>
• Re: Why is dedup inline, not delayed (as opposed to offline)? Explain like I'm five pls.
  • From: "Austin S. Hemmelgarn" <ahferroin7@xxxxxxxxx>
• FS corruption when mounting non-degraded after mounting degraded
  • From: Rian Hunter <rian@xxxxxxxxx>
• Improve detail regarding distribution of RAID-stripes on "btrfs device usage" output (btrfs-progs 4.4)
  • From: Christian Rohmann <crohmann@xxxxxxxxxxxxx>
• [PULL] Btrfs: misc fixes for 4.5, part 2
  • From: David Sterba <dsterba@xxxxxxxx>
• [PATCH 3/4] Btrfs: clean up an error code in btrfs_init_space_info()
  • From: David Sterba <dsterba@xxxxxxxx>
• [PATCH 1/4] btrfs: cleanup, stop casting for extent_map->lookup everywhere
  • From: David Sterba <dsterba@xxxxxxxx>
• [PATCH 4/4] btrfs: remove duplicate const specifier
  • From: David Sterba <dsterba@xxxxxxxx>
• [PATCH 2/4] btrfs: fix iterator with update error in backref.c
  • From: David Sterba <dsterba@xxxxxxxx>
• [PULL][PATCH 0/4] Btrfs: cleanups for 4.5, part 2
  • From: David Sterba <dsterba@xxxxxxxx>
• [PATCH 3/3] btrfs: scrub: use GFP_KERNEL on the submission path
  • From: David Sterba <dsterba@xxxxxxxx>
• [PATCH 2/3] btrfs: reada: use GFP_KERNEL everywhere
  • From: David Sterba <dsterba@xxxxxxxx>
• [PATCH 1/3] btrfs: send: use GFP_KERNEL everywhere
  • From: David Sterba <dsterba@xxxxxxxx>
• [PATCH 0/3] GFP flags adjustments, part 2
  • From: David Sterba <dsterba@xxxxxxxx>
• Re: BTRFS: bdev /dev/mapper/dshelf1 errs: wr 2970, rd 848, flush 0, corrupt 189, gen 0
  • From: Duncan <1i5t5.duncan@xxxxxxx>
• Re: Why is dedup inline, not delayed (as opposed to offline)? Explain like I'm five pls.
  • From: Duncan <1i5t5.duncan@xxxxxxx>
• Re: Why is dedup inline, not delayed (as opposed to offline)? Explain like I'm five pls.
  • From: Duncan <1i5t5.duncan@xxxxxxx>
• [PATCH V7 2/3] btrfs: Introduce new mount option to disable tree log replay
  • From: Qu Wenruo <quwenruo@xxxxxxxxxxxxxx>
• [PATCH V7 3/3] btrfs: Introduce new mount option alias for nologreplay
  • From: Qu Wenruo <quwenruo@xxxxxxxxxxxxxx>
• [PATCH V7 1/3] btrfs: Introduce new mount option usebackuproot to replace recovery
  • From: Qu Wenruo <quwenruo@xxxxxxxxxxxxxx>
• [PATCH V7 0/3][PULL REQUEST] Unify 'norecovery' bahavior with other filesystems
  • From: Qu Wenruo <quwenruo@xxxxxxxxxxxxxx>
• Re: [PATCH V6 1/3] btrfs: Introduce new mount option usebackuproot to replace recovery
  • From: Qu Wenruo <quwenruo@xxxxxxxxxxxxxx>
• Re: [PATCH V6 2/3] btrfs: Introduce new mount option to disable tree log replay
  • From: Qu Wenruo <quwenruo@xxxxxxxxxxxxxx>
• Re: [PATCH V6 1/3] btrfs: Introduce new mount option usebackuproot to replace recovery
  • From: Christoph Anton Mitterer <calestyo@xxxxxxxxxxxx>
• Re: [PATCH V6 2/3] btrfs: Introduce new mount option to disable tree log replay
  • From: Christoph Anton Mitterer <calestyo@xxxxxxxxxxxx>
• [PATCH V6 2/3] btrfs: Introduce new mount option to disable tree log replay
  • From: Qu Wenruo <quwenruo@xxxxxxxxxxxxxx>
• [PATCH V6 1/3] btrfs: Introduce new mount option usebackuproot to replace recovery
  • From: Qu Wenruo <quwenruo@xxxxxxxxxxxxxx>
• [PATCH V6 3/3] btrfs: Introduce new mount option alias for nologreplay
  • From: Qu Wenruo <quwenruo@xxxxxxxxxxxxxx>
• [PATCH V6 0/3][PULL REQUEST] Unify 'norecovery' bahavior with other filesystems
  • From: Qu Wenruo <quwenruo@xxxxxxxxxxxxxx>
• Re: [PATCH v5 0/2][PULL REQUEST] Unify 'norecovery' bahavior with other filesystems
  • From: Qu Wenruo <quwenruo@xxxxxxxxxxxxxx>
• [PATCH] btrfs: remove duplicate const specifier
  • From: Colin King <colin.king@xxxxxxxxxxxxx>
• Re: BTRFS: bdev /dev/mapper/dshelf1 errs: wr 2970, rd 848, flush 0, corrupt 189, gen 0
  • From: Marc MERLIN <marc@xxxxxxxxxxx>
• Re: space_cache=v2 on root fs
  • From: Kai Krakow <hurikhan77@xxxxxxxxx>
• Re: space_cache=v2 on root fs
  • From: Markus Trippelsdorf <markus@xxxxxxxxxxxxxxx>
• space_cache=v2 on root fs
  • From: Markus Trippelsdorf <markus@xxxxxxxxxxxxxxx>
• Re: [PATCH 00/35 v3] eparate operations from flags in the bio/request structs
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• Btrfs progs release 4.4
  • From: David Sterba <dsterba@xxxxxxx>
• Re: Why is dedup inline, not delayed (as opposed to offline)? Explain like I'm five pls.
  • From: "Austin S. Hemmelgarn" <ahferroin7@xxxxxxxxx>
• Re: BTRFS: bdev /dev/mapper/dshelf1 errs: wr 2970, rd 848, flush 0, corrupt 189, gen 0
  • From: Hugo Mills <hugo@xxxxxxxxxxxxx>
• Re: Why is dedup inline, not delayed (as opposed to offline)? Explain like I'm five pls.
  • From: "Austin S. Hemmelgarn" <ahferroin7@xxxxxxxxx>
• RE: [GIT PULL] Fujitsu for 4.5
  • From: Zhao Lei <zhaolei@xxxxxxxxxxxxxx>
• Re: [GIT PULL] Btrfs
  • From: Holger Hoffstätte <holger.hoffstaette@xxxxxxxxxxxxxx>
• Re: [GIT PULL] Btrfs
  • From: Martin Steigerwald <martin@xxxxxxxxxxxx>
• Re: Why is dedup inline, not delayed (as opposed to offline)? Explain like I'm five pls.
  • From: Duncan <1i5t5.duncan@xxxxxxx>
• Re: BTRFS: bdev /dev/mapper/dshelf1 errs: wr 2970, rd 848, flush 0, corrupt 189, gen 0
  • From: Duncan <1i5t5.duncan@xxxxxxx>
• Re: Why is dedup inline, not delayed (as opposed to offline)? Explain like I'm five pls.
  • From: Qu Wenruo <quwenruo@xxxxxxxxxxxxxx>
• Re: Why is dedup inline, not delayed (as opposed to offline)? Explain like I'm five pls.
  • From: Duncan <1i5t5.duncan@xxxxxxx>
• Re: btrfs send - detect if complete
  • From: Duncan <1i5t5.duncan@xxxxxxx>
• Re: Why is dedup inline, not delayed (as opposed to offline)? Explain like I'm five pls.
  • From: Qu Wenruo <quwenruo@xxxxxxxxxxxxxx>
• BTRFS: bdev /dev/mapper/dshelf1 errs: wr 2970, rd 848, flush 0, corrupt 189, gen 0
  • From: Marc MERLIN <marc@xxxxxxxxxxx>
• [GIT PULL] Btrfs
  • From: Chris Mason <clm@xxxxxx>
• Re: Copying between lzo compressed BtrFS's: de/re-compressing.
  • From: Diagon <kernel.boxy@xxxxxxxx>
• Re: Copying between lzo compressed BtrFS's: de/re-compressing.
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: Copying between lzo compressed BtrFS's: de/re-compressing.
  • From: Diagon <kernel.boxy@xxxxxxxx>
• Re: kernel crash when balancing raid56 after low on space
  • From: bbrendon@xxxxxxxxx
• btrfs send - detect if complete
  • From: Lubos Kolouch <kolcon@xxxxxxxxxx>
• Re: Why is dedup inline, not delayed (as opposed to offline)? Explain like I'm five pls.
  • From: Rich Freeman <r-btrfs@xxxxxxxxxxxxxxxxxxxxx>
• Re: Why is dedup inline, not delayed (as opposed to offline)? Explain like I'm five pls.
  • From: Duncan <1i5t5.duncan@xxxxxxx>
• Why is dedup inline, not delayed (as opposed to offline)? Explain like I'm five pls.
  • From: Al <6401e46d@xxxxxxxxx>
• BTRFS Soft CPU Lockup
  • From: Bryan Apperson <bryan.apperson@xxxxxxxx>
• BTRFS CPU Soft Lockup
  • From: "Apperson, Bryan" <Bryan.Apperson@xxxxxxxx>
• Re: [PATCH v4 17/18] btrfs: dedup: add a property handler for online dedup
  • From: Duncan <1i5t5.duncan@xxxxxxx>
• Re: [PATCH] Btrfs: copy the certain type of item if min_type equals to max_type
  • From: Liu Bo <bo.li.liu@xxxxxxxxxx>
• Re: [PATCH] Btrfs: copy the certain type of item if min_type equals to max_type
  • From: Hugo Mills <hugo@xxxxxxxxxxxxx>
• [PATCH] Btrfs: copy the certain type of item if min_type equals to max_type
  • From: Liu Bo <bo.li.liu@xxxxxxxxxx>
• Re: [PATCH] btrfs: initialize the seq counter in struct btrfs_device
  • From: David Sterba <dsterba@xxxxxxx>
• Re: Btrfs progs pre-release 4.4-rc1
  • From: David Sterba <dsterba@xxxxxxx>
• Re: [PATCH v5 0/2][PULL REQUEST] Unify 'norecovery' bahavior with other filesystems
  • From: David Sterba <dsterba@xxxxxxx>
• Re: [PATCH 2/3] btrfs: add balance filter for stripes
  • From: David Sterba <dsterba@xxxxxxx>
• Re: [GIT PULL] Fujitsu for 4.5
  • From: David Sterba <dsterba@xxxxxxx>
• Re: [GIT PULL] Fujitsu for 4.5
  • From: Chris Mason <clm@xxxxxx>
• Re: Recursive delete file from all subvolumes (snapshots)
  • From: Duncan <1i5t5.duncan@xxxxxxx>
• Re: [PATCH v4 17/18] btrfs: dedup: add a property handler for online dedup
  • From: Filipe Manana <fdmanana@xxxxxxxxx>
• Re: Crash on btrfs check
  • From: "cheater00 ." <cheater00@xxxxxxxxx>
• [PATCH] btrfs: initialize the seq counter in struct btrfs_device
  • From: Sebastian Andrzej Siewior <bigeasy@xxxxxxxxxxxxx>
• Re: Recursive delete file from all subvolumes (snapshots)
  • From: Wolfgang Mader <Wolfgang_Mader@xxxxxxxxxxxxx>
• Re: Btrfs progs pre-release 4.4-rc1
  • From: David Sterba <dsterba@xxxxxxx>
• Static build fixed (Was: Re: Btrfs progs pre-release 4.4-rc1
  • From: David Sterba <dsterba@xxxxxxx>
• Re: [PATCH v4 17/18] btrfs: dedup: add a property handler for online dedup
  • From: Duncan <1i5t5.duncan@xxxxxxx>
• Re: Copying between lzo compressed BtrFS's: de/re-compressing.
  • From: Timofey Titovets <nefelim4ag@xxxxxxxxx>
• Re: Copying between lzo compressed BtrFS's: de/re-compressing.
  • From: Filipe Manana <fdmanana@xxxxxxxxx>
• Re: Query about proposed dedup patches and behaviours
  • From: Duncan <1i5t5.duncan@xxxxxxx>
• Re: Recursive delete file from all subvolumes (snapshots)
  • From: Duncan <1i5t5.duncan@xxxxxxx>
• [PATCH] Btrfs: fix deadlock running delayed iputs at transaction commit time
  • From: fdmanana@xxxxxxxxxx
• [PATCH] Btrfs: fix typo in log message when starting a balance
  • From: fdmanana@xxxxxxxxxx
• Re: Copying between lzo compressed BtrFS's: de/re-compressing.
  • From: Timofey Titovets <nefelim4ag@xxxxxxxxx>
• RE: [GIT PULL] Fujitsu for 4.5
  • From: Zhao Lei <zhaolei@xxxxxxxxxxxxxx>
• Re: [PATCH v4 17/18] btrfs: dedup: add a property handler for online dedup
  • From: Qu Wenruo <quwenruo@xxxxxxxxxxxxxx>
• Re: Query about proposed dedup patches and behaviours
  • From: James Hogarth <james.hogarth@xxxxxxxxx>
• Re: [PATCH v4 17/18] btrfs: dedup: add a property handler for online dedup
  • From: Filipe Manana <fdmanana@xxxxxxxxx>
• Copying between lzo compressed BtrFS's: de/re-compressing.
  • From: Diagon <kernel.boxy@xxxxxxxx>
• Re: Recursive delete file from all subvolumes (snapshots)
  • From: Wolfgang Mader <Wolfgang_Mader@xxxxxxxxxxxxx>
• Re: Recursive delete file from all subvolumes (snapshots)
  • From: Roman Mamedov <rm@xxxxxxxxxxx>
• Recursive delete file from all subvolumes (snapshots)
  • From: Wolfgang Mader <Wolfgang_Mader@xxxxxxxxxxxxx>
• kernel crash when balancing raid56 after low on space
  • From: bbrendon@xxxxxxxxx
• use-after-free in perf_trace_btrfs__work
  • From: Dave Jones <davej@xxxxxxxxxxxxxxxxx>
• Re: Crash on btrfs check
  • From: Qu Wenruo <quwenruo@xxxxxxxxxxxxxx>
• Re: Crash on btrfs check
  • From: Qu Wenruo <quwenruo@xxxxxxxxxxxxxx>
• Crash on btrfs check
  • From: "cheater00 ." <cheater00@xxxxxxxxx>
• Re: [PATCH v5 0/2][PULL REQUEST] Unify 'norecovery' bahavior with other filesystems
  • From: Qu Wenruo <quwenruo@xxxxxxxxxxxxxx>
• Re: Query about proposed dedup patches and behaviours
  • From: Duncan <1i5t5.duncan@xxxxxxx>
• Re: [PATCH v4 13/18] btrfs: dedup: Add support to delete hash for on-disk backend
  • From: Qu Wenruo <quwenruo@xxxxxxxxxxxxxx>
• Re: [PATCH v4 07/18] btrfs: dedup: Implement btrfs_dedup_calc_hash interface
  • From: Qu Wenruo <quwenruo@xxxxxxxxxxxxxx>
• Re: [PATCH v4 17/18] btrfs: dedup: add a property handler for online dedup
  • From: Qu Wenruo <quwenruo@xxxxxxxxxxxxxx>
• Re: [PATCH v4 05/18] btrfs: delayed-ref: Add support for atomic increasing extent ref
  • From: Qu Wenruo <quwenruo@xxxxxxxxxxxxxx>
• Re: [PATCH V2] Btrfs: fix output of compression message in btrfs_parse_options()
  • From: Tsutomu Itoh <t-itoh@xxxxxxxxxxxxxx>
• [PATCH] Btrfs-progs: add check-only option for balance
  • From: Liu Bo <bo.li.liu@xxxxxxxxxx>
• Re: [PATCH v4 02/18] btrfs: dedup: Introduce function to initialize dedup info
  • From: kbuild test robot <lkp@xxxxxxxxx>
• Re: Query about proposed dedup patches and behaviours
  • From: "Austin S. Hemmelgarn" <ahferroin7@xxxxxxxxx>
• Re: Query about proposed dedup patches and behaviours
  • From: Liu Bo <bo.li.liu@xxxxxxxxxx>
• Re: [PATCH v4 17/18] btrfs: dedup: add a property handler for online dedup
  • From: "Darrick J. Wong" <darrick.wong@xxxxxxxxxx>
• Re: Query about proposed dedup patches and behaviours
  • From: "Austin S. Hemmelgarn" <ahferroin7@xxxxxxxxx>
• Query about proposed dedup patches and behaviours
  • From: James Hogarth <james.hogarth@xxxxxxxxx>
• Re: [PATCH 2/3] btrfs: add balance filter for stripes
  • From: Christian Rohmann <crohmann@xxxxxxxxxxxxx>
• Re: [PATCH v5 0/2][PULL REQUEST] Unify 'norecovery' bahavior with other filesystems
  • From: David Sterba <dsterba@xxxxxxx>
• Re: Btrfs progs pre-release 4.4-rc1
  • From: Noah Massey <noah.massey@xxxxxxxxx>
• Re: [PATCH V2] Btrfs: fix output of compression message in btrfs_parse_options()
  • From: David Sterba <dsterba@xxxxxxx>
• Re: [PATCH V2] Btrfs: fix output of compression message in btrfs_parse_options()
  • From: David Sterba <dsterba@xxxxxxx>
• Re: [GIT PULL] Fujitsu for 4.5
  • From: David Sterba <dsterba@xxxxxxx>
• Re: Btrfs progs pre-release 4.4-rc1
  • From: Holger Hoffstätte <holger.hoffstaette@xxxxxxxxxxxxxx>
• Btrfs progs pre-release 4.4-rc1
  • From: David Sterba <dsterba@xxxxxxx>
• Re: [PATCH] btrfs-progs: Use AC_CHECK_TOOL to find AR
  • From: David Sterba <dsterba@xxxxxxx>
• Re: [PATCH v4 13/18] btrfs: dedup: Add support to delete hash for on-disk backend
  • From: Filipe Manana <fdmanana@xxxxxxxxx>
• [PATCH] btrfs-progs: Use AC_CHECK_TOOL to find AR
  • From: Mike Gilbert <floppym@xxxxxxxxxx>
• Re: [PATCH v4 07/18] btrfs: dedup: Implement btrfs_dedup_calc_hash interface
  • From: Filipe Manana <fdmanana@xxxxxxxxx>
• Re: [PATCH v4.1 12/18] btrfs: dedup: Add support for on-disk hash search
  • From: Filipe Manana <fdmanana@xxxxxxxxx>
• Re: [PATCH v4 17/18] btrfs: dedup: add a property handler for online dedup
  • From: Filipe Manana <fdmanana@xxxxxxxxx>
• Re: [PATCH v4 05/18] btrfs: delayed-ref: Add support for atomic increasing extent ref
  • From: Filipe Manana <fdmanana@xxxxxxxxx>
• [PATCH v4.1 12/18] btrfs: dedup: Add support for on-disk hash search
  • From: Qu Wenruo <quwenruo@xxxxxxxxxxxxxx>
• [PATCH v4 04/18] btrfs: dedup: Introduce function to remove hash from in-memory tree
  • From: Qu Wenruo <quwenruo@xxxxxxxxxxxxxx>
• [PATCH v4 01/18] btrfs: dedup: Introduce dedup framework and its header
  • From: Qu Wenruo <quwenruo@xxxxxxxxxxxxxx>
• [PATCH v4 03/18] btrfs: dedup: Introduce function to add hash into in-memory tree
  • From: Qu Wenruo <quwenruo@xxxxxxxxxxxxxx>
• [PATCH v4 00/14][For 4.6] Btrfs: Add inband (write time) de-duplication framework
  • From: Qu Wenruo <quwenruo@xxxxxxxxxxxxxx>
• [PATCH v4 08/18] btrfs: ordered-extent: Add support for dedup
  • From: Qu Wenruo <quwenruo@xxxxxxxxxxxxxx>
• [PATCH v4 13/18] btrfs: dedup: Add support to delete hash for on-disk backend
  • From: Qu Wenruo <quwenruo@xxxxxxxxxxxxxx>
• [PATCH v4 02/18] btrfs: dedup: Introduce function to initialize dedup info
  • From: Qu Wenruo <quwenruo@xxxxxxxxxxxxxx>
• [PATCH v4 07/18] btrfs: dedup: Implement btrfs_dedup_calc_hash interface
  • From: Qu Wenruo <quwenruo@xxxxxxxxxxxxxx>
• [PATCH v4 11/18] btrfs: dedup: Introduce interfaces to resume and cleanup dedup info
  • From: Qu Wenruo <quwenruo@xxxxxxxxxxxxxx>
• [PATCH v4 17/18] btrfs: dedup: add a property handler for online dedup
  • From: Qu Wenruo <quwenruo@xxxxxxxxxxxxxx>
• [PATCH v4 09/18] btrfs: dedup: Inband in-memory only de-duplication implement
  • From: Qu Wenruo <quwenruo@xxxxxxxxxxxxxx>
• [PATCH v4 18/18] btrfs: dedup: add per-file online dedup control
  • From: Qu Wenruo <quwenruo@xxxxxxxxxxxxxx>
• [PATCH v3 2/8] btrfs-progs: dedup: Add enable command for dedup command group
  • From: Qu Wenruo <quwenruo@xxxxxxxxxxxxxx>
• [PATCH v3 3/8] btrfs-progs: dedup: Add disable support for inban deduplication
  • From: Qu Wenruo <quwenruo@xxxxxxxxxxxxxx>
• [PATCH v3 5/8] btrfs-progs: Add dedup feature for mkfs and convert
  • From: Qu Wenruo <quwenruo@xxxxxxxxxxxxxx>
• [PATCH v3 6/8] btrfs-progs: Add show-super support for new DEDUP flag
  • From: Qu Wenruo <quwenruo@xxxxxxxxxxxxxx>
• [PATCH v4 16/18] btrfs: dedup: add an inode nodedup flag
  • From: Qu Wenruo <quwenruo@xxxxxxxxxxxxxx>
• [PATCH v3 0/8] btrfs-progs: Support in-band de-duplication
  • From: Qu Wenruo <quwenruo@xxxxxxxxxxxxxx>
• [PATCH v3 1/8] btrfs-progs: Basic framework for dedup command group
  • From: Qu Wenruo <quwenruo@xxxxxxxxxxxxxx>
• [PATCH v3 8/8] btrfs-progs: property: add a dedup property
  • From: Qu Wenruo <quwenruo@xxxxxxxxxxxxxx>
• [PATCH v4 10/18] btrfs: dedup: Add basic tree structure for on-disk dedup method
  • From: Qu Wenruo <quwenruo@xxxxxxxxxxxxxx>
• [PATCH v4 14/18] btrfs: dedup: Add support for adding hash for on-disk backend
  • From: Qu Wenruo <quwenruo@xxxxxxxxxxxxxx>
• [PATCH v3 7/8] btrfs-progs: dedup-tree: Add dedup tree support
  • From: Qu Wenruo <quwenruo@xxxxxxxxxxxxxx>
• [PATCH v3 4/8] btrfs-progs: dedup: Add status subcommand
  • From: Qu Wenruo <quwenruo@xxxxxxxxxxxxxx>
• [PATCH v4 15/18] btrfs: dedup: Add ioctl for inband deduplication
  • From: Qu Wenruo <quwenruo@xxxxxxxxxxxxxx>
• [PATCH v4 12/18] btrfs: dedup: Add support for on-disk hash search
  • From: Qu Wenruo <quwenruo@xxxxxxxxxxxxxx>
• [PATCH v4 06/18] btrfs: dedup: Introduce function to search for an existing hash
  • From: Qu Wenruo <quwenruo@xxxxxxxxxxxxxx>
• [PATCH v4 05/18] btrfs: delayed-ref: Add support for atomic increasing extent ref
  • From: Qu Wenruo <quwenruo@xxxxxxxxxxxxxx>
• input/output errors on btrfs-luks-lvm
  • From: Kenny MacDermid <kenny.macdermid@xxxxxxxxx>
• Re: [PATCH V2] Btrfs: fix output of compression message in btrfs_parse_options()
  • From: Tsutomu Itoh <t-itoh@xxxxxxxxxxxxxx>
• [PATCH] Btrfs: add transaction space reservation tracepoints
  • From: Josef Bacik <jbacik@xxxxxx>
• Re: [patch] Btrfs: clean up an error code in btrfs_init_space_info()
  • From: Liu Bo <bo.li.liu@xxxxxxxxxx>
• Re: "BTRFS critical (device sda1): unable to find logical 576460868201611264 len 4096", hardware or software error ?
  • From: David Sterba <dsterba@xxxxxxx>
• [PATCH] Btrfs: fix truncate_space_check
  • From: Josef Bacik <jbacik@xxxxxx>
• "BTRFS critical (device sda1): unable to find logical 576460868201611264 len 4096", hardware or software error ?
  • From: Léo Gillot-Lamure <leo.gillot@xxxxxxxxxxx>
• Re: [PATCH] btrfs: add lz4 compression support
  • From: David Sterba <dsterba@xxxxxxx>
• [PATCH] btrfs: fix iterator with update error in backref.c
  • From: Geliang Tang <geliangtang@xxxxxxx>
• [PATCH] btrfs: add lz4 compression support
  • From: Geliang Tang <geliangtang@xxxxxxx>
• Re: [patch] Btrfs: clean up an error code in btrfs_init_space_info()
  • From: David Sterba <dsterba@xxxxxxx>
• Re: [PATCH V2] Btrfs: fix output of compression message in btrfs_parse_options()
  • From: David Sterba <dsterba@xxxxxxx>
• [patch] Btrfs: clean up an error code in btrfs_init_space_info()
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• [PATCH] btrfs-progs: fi usage: support mixed blockgroups
  • From: David Sterba <dsterba@xxxxxxxx>
• send/receive and a WEIRD path
  • From: Mordechay Kaganer <mkaganer@xxxxxxxxx>
• [GIT PULL] Fujitsu for 4.5
  • From: Zhao Lei <zhaolei@xxxxxxxxxxxxxx>
• Re: [PATCH v2 17/25] btrfs-progs: extent-tree: Enhance btrfs_record_file_extent
  • From: David Sterba <dsterba@xxxxxxx>
• Re: [PATCH 8/9] vfs: hoist the btrfs deduplication ioctl to the vfs
  • From: Eric Biggers <ebiggers3@xxxxxxxxx>
• Re: [PATCH] btrfs-progs: Format change for btrfs fi df
  • From: Qu Wenruo <quwenruo@xxxxxxxxxxxxxx>
• Re: [PATCH] btrfs-progs: Format change for btrfs fi df
  • From: Qu Wenruo <quwenruo@xxxxxxxxxxxxxx>
• Re: [PATCH v2 17/25] btrfs-progs: extent-tree: Enhance btrfs_record_file_extent
  • From: Qu Wenruo <quwenruo@xxxxxxxxxxxxxx>
• Re: [PATCH] btrfs-progs: Format change for btrfs fi df
  • From: Henk Slager <eye1tm@xxxxxxxxx>
• Re: [PATCH] btrfs-progs: Format change for btrfs fi df
  • From: Goffredo Baroncelli <kreijack@xxxxxxxxx>
• Re: [PATCH v3] btrfs: use list_for_each_entry* in backref.c
  • From: David Sterba <dsterba@xxxxxxx>
• Re: [PATCH] BTRFS: Adds an option to select RAID Stripe size
  • From: Sanidhya Solanki <jpage.lkml@xxxxxxxxx>
• LSF/MM 2016: Call for Proposals
  • From: "Martin K. Petersen" <martin.petersen@xxxxxxxxxx>
• [PATCH v3] btrfs: use list_for_each_entry* in backref.c
  • From: Geliang Tang <geliangtang@xxxxxxx>
• Re: [kdave:misc-cleanups-4.5 9/9] fs/btrfs/backref.c:565:1-20: iterator with update on line 577
  • From: Geliang Tang <geliangtang@xxxxxxx>
• Re: [PATCH] btrfs-progs: Format change for btrfs fi df
  • From: David Sterba <dsterba@xxxxxxx>
• Re: [PATCH] BTRFS: Adds an option to select RAID Stripe size
  • From: "Austin S. Hemmelgarn" <ahferroin7@xxxxxxxxx>
• Re: [PATCH v2 17/25] btrfs-progs: extent-tree: Enhance btrfs_record_file_extent
  • From: David Sterba <dsterba@xxxxxxx>
• Re: [PATCH 8/9] vfs: hoist the btrfs deduplication ioctl to the vfs
  • From: "Darrick J. Wong" <darrick.wong@xxxxxxxxxx>
• [PATCH 2/2] btrfs: reada: simplify dev->reada_in_flight processing
  • From: Zhao Lei <zhaolei@xxxxxxxxxxxxxx>
• [PATCH 1/2] btrfs: reada: limit max works count
  • From: Zhao Lei <zhaolei@xxxxxxxxxxxxxx>
• Re: About per-file dedup flag
  • From: Duncan <1i5t5.duncan@xxxxxxx>
• Re: About per-file dedup flag
  • From: Qu Wenruo <quwenruo@xxxxxxxxxxxxxx>
• Re: About per-file dedup flag
  • From: Duncan <1i5t5.duncan@xxxxxxx>
• About per-file dedup flag
  • From: Qu Wenruo <quwenruo@xxxxxxxxxxxxxx>
• Re: 6TB partition, Data only 2TB - aka When you haven't hit the "usual" problem
  • From: Duncan <1i5t5.duncan@xxxxxxx>
• [PATCH v5 2/2] btrfs: Introduce new mount option to disable tree log replay
  • From: Qu Wenruo <quwenruo@xxxxxxxxxxxxxx>
• [PATCH v5 1/2] btrfs: Introduce new mount option usebackuproot to replace recovery
  • From: Qu Wenruo <quwenruo@xxxxxxxxxxxxxx>
• [PATCH v5 0/2][PULL REQUEST] Unify 'norecovery' bahavior with other filesystems
  • From: Qu Wenruo <quwenruo@xxxxxxxxxxxxxx>
• Re: 6TB partition, Data only 2TB - aka When you haven't hit the "usual" problem
  • From: Duncan <1i5t5.duncan@xxxxxxx>
• Re: 6TB partition, Data only 2TB - aka When you haven't hit the "usual" problem
  • From: Duncan <1i5t5.duncan@xxxxxxx>
• Re: 6TB partition, Data only 2TB - aka When you haven't hit the "usual" problem
  • From: Duncan <1i5t5.duncan@xxxxxxx>
• Re: [PATCH] btrfs-progs: chunk-recovery: Fix a float point error
  • From: Qu Wenruo <quwenruo@xxxxxxxxxxxxxx>
• Re: [PATCH] btrfs-progs: Format change for btrfs fi df
  • From: Duncan <1i5t5.duncan@xxxxxxx>
• Re: 6TB partition, Data only 2TB - aka When you haven't hit the "usual" problem
  • From: "cheater00 ." <cheater00@xxxxxxxxx>
• Re: 6TB partition, Data only 2TB - aka When you haven't hit the "usual" problem
  • From: Hugo Mills <hugo@xxxxxxxxxxxxx>
• Re: 6TB partition, Data only 2TB - aka When you haven't hit the "usual" problem
  • From: "cheater00 ." <cheater00@xxxxxxxxx>
• Re: 6TB partition, Data only 2TB - aka When you haven't hit the "usual" problem
  • From: "cheater00 ." <cheater00@xxxxxxxxx>
• Re: 6TB partition, Data only 2TB - aka When you haven't hit the "usual" problem
  • From: "cheater00 ." <cheater00@xxxxxxxxx>
• Re: 6TB partition, Data only 2TB - aka When you haven't hit the "usual" problem
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: 6TB partition, Data only 2TB - aka When you haven't hit the "usual" problem
  • From: Hugo Mills <hugo@xxxxxxxxxxxxx>
• [PATCH] Btrfs: change how we update the global block rsv
  • From: Josef Bacik <jbacik@xxxxxx>
• Re: 6TB partition, Data only 2TB - aka When you haven't hit the "usual" problem
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: Purposely using btrfs RAID1 in degraded mode ?
  • From: Alphazo <alphazo@xxxxxxxxx>
• Re: 6TB partition, Data only 2TB - aka When you haven't hit the "usual" problem
  • From: Hugo Mills <hugo@xxxxxxxxxxxxx>
• Re: 6TB partition, Data only 2TB - aka When you haven't hit the "usual" problem
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• [PATCH 00/35 v3] eparate operations from flags in the bio/request structs
  • From: mchristi@xxxxxxxxxx
• [PATCH 01/35] block/fs/drivers: remove rw argument from submit_bio
  • From: mchristi@xxxxxxxxxx
• [PATCH 04/35] fs: have submit_bh users pass in op and flags separately
  • From: mchristi@xxxxxxxxxx
• [PATCH 02/35] block: add REQ_OP definitions and bi_op/op fields
  • From: mchristi@xxxxxxxxxx
• [PATCH 05/35] fs: have ll_rw_block users pass in op and flags separately
  • From: mchristi@xxxxxxxxxx
• [PATCH 06/35] direct-io: set bi_op to REQ_OP
  • From: mchristi@xxxxxxxxxx
• [PATCH 09/35] btrfs: update __btrfs_map_block for bi_op transition
  • From: mchristi@xxxxxxxxxx
• [PATCH 08/35] btrfs: set bi_op tp REQ_OP
  • From: mchristi@xxxxxxxxxx
• [PATCH 10/35] btrfs: don't pass rq_flag_bits if there is a bio
  • From: mchristi@xxxxxxxxxx
• [PATCH 11/35] f2fs: set bi_op to REQ_OP
  • From: mchristi@xxxxxxxxxx
• [PATCH 07/35] btrfs: have submit_one_bio users setup bio bi_op
  • From: mchristi@xxxxxxxxxx
• [PATCH 12/35] gfs2: set bi_op to REQ_OP
  • From: mchristi@xxxxxxxxxx
• [PATCH 13/35] xfs: set bi_op to REQ_OP
  • From: mchristi@xxxxxxxxxx
• [PATCH 15/35] mpage: set bi_op to REQ_OP
  • From: mchristi@xxxxxxxxxx
• [PATCH 14/35] hfsplus: set bi_op to REQ_OP
  • From: mchristi@xxxxxxxxxx
• [PATCH 17/35] ocfs2: set bi_op to REQ_OP
  • From: mchristi@xxxxxxxxxx
• [PATCH 16/35] nilfs: set bi_op to REQ_OP
  • From: mchristi@xxxxxxxxxx
• [PATCH 18/35] pm: set bi_op to REQ_OP
  • From: mchristi@xxxxxxxxxx
• [PATCH 20/35] dm: pass dm stats data dir instead of bi_rw
  • From: mchristi@xxxxxxxxxx
• [PATCH 21/35] bcache: set bi_op to REQ_OP
  • From: mchristi@xxxxxxxxxx
• [PATCH 19/35] dm: set bi_op to REQ_OP
  • From: mchristi@xxxxxxxxxx
• [PATCH 23/35] md/raid: set bi_op to REQ_OP
  • From: mchristi@xxxxxxxxxx
• [PATCH 22/35] drbd: set bi_op to REQ_OP
  • From: mchristi@xxxxxxxxxx
• [PATCH 24/35] xen: set bi_op to REQ_OP
  • From: mchristi@xxxxxxxxxx
• [PATCH 26/35] block: set op to REQ_OP
  • From: mchristi@xxxxxxxxxx
• [PATCH 25/35] target: set bi_op to REQ_OP
  • From: mchristi@xxxxxxxxxx
• [PATCH 27/35] drivers: set request op to REQ_OP
  • From: mchristi@xxxxxxxxxx
• Re: 6TB partition, Data only 2TB - aka When you haven't hit the "usual" problem
  • From: Henk Slager <eye1tm@xxxxxxxxx>
• [PATCH 29/35] ide cd: do not set REQ_WRITE on requests.
  • From: mchristi@xxxxxxxxxx
• [PATCH 30/35] block, fs, drivers: do not test bi_rw for REQ_OPs
  • From: mchristi@xxxxxxxxxx
• [PATCH 28/35] blktrace: get op from req->op/bio->bi_op
  • From: mchristi@xxxxxxxxxx
• [PATCH 32/35] block: shrink bi_rw and bi_op
  • From: mchristi@xxxxxxxxxx
• [PATCH 33/35] block, drivers: add REQ_OP_FLUSH operation
  • From: mchristi@xxxxxxxxxx
• [PATCH 31/35] block, fs: remove old REQ definitions.
  • From: mchristi@xxxxxxxxxx
• [PATCH 34/35] block: add QUEUE_FLAGs for flush and fua
  • From: mchristi@xxxxxxxxxx
• [PATCH 35/35] block, drivers, fs: rename REQ_FLUSH to REQ_PREFLUSH
  • From: mchristi@xxxxxxxxxx
• [PATCH 03/35] block, fs, mm, drivers: set bi_op to REQ_OP
  • From: mchristi@xxxxxxxxxx
• [PATCH] Btrfs-progs: use btrfs-debugfs to fetch block group information
  • From: Liu Bo <bo.li.liu@xxxxxxxxxx>
• Re: 6TB partition, Data only 2TB - aka When you haven't hit the "usual" problem
  • From: Henk Slager <eye1tm@xxxxxxxxx>
• Re: 6TB partition, Data only 2TB - aka When you haven't hit the "usual" problem
  • From: "cheater00 ." <cheater00@xxxxxxxxx>
• Re: 6TB partition, Data only 2TB - aka When you haven't hit the "usual" problem
  • From: "cheater00 ." <cheater00@xxxxxxxxx>
• Re: [PATCH] BTRFS: Adds an option to select RAID Stripe size
  • From: Hugo Mills <hugo@xxxxxxxxxxxxx>
• Re: [PATCH] BTRFS: Adds an option to select RAID Stripe size
  • From: Christoph Anton Mitterer <calestyo@xxxxxxxxxxxx>
• Re: [PATCH] btrfs-progs: Format change for btrfs fi df
  • From: David Sterba <dsterba@xxxxxxx>
• Re: [PATCH] BTRFS: Adds an option to select RAID Stripe size
  • From: Sanidhya Solanki <jpage.lkml@xxxxxxxxx>
• Re: [PATCH] BTRFS: Adds an option to select RAID Stripe size
  • From: Christoph Anton Mitterer <calestyo@xxxxxxxxxxxx>
• Re: [PATCH] btrfs-corrupt-blocks: Include limits.h
  • From: David Sterba <dsterba@xxxxxxx>
• Re: Purposely using btrfs RAID1 in degraded mode ?
  • From: Psalle <psalleetsile@xxxxxxxxx>
• Re: 6TB partition, Data only 2TB - aka When you haven't hit the "usual" problem
  • From: "Austin S. Hemmelgarn" <ahferroin7@xxxxxxxxx>
• Re: 6TB partition, Data only 2TB - aka When you haven't hit the "usual" problem
  • From: "cheater00 ." <cheater00@xxxxxxxxx>
• Re: [GIT PULL] More btrfs bug fixes for 4.5
  • From: Chris Mason <clm@xxxxxx>
• Re: [PULL] Btrfs: cleanups for 4.5
  • From: Chris Mason <clm@xxxxxx>
• Re: 6TB partition, Data only 2TB - aka When you haven't hit the "usual" problem
  • From: "cheater00 ." <cheater00@xxxxxxxxx>
• Re: 6TB partition, Data only 2TB - aka When you haven't hit the "usual" problem
  • From: "cheater00 ." <cheater00@xxxxxxxxx>
• [PATCH v3] fstests: fix btrfs test failures after commit 27d077ec0bda
  • From: fdmanana@xxxxxxxxxx
• Re: 6TB partition, Data only 2TB - aka When you haven't hit the "usual" problem
  • From: "cheater00 ." <cheater00@xxxxxxxxx>
• Re: 6TB partition, Data only 2TB - aka When you haven't hit the "usual" problem
  • From: "Austin S. Hemmelgarn" <ahferroin7@xxxxxxxxx>
• Re: 6TB partition, Data only 2TB - aka When you haven't hit the "usual" problem
  • From: "cheater00 ." <cheater00@xxxxxxxxx>
• Re: send/receive for encrypted backup purposes
  • From: "Austin S. Hemmelgarn" <ahferroin7@xxxxxxxxx>
• Re: btrfs fail behavior when a device vanishes
  • From: Anand Jain <anand.jain@xxxxxxxxxx>
• Re: [PATCH] btrfs-progs: chunk-recovery: Fix a float point error
  • From: David Sterba <dsterba@xxxxxxx>
• Re: 6TB partition, Data only 2TB - aka When you haven't hit the "usual" problem
  • From: Hugo Mills <hugo@xxxxxxxxxxxxx>
• Re: 6TB partition, Data only 2TB - aka When you haven't hit the "usual" problem
  • From: "cheater00 ." <cheater00@xxxxxxxxx>
• Re: 6TB partition, Data only 2TB - aka When you haven't hit the "usual" problem
  • From: "cheater00 ." <cheater00@xxxxxxxxx>
• Re: 6TB partition, Data only 2TB - aka When you haven't hit the "usual" problem
  • From: "cheater00 ." <cheater00@xxxxxxxxx>
• Re: [PATCH 1/4 v2] fstests: fix btrfs test failures after commit 27d077ec0bda
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: [PATCH] btrfs-progs: chunk-recovery: Fix a float point error
  • From: Qu Wenruo <quwenruo@xxxxxxxxxxxxxx>
• Re: Recovery of a raid1 FS
  • From: Qu Wenruo <quwenruo@xxxxxxxxxxxxxx>
• Re: [PATCH] BTRFS: Adds an option to select RAID Stripe size
  • From: Qu Wenruo <quwenruo@xxxxxxxxxxxxxx>
• Re: 6TB partition, Data only 2TB - aka When you haven't hit the "usual" problem
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: 6TB partition, Data only 2TB - aka When you haven't hit the "usual" problem
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: 6TB partition, Data only 2TB - aka When you haven't hit the "usual" problem
  • From: "cheater00 ." <cheater00@xxxxxxxxx>
• Re: 6TB partition, Data only 2TB - aka When you haven't hit the "usual" problem
  • From: Lionel Bouton <lionel-subscription@xxxxxxxxxxx>
• Re: 6TB partition, Data only 2TB - aka When you haven't hit the "usual" problem
  • From: "cheater00 ." <cheater00@xxxxxxxxx>
• Re: evidence of persistent state, despite device disconnects
  • From: Goffredo Baroncelli <kreijack@xxxxxxxxx>
• Re: 6TB partition, Data only 2TB - aka When you haven't hit the "usual" problem
  • From: Henk Slager <eye1tm@xxxxxxxxx>
• Re: [dm-devel] [PATCH 02/35] block: add REQ_OP definitions and bi_op/op fields
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• Re: [dm-devel] [PATCH 02/35] block: add REQ_OP definitions and bi_op/op fields
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• Re: [PATCH] BTRFS: Adds an option to select RAID Stripe size
  • From: Sanidhya Solanki <jpage.lkml@xxxxxxxxx>
• Re: 6TB partition, Data only 2TB - aka When you haven't hit the "usual" problem
  • From: Russell Coker <russell@xxxxxxxxxxxx>
• Re: evidence of persistent state, despite device disconnects
  • From: Duncan <1i5t5.duncan@xxxxxxx>
• Re: 6TB partition, Data only 2TB - aka When you haven't hit the "usual" problem
  • From: "cheater00 ." <cheater00@xxxxxxxxx>
• [PATCH] btrfs-corrupt-blocks: Include limits.h
  • From: Khem Raj <raj.khem@xxxxxxxxx>
• Re: [dm-devel] [PATCH 02/35] block: add REQ_OP definitions and bi_op/op fields
  • From: Mike Christie <michaelc@xxxxxxxxxxx>
• Re: [dm-devel] [PATCH 02/35] block: add REQ_OP definitions and bi_op/op fields
  • From: Mike Christie <michaelc@xxxxxxxxxxx>
• Re: [PATCH 01/35] block/fs/drivers: remove rw argument from submit_bio
  • From: Mike Christie <michaelc@xxxxxxxxxxx>
• Reproduced deadlock after upgrade from 3.18 to 4.1 or 4.3 (+ more info)
  • From: Roman Mamedov <rm@xxxxxxxxxxx>
• Re: evidence of persistent state, despite device disconnects
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: 6TB partition, Data only 2TB - aka When you haven't hit the "usual" problem
  • From: Hugo Mills <hugo@xxxxxxxxxxxxx>
• Re: 6TB partition, Data only 2TB - aka When you haven't hit the "usual" problem
  • From: "cheater00 ." <cheater00@xxxxxxxxx>
• Re: 6TB partition, Data only 2TB - aka When you haven't hit the "usual" problem
  • From: Hugo Mills <hugo@xxxxxxxxxxxxx>
• Re: 6TB partition, Data only 2TB - aka When you haven't hit the "usual" problem
  • From: "cheater00 ." <cheater00@xxxxxxxxx>
• Re: 6TB partition, Data only 2TB - aka When you haven't hit the "usual" problem
  • From: Hugo Mills <hugo@xxxxxxxxxxxxx>
• Re: 6TB partition, Data only 2TB - aka When you haven't hit the "usual" problem
  • From: "cheater00 ." <cheater00@xxxxxxxxx>
• Re: send/receive for encrypted backup purposes
  • From: Christoph Biedl <linux-kernel.bfrz@xxxxxxxxxxxxxxxxxx>
• Re: [PATCH 26/35] block: set op to REQ_OP
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• Re: [PATCH 02/35] block: add REQ_OP definitions and bi_op/op fields
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• Re: [PATCH 01/35] block/fs/drivers: remove rw argument from submit_bio
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• Re: evidence of persistent state, despite device disconnects
  • From: Duncan <1i5t5.duncan@xxxxxxx>
• Re: Purposely using btrfs RAID1 in degraded mode ?
  • From: Duncan <1i5t5.duncan@xxxxxxx>
• Re: Filesystem hang on kernel 4.2.0 with copy reflink
  • From: Duncan <1i5t5.duncan@xxxxxxx>
• Re: [PATCH 34/35] block: add QUEUE_FLAGs for flush and fua
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• Re: Recovery of a raid1 FS
  • From: Tom Hunt <tomdicksonhunt@xxxxxxxxx>
• Re: [PATCH 00/35 v2] separate operations from flags in the bio/request structs
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [josef-btrfs:enospc-rework 7/8] fs/btrfs/extent-tree.c:5292:33: error: 'fs_info' undeclared
  • From: kbuild test robot <fengguang.wu@xxxxxxxxx>
• Re: [PATCH 00/35 v2] separate operations from flags in the bio/request structs
  • From: Mike Christie <michaelc@xxxxxxxxxxx>
• Re: send/receive for encrypted backup purposes
  • From: "Austin S. Hemmelgarn" <ahferroin7@xxxxxxxxx>
• Re: send/receive for encrypted backup purposes
  • From: "Austin S. Hemmelgarn" <ahferroin7@xxxxxxxxx>
• Re: send/receive for encrypted backup purposes
  • From: Christoph Anton Mitterer <calestyo@xxxxxxxxxxxx>