XFS

• Thread Index

• Re: xfsprogs for-next build error on Debian Wheezy / amd64
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• Re: xfsprogs for-next build error on Debian Wheezy / amd64
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: xfsprogs for-next build error on Debian Wheezy / amd64
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• Re: xfsprogs for-next build error on Debian Wheezy / amd64
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• Re: xfsprogs for-next build error on Debian Wheezy / amd64
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• xfsprogs for-next build error on Debian Wheezy / amd64
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• [ANNOUNCE] xfsprogs: v3.2.3 released
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: simplify transaction commit and cancel interfaces V2
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: [PATCH 4/4 V2] xfsprogs: zero out clean log in xfs_metadump
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: XFS Syncd
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: XFS Syncd
  • From: Shrinand Javadekar <shrinand@xxxxxxxxxxxxxx>
• Re: [PATCH 4/4 V3] xfsprogs: zero out clean log in xfs_metadump
  • From: Brian Foster <bfoster@xxxxxxxxxx>
• Re: [PATCH 4/4 V3] xfsprogs: zero out clean log in xfs_metadump
  • From: Eric Sandeen <sandeen@xxxxxxxxxxx>
• Re: [PATCH 4/4 V2] xfsprogs: zero out clean log in xfs_metadump
  • From: Eric Sandeen <sandeen@xxxxxxxxxxx>
• Re: [PATCH 4/4 V2] xfsprogs: zero out clean log in xfs_metadump
  • From: Brian Foster <bfoster@xxxxxxxxxx>
• Re: High %sy cpu usage , server is very slow
  • From: Emmanuel Florac <eflorac@xxxxxxxxxxxxxx>
• [PATCH 4/4 V2] xfsprogs: zero out clean log in xfs_metadump
  • From: Eric Sandeen <sandeen@xxxxxxxxxxx>
• Re: [PATCH] xfs: fix in the setting of logbsize
  • From: Mark Tinguely <tinguely@xxxxxxx>
• [PATCH 1/4] repair: access helpers for on-disk inobt record freecount
  • From: Brian Foster <bfoster@xxxxxxxxxx>
• [PATCH 4/4] repair: helper to transition inode blocks to inode state
  • From: Brian Foster <bfoster@xxxxxxxxxx>
• [PATCH 3/4] repair: helper to import on-disk inobt records to in-core trees
  • From: Brian Foster <bfoster@xxxxxxxxxx>
• [PATCH 2/4] repair: helper for inode chunk alignment and start/end ino number verification
  • From: Brian Foster <bfoster@xxxxxxxxxx>
• [PATCH 0/4] xfsprogs/repair: sparse inode chunks cleanups
  • From: Brian Foster <bfoster@xxxxxxxxxx>
• High %sy cpu usage , server is very slow
  • From: Aravind M D <aravind@xxxxxxxx>
• Re: [PATCH] xfs: fix in the setting of logbsize
  • From: Ales Novak <alnovak@xxxxxxx>
• Re: [PATCH] xfs: fix in the setting of logbsize
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: [PATCH] xfs: fix in the setting of logbsize
  • From: Eric Sandeen <sandeen@xxxxxxxxxxx>
• Re: [PATCH] xfs: fix in the setting of logbsize
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: XFS Syncd
  • From: Shrinand Javadekar <shrinand@xxxxxxxxxxxxxx>
• Re: [PATCH 19/28] repair: scan sparse finobt records correctly
  • From: Brian Foster <bfoster@xxxxxxxxxx>
• [PATCH] xfs: fix in the setting of logbsize
  • From: Ales Novak <alnovak@xxxxxxx>
• [ANNOUNCE] xfsprogs: for-next branch created
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: [PATCH] xfsprogs: silence unused var warnings
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: [PATCH 21/28] repair: process sparse inode records correctly
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: [PATCH 19/28] repair: scan sparse finobt records correctly
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: XFS Syncd
  • From: Shrinand Javadekar <shrinand@xxxxxxxxxxxxxx>
• Re: [PATCH 18/28] repair: scan and track sparse inode chunks correctly
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: [PATCH 15/28] repair: handle sparse format inobt record freecount correctly
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: linux-next: Tree for Jun 4 (radeonfb && xfs)
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• [ANNOUNCE] xfs: for-next branch updated to 4ea7976
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: Rules for calling ->releasepage()
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: XFS Syncd
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: linux-next: Tree for Jun 4 (radeonfb && xfs)
  • From: Randy Dunlap <rdunlap@xxxxxxxxxxxxx>
• Re: [PATCH] xfstests/xfs: test inode allocation with fragmented free space
  • From: Brian Foster <bfoster@xxxxxxxxxx>
• Re: Rules for calling ->releasepage()
  • From: Andreas Dilger <adilger@xxxxxxxxx>
• Rules for calling ->releasepage()
  • From: Jan Kara <jack@xxxxxxx>
• Re: XFS Syncd
  • From: Shrinand Javadekar <shrinand@xxxxxxxxxxxxxx>
• Re: XFS Syncd
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: randconfig build error with next-20150603, in fs/xfs/xfs_inode.c
  • From: Paul Gortmaker <paul.gortmaker@xxxxxxxxxxxxx>
• Re: randconfig build error with next-20150603, in fs/xfs/xfs_inode.c
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: randconfig build error with next-20150603, in fs/xfs/xfs_inode.c
  • From: Paul Gortmaker <paul.gortmaker@xxxxxxxxxxxxx>
• Re: XFS Syncd
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: XFS Syncd
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: XFS Syncd
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: XFS Syncd
  • From: Shrinand Javadekar <shrinand@xxxxxxxxxxxxxx>
• Re: XFS Syncd
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: XFS Syncd
  • From: Shrinand Javadekar <shrinand@xxxxxxxxxxxxxx>
• Re: "XFS: possible memory allocation deadlock in kmem_alloc" on high memory machine
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: [PATCH] [RFC v2] xfs: byte range buffer dirty region tracking
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: [PATCH] [RFC v2] xfs: byte range buffer dirty region tracking
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: [PATCH] xfstests/xfs: test inode allocation with fragmented free space
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: [PATCH 0/2 V3] allow UUID changes on V5/CRC filesystems
  • From: Eric Sandeen <sandeen@xxxxxxxxxxx>
• Re: [PATCH 4/4] xfsprogs: zero out clean log in xfs_metadump
  • From: Eric Sandeen <sandeen@xxxxxxxxxxx>
• [PATCH] xfstests/xfs: test inode allocation with fragmented free space
  • From: Brian Foster <bfoster@xxxxxxxxxx>
• Re: [PATCH 4/4] xfsprogs: zero out clean log in xfs_metadump
  • From: Brian Foster <bfoster@xxxxxxxxxx>
• Re: [PATCH 3/4] xfsprogs: rename dont_obfuscate in xfs_metadump
  • From: Brian Foster <bfoster@xxxxxxxxxx>
• Re: [PATCH 2/4] xfsprogs: add xlog_is_empty() helper
  • From: Brian Foster <bfoster@xxxxxxxxxx>
• Re: [PATCH 1/4] xfsprogs: remove unused write-only var l_logsize
  • From: Brian Foster <bfoster@xxxxxxxxxx>
• randconfig build error with next-20150603, in fs/xfs/xfs_inode.c
  • From: Jim Davis <jim.epost@xxxxxxxxx>
• Re: [PATCH] [RFC v2] xfs: byte range buffer dirty region tracking
  • From: Mark Tinguely <tinguely@xxxxxxx>
• Re: [PATCH] [RFC v2] xfs: byte range buffer dirty region tracking
  • From: Brian Foster <bfoster@xxxxxxxxxx>
• [PATCH 5/5] xfs: fix xfs_log_done interface
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH 4/5] xfs: saner xfs_trans_commit interface
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH 3/5] xfs: remove the flags argument to xfs_trans_cancel
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH 2/5] xfs: pass a boolean flag to xfs_trans_free_items
  • From: Christoph Hellwig <hch@xxxxxx>
• simplify transaction commit and cancel interfaces V2
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH 1/5] xfs: switch remaining xfs_trans_dup users to xfs_trans_roll
  • From: Christoph Hellwig <hch@xxxxxx>
• Re: [PATCH 0/2 V3] allow UUID changes on V5/CRC filesystems
  • From: Linda Walsh <xfs@xxxxxxxxx>
• Re: "XFS: possible memory allocation deadlock in kmem_alloc" on high memory machine
  • From: Anders Ossowicki <aowi@xxxxxxxxxxxxx>
• Re: [PATCH 05/20] xfs: introduce rmap btree definitions
  • From: "Darrick J. Wong" <darrick.wong@xxxxxxxxxx>
• Re: [PATCH 05/20] xfs: introduce rmap btree definitions
  • From: "Darrick J. Wong" <darrick.wong@xxxxxxxxxx>
• [PATCH 14/20] xfs: add rmap btree operations
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• [PATCH 04/20] xfs: clean up XFS_MIN_FREELIST macros
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• [PATCH 13/20] xfs: rmap btree requires more reserved free space
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• [PATCH 01/20] xfs: xfs_alloc_fix_freelist() can use incore perag structures
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• [PATCH 03/20] xfs: sanitise error handling in xfs_alloc_fix_freelist
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• [PATCH 08/20] xfs: add owner field to extent allocation and freeing
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• [PATCH 09/20] xfs: introduce rmap extent operation stubs
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• [PATCH 17/20] xfs: add rmap btree geometry feature flag
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• [PATCH 07/20] xfs: rmap btree add more reserved blocks
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• [PATCH 16/20] xfs: remove an extent from the rmap btree
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• [PATCH 19/20] xfs: disable XFS_IOC_SWAPEXT when rmap btree is enabled
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• [PATCH 10/20] xfs: define the on-disk rmap btree format
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• [PATCH 18/20] xfs: add rmap btree block detection to log recovery
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• [PATCH 15/20] xfs: add an extent to the rmap btree
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• [PATCH 06/20] xfs: add rmap btree stats infrastructure
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• [PATCH 02/20] xfs: factor out free space extent length check
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• [PATCH 12/20] xfs: rmap btree transaction reservations
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• [PATCH 20/20] xfs: enable the rmap btree functionality
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• [PATCH 11/20] xfs: add rmap btree growfs support
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• [RFC PATCH 00/20] xfs: reverse mapping btree support
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• [PATCH 05/20] xfs: introduce rmap btree definitions
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: XFS Syncd
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: "XFS: possible memory allocation deadlock in kmem_alloc" on high memory machine
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: [PATCH 5/8 v2] xfs: add DAX block zeroing support
  • From: Brian Foster <bfoster@xxxxxxxxxx>
• [PATCH 5/8 v2] xfs: add DAX block zeroing support
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• [PATCH 04/28] xfs: add sparse inode chunk alignment superblock field
  • From: Brian Foster <bfoster@xxxxxxxxxx>
• [PATCH 00/28] xfsprogs: sparse inode chunks
  • From: Brian Foster <bfoster@xxxxxxxxxx>
• Re: XFS Syncd
  • From: Shrinand Javadekar <shrinand@xxxxxxxxxxxxxx>
• [PATCH 12/28] db: support sparse inode chunk inobt record and sb fields
  • From: Brian Foster <bfoster@xxxxxxxxxx>
• [PATCH 02/28] xfs: update free inode record logic to support sparse inode records
  • From: Brian Foster <bfoster@xxxxxxxxxx>
• [PATCH 05/28] xfs: use sparse chunk alignment for min. inode allocation requirement
  • From: Brian Foster <bfoster@xxxxxxxxxx>
• [PATCH 03/28] xfs: support min/max agbno args in block allocator
  • From: Brian Foster <bfoster@xxxxxxxxxx>
• [PATCH 18/28] repair: scan and track sparse inode chunks correctly
  • From: Brian Foster <bfoster@xxxxxxxxxx>
• [PATCH 25/28] repair: do not prefetch holes in sparse inode chunks
  • From: Brian Foster <bfoster@xxxxxxxxxx>
• [PATCH 20/28] repair: validate ir_count field for sparse format records
  • From: Brian Foster <bfoster@xxxxxxxxxx>
• [PATCH 21/28] repair: process sparse inode records correctly
  • From: Brian Foster <bfoster@xxxxxxxxxx>
• [PATCH 08/28] xfs: introduce inode record hole mask for sparse inode chunks
  • From: Brian Foster <bfoster@xxxxxxxxxx>
• [PATCH 28/28] metadump: support sparse inode records
  • From: Brian Foster <bfoster@xxxxxxxxxx>
• [PATCH 13/28] db: show sparse inodes feature state in version command output
  • From: Brian Foster <bfoster@xxxxxxxxxx>
• [PATCH 16/28] repair: remove duplicate field from aghdr_cnts
  • From: Brian Foster <bfoster@xxxxxxxxxx>
• [PATCH 11/28] mkfs: sparse inode chunk support
  • From: Brian Foster <bfoster@xxxxxxxxxx>
• [PATCH 15/28] repair: handle sparse format inobt record freecount correctly
  • From: Brian Foster <bfoster@xxxxxxxxxx>
• [PATCH 22/28] repair: factor out sparse inodes from finobt reconstruction
  • From: Brian Foster <bfoster@xxxxxxxxxx>
• [PATCH 19/28] repair: scan sparse finobt records correctly
  • From: Brian Foster <bfoster@xxxxxxxxxx>
• [PATCH 24/28] repair: reconstruct sparse inode records correctly on disk
  • From: Brian Foster <bfoster@xxxxxxxxxx>
• [PATCH 27/28] metadump: reorder inode record sanity checks and inode buffer read
  • From: Brian Foster <bfoster@xxxxxxxxxx>
• [PATCH 14/28] growfs: display sparse inode status from xfs_info
  • From: Brian Foster <bfoster@xxxxxxxxxx>
• [PATCH 06/28] xfs: sparse inode chunks feature helpers and mount requirements
  • From: Brian Foster <bfoster@xxxxxxxxxx>
• [PATCH 26/28] repair: handle sparse inode alignment
  • From: Brian Foster <bfoster@xxxxxxxxxx>
• [PATCH 23/28] repair: do not account sparse inodes in phase 5 cursor init.
  • From: Brian Foster <bfoster@xxxxxxxxxx>
• [PATCH 09/28] xfs: pass inode count through ordered icreate log item
  • From: Brian Foster <bfoster@xxxxxxxxxx>
• [PATCH 17/28] repair: use ir_count for filesystems with sparse inode support
  • From: Brian Foster <bfoster@xxxxxxxxxx>
• [PATCH 10/28] xfs: enable sparse inode chunks for v5 superblocks
  • From: Brian Foster <bfoster@xxxxxxxxxx>
• [PATCH 07/28] xfs: add fs geometry bit for sparse inode chunks
  • From: Brian Foster <bfoster@xxxxxxxxxx>
• [PATCH 01/28] xfs: create individual inode alloc. helper
  • From: Brian Foster <bfoster@xxxxxxxxxx>
• Re: [PATCH 5/8] xfs: add DAX block zeroing support
  • From: Brian Foster <bfoster@xxxxxxxxxx>
• Re: [PATCH 4/8] xfs: add DAX file operations support
  • From: Brian Foster <bfoster@xxxxxxxxxx>
• Re: "XFS: possible memory allocation deadlock in kmem_alloc" on high memory machine
  • From: Anders Ossowicki <aowi@xxxxxxxxxxxxx>
• Re: [PATCH v5 00/18] xfs: sparse inode chunks
  • From: Brian Foster <bfoster@xxxxxxxxxx>
• [PATCH v2] xfs: fix sparse inodes 32-bit compile failure
  • From: Brian Foster <bfoster@xxxxxxxxxx>
• Re: "XFS: possible memory allocation deadlock in kmem_alloc" on high memory machine
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: [PATCH 1/2] xfs: fix sparse inodes 32-bit compile failure
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: Overwritten partition
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: [PATCH v5 00/18] xfs: sparse inode chunks
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: Overwritten partition
  • From: Greg Freemyer <greg.freemyer@xxxxxxxxx>
• "XFS: possible memory allocation deadlock in kmem_alloc" on high memory machine
  • From: Anders Ossowicki <aowi@xxxxxxxxxxxxx>
• [PATCH 1/2] xfs: fix sparse inodes 32-bit compile failure
  • From: Brian Foster <bfoster@xxxxxxxxxx>
• [PATCH 2/2] xfs: check min blks for random debug mode sparse allocations
  • From: Brian Foster <bfoster@xxxxxxxxxx>
• [PATCH 0/2] xfs: fix a couple post-merge sparse inode chunks issues
  • From: Brian Foster <bfoster@xxxxxxxxxx>
• Re: [dgc-xfs:xfs-sparse-inode 17/18] xfs_inode.c:undefined reference to `__umoddi3'
  • From: Brian Foster <bfoster@xxxxxxxxxx>
• Re: [PATCH v5 00/18] xfs: sparse inode chunks
  • From: Brian Foster <bfoster@xxxxxxxxxx>
• Re: Overwritten partition
  • From: Emmanuel Florac <eflorac@xxxxxxxxxxxxxx>
• Re: xfs_repair segfault + debug info
  • From: Mike Grant <mggr@xxxxxxxxx>
• [ANNOUNCE] xfs: for-next branch updated to b9a350a
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• [ANNOUNCE] xfsprogs v3.2.3-rc2: master branch updated to 29358c9
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: [PATCH v5 00/18] xfs: sparse inode chunks
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: [PATCH v2 2/5] xfs_repair: better checking of v5 metadata fields
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• [PATCH 2/2] fs: xfs: xfs_trans_dquot: Add missing space according to coding style
  • From: Nan Jia <jiananmail@xxxxxxxxx>
• [PATCH 2/2] fs: xfs: xfs_trans_dquot: Add missing space according to coding style
  • From: Nan Jia <jiananmail@xxxxxxxxx>
• [PATCH 2/2] fs: xfs: xfs_trans_dquot: Add missing space according to coding style
  • From: Nan Jia <jiananmail@xxxxxxxxx>
• Overwritten partition
  • From: hallexh@xxxxxxxxx
• Re: [ANNOUNCE] xfs: for-next branch updated to cddc116
  • From: Brian Foster <bfoster@xxxxxxxxxx>
• re:re: led ceiling lamp lighiting price list
  • From: "ledlighting11@xxxxxxxxxxxxxxxxxxxxx" <ledlighting11@xxxxxxxxxxxxxxxxxxxxx>
• [GIT PULL] xfs: update for v4.1-rc6
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: generic/247 triggers warnings occasionally
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: [ANNOUNCE] xfs: for-next branch updated to cddc116
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: xfs_repair segfault + debug info
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• [PATCH 4/4] xfsprogs: zero out clean log in xfs_metadump
  • From: Eric Sandeen <sandeen@xxxxxxxxxxx>
• [PATCH 3/4] xfsprogs: rename dont_obfuscate in xfs_metadump
  • From: Eric Sandeen <sandeen@xxxxxxxxxxx>
• [PATCH 2/4] xfsprogs: add xlog_is_empty() helper
  • From: Eric Sandeen <sandeen@xxxxxxxxxxx>
• [PATCH 1/4] xfsprogs: remove unused write-only var l_logsize
  • From: Eric Sandeen <sandeen@xxxxxxxxxxx>
• [PATCH 0/4] xfsprogs: mini patch-bomb
  • From: Eric Sandeen <sandeen@xxxxxxxxxx>
• Re: generic/247 triggers warnings occasionally
  • From: Brian Foster <bfoster@xxxxxxxxxx>
• Re: [PATCH, RESEND] xfs: fix kernel version in docs
  • From: Fanael Linithien <fanael4@xxxxxxxxx>
• xfs_repair segfault + debug info
  • From: Mike Grant <mggr@xxxxxxxxx>
• Re: [ANNOUNCE] xfs: for-next branch updated to cddc116
  • From: Brian Foster <bfoster@xxxxxxxxxx>
• Re: generic/247 triggers warnings occasionally
  • From: Eryu Guan <eguan@xxxxxxxxxx>
• generic/247 triggers warnings occasionally
  • From: Eryu Guan <eguan@xxxxxxxxxx>
• [PATCH] [RFC v2] xfs: byte range buffer dirty region tracking
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: [PATCH] xfsprogs: merge the duplicated condition in xfs_mkfs.c/validate_ag_geometry
  • From: Wang Sheng-Hui <shhuiw@xxxxxxxxxxx>
• [PATCH 4/8] xfs: add DAX file operations support
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• [PATCH 5/8] xfs: add DAX block zeroing support
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• [PATCH 2/8] dax: don't abuse get_block mapping for endio callbacks
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• [PATCH 7/8] xfs: add DAX IO path support
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• [PATCH 3/8] dax: expose __dax_fault for filesystems with locking constraints
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• [PATCH 8/8] xfs: add initial DAX support
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• [PATCH 6/8] xfs: add DAX truncate support
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• [PATCH 0/8 v3] xfs: DAX support
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• [PATCH 1/8] xfs: mmap lock needs to be inside freeze protection
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: [ANNOUNCE] xfs: for-next branch updated to cddc116
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: [PATCH, RESEND] xfs: fix kernel version in docs
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• [ANNOUNCE] xfs: for-next branch updated to cddc116
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• [PATCH 2/3] xfs: remove entire inode chunks when all inodes are free
  • From: Brian Foster <bfoster@xxxxxxxxxx>
• [PATCH 3/3] xfs: inobt record insert/delete tracepoints
  • From: Brian Foster <bfoster@xxxxxxxxxx>
• [PATCH 1/3] xfs: create helper to delete multiple inobt records
  • From: Brian Foster <bfoster@xxxxxxxxxx>
• [PATCH 0/3] xfs: support removal of multi-record inode chunks
  • From: Brian Foster <bfoster@xxxxxxxxxx>
• Re: XFS crashes on VMs
  • From: Shrinand Javadekar <shrinand@xxxxxxxxxxxxxx>
• Re: [PATCH] xfsprogs: merge the duplicated condition in xfs_mkfs.c/validate_ag_geometry
  • From: Eric Sandeen <sandeen@xxxxxxxxxxx>
• [PATCH] xfsprogs: merge the duplicated condition in xfs_mkfs.c/validate_ag_geometry
  • From: Wang Sheng-Hui <shhuiw@xxxxxxxxxxx>
• Re: [PATCH 5/5] xfs_db: enable blocktrash for checksummed filesystems
  • From: "Darrick J. Wong" <darrick.wong@xxxxxxxxxx>
• Re: XFS crashes on VMs
  • From: Eric Sandeen <sandeen@xxxxxxxxxxx>
• Re: XFS crashes on VMs
  • From: Eric Sandeen <sandeen@xxxxxxxxxxx>
• Re: XFS crashes on VMs
  • From: Shrinand Javadekar <shrinand@xxxxxxxxxxxxxx>
• Re: XFS crashes on VMs
  • From: Eric Sandeen <sandeen@xxxxxxxxxxx>
• XFS crashes on VMs
  • From: Shrinand Javadekar <shrinand@xxxxxxxxxxxxxx>
• Re: [PATCH v3 1/5] xfs_repair: refuse to run if we don't recognize version or feature flags
  • From: Fanael Linithien <fanael4@xxxxxxxxx>
• [PATCH v3 1/5] xfs_repair: refuse to run if we don't recognize version or feature flags
  • From: "Darrick J. Wong" <darrick.wong@xxxxxxxxxx>
• Re: [PATCH v2 1/5] xfs_repair: refuse to run if we don't recognize version or feature flags
  • From: "Darrick J. Wong" <darrick.wong@xxxxxxxxxx>
• Re: [PATCH v2 1/5] xfs_repair: refuse to run if we don't recognize version or feature flags
  • From: "Darrick J. Wong" <darrick.wong@xxxxxxxxxx>
• Re: [PATCH v2 1/5] xfs_repair: refuse to run if we don't recognize version or feature flags
  • From: Eric Sandeen <sandeen@xxxxxxxxxxx>
• Re: [PATCH v2 1/5] xfs_repair: refuse to run if we don't recognize version or feature flags
  • From: Fanael Linithien <fanael4@xxxxxxxxx>
• Re: [PATCH v2 1/5] xfs_repair: refuse to run if we don't recognize version or feature flags
  • From: Eric Sandeen <sandeen@xxxxxxxxxxx>
• Re: [PATCH v2 1/5] xfs_repair: refuse to run if we don't recognize version or feature flags
  • From: Eric Sandeen <sandeen@xxxxxxxxxxx>
• Re: [PATCH v2 1/5] xfs_repair: refuse to run if we don't recognize version or feature flags
  • From: Fanael Linithien <fanael4@xxxxxxxxx>
• Re: [PATCH v2 1/5] xfs_repair: refuse to run if we don't recognize version or feature flags
  • From: Eric Sandeen <sandeen@xxxxxxxxxxx>
• [PATCH, RESEND] xfs: fix kernel version in docs
  • From: Fanael Linithien <fanael4@xxxxxxxxx>
• Re: [PATCH v3] xfs: extent size hints can round up extents past MAXEXTLEN
  • From: Brian Foster <bfoster@xxxxxxxxxx>
• [PATCH v2 1/5] xfs_repair: refuse to run if we don't recognize version or feature flags
  • From: "Darrick J. Wong" <darrick.wong@xxxxxxxxxx>
• [PATCH v2 2/5] xfs_repair: better checking of v5 metadata fields
  • From: "Darrick J. Wong" <darrick.wong@xxxxxxxxxx>
• Re: [PATCH v3] xfs: extent size hints can round up extents past MAXEXTLEN
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: [PATCH 4/5] xfs: saner xfs_trans_commit interface
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• [PATCH v3] xfs: extent size hints can round up extents past MAXEXTLEN
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: [PATCH 2/5] xfs_repair: better checking of v5 metadata fields
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: [PATCH 1/5] xfs_repair: refuse to run if we don't recognize version or feature flags
  • From: Eric Sandeen <sandeen@xxxxxxxxxxx>
• Re: [PATCH 2/2] xfs: xfs_attr_inactive leaves inconsistent attr fork state behind
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• [PATCH v2 4/5] xfs_db: enable blockget for v5 filesystems
  • From: "Darrick J. Wong" <darrick.wong@xxxxxxxxxx>
• Re: [PATCH 4/5] xfs_db: enable blockget for v5 filesystems
  • From: "Darrick J. Wong" <darrick.wong@xxxxxxxxxx>
• Re: [PATCH 4/5] xfs_db: enable blockget for v5 filesystems
  • From: Eric Sandeen <sandeen@xxxxxxxxxxx>
• [PATCH 5/5] xfs_db: enable blocktrash for checksummed filesystems
  • From: "Darrick J. Wong" <darrick.wong@xxxxxxxxxx>
• [PATCH 4/5] xfs_db: enable blockget for v5 filesystems
  • From: "Darrick J. Wong" <darrick.wong@xxxxxxxxxx>
• [PATCH 3/5] xfs_repair: ensure .. is set to a sane ino value when rebuilding dir
  • From: "Darrick J. Wong" <darrick.wong@xxxxxxxxxx>
• [PATCH 2/5] xfs_repair: better checking of v5 metadata fields
  • From: "Darrick J. Wong" <darrick.wong@xxxxxxxxxx>
• [PATCH 1/5] xfs_repair: refuse to run if we don't recognize version or feature flags
  • From: "Darrick J. Wong" <darrick.wong@xxxxxxxxxx>
• [PATCH 0/5] xfsprogs May 2015 patchbomb
  • From: "Darrick J. Wong" <darrick.wong@xxxxxxxxxx>
• [PATCH] xfs: fix kernel version in docs
  • From: Fanael Linithien <fanael4@xxxxxxxxx>
• RE: xfs_repair fails
  • From: "Rhorer, Leslie" <Leslie.Rhorer@xxxxxxxxxx>
• Re: [Regression] Guest fs corruption with 'block: loop: improve performance via blk-mq'
  • From: santosh shilimkar <santosh.shilimkar@xxxxxxxxxx>
• Re: Let's get a File & Storage miniconf going at LPC2015!
  • From: "Darrick J. Wong" <darrick.wong@xxxxxxxxxx>
• Re: Let's get a File & Storage miniconf going at LPC2015!
  • From: Kent Overstreet <kent.overstreet@xxxxxxxxx>
• Re: inode64
  • From: Carlos Maiolino <cmaiolino@xxxxxxxxxx>
• inode64
  • From: Jerzy Borkowski <jubork@xxxxxxxxxxxxx>
• Re: xfsprogs/mkfs: what's the relationship between max trans res and min log size
  • From: Wang Sheng-Hui <shhuiw@xxxxxxxxxxx>
• Re: [PATCH 1/4 linux-next] xfs: use swap() in xfs_dir2_leafn_rebalance()
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: [PATCH 1/4 linux-next] xfs: use swap() in xfs_dir2_leafn_rebalance()
  • From: Al Viro <viro@xxxxxxxxxxxxxxxxxx>
• [PATCH] xfs/007: use gquotino for project quotas on pre-v5 superblocks
  • From: Brian Foster <bfoster@xxxxxxxxxx>
• Re: [PATCH 2/2 V5] xfsprogs: Add new sb_meta_uuid field, update userspace tools to manipulate it
  • From: Brian Foster <bfoster@xxxxxxxxxx>
• Re: xfsprogs/mkfs: what's the relationship between max trans res and min log size
  • From: Brian Foster <bfoster@xxxxxxxxxx>
• xfsprogs/mkfs: what's the relationship between max trans res and min log size
  • From: Wang Sheng-Hui <shhuiw@xxxxxxxxxxx>
• Let's get a File & Storage miniconf going at LPC2015!
  • From: "Darrick J. Wong" <darrick.wong@xxxxxxxxxx>
• [PATCH] xfs: fix broken i_nlink accounting for whiteout tmpfile inode
  • From: Brian Foster <bfoster@xxxxxxxxxx>
• Script to cross-apply libxfs changes
  • From: Eric Sandeen <sandeen@xxxxxxxxxx>
• [PATCH] xfsprogs: install PKGHFILES in install-dev
  • From: Eric Sandeen <sandeen@xxxxxxxxxx>
• Re: xfs_repair fails
  • From: Brian Foster <bfoster@xxxxxxxxxx>
• Re: xfs_repair fails
  • From: Emmanuel Florac <eflorac@xxxxxxxxxxxxxx>
• Re: [PATCH] xfstests/common/renameat2: pass the renameat2 flags from _rename_tests to _rename_tests_source_dest
  • From: Eryu Guan <eguan@xxxxxxxxxx>
• Re: [PATCH] xfstests/common/renameat2: pass the renameat2 flags from _rename_tests to _rename_tests_source_dest
  • From: Eryu Guan <eguan@xxxxxxxxxx>
• RE: xfs_repair fails
  • From: "Rhorer, Leslie" <Leslie.Rhorer@xxxxxxxxxx>
• Re: [PATCH] xfstests/common/renameat2: pass the renameat2 flags from _rename_tests to _rename_tests_source_dest
  • From: Wang Sheng-Hui <shhuiw@xxxxxxxxxxx>
• [PATCH 2/2 V5] xfsprogs: Add new sb_meta_uuid field, update userspace tools to manipulate it
  • From: Eric Sandeen <sandeen@xxxxxxxxxxx>
• [PATCH 1/2 V4] xfs: create new metadata UUID field and incompat flag
  • From: Eric Sandeen <sandeen@xxxxxxxxxxx>
• Re: [PATCH 1/2] xfs: create new metadata UUID field and incompat flag
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• [PATCH] xfsprogs: silence unused var warnings
  • From: Eric Sandeen <sandeen@xxxxxxxxxx>
• [PATCH 2/2 V4] xfsprogs: Add new sb_meta_uuid field, update userspace tools to manipulate it
  • From: Eric Sandeen <sandeen@xxxxxxxxxxx>
• Re: [PATCH 2/2] xfsprogs: Add new sb_meta_uuid field, update userspace tools to manipulate it
  • From: Eric Sandeen <sandeen@xxxxxxxxxxx>
• Re: [PATCH] xfs_repair: properly detect reserved attribute names
  • From: Eric Sandeen <sandeen@xxxxxxxxxx>
• Re: [PATCH 1/2] percpu_counter: batch size aware __percpu_counter_compare()
  • From: Tejun Heo <tj@xxxxxxxxxx>
• Re: [PATCH] xfs_repair: properly detect reserved attribute names
  • From: Brian Foster <bfoster@xxxxxxxxxx>
• Re: [PATCH] xfs: don't cast string literals
  • From: Brian Foster <bfoster@xxxxxxxxxx>
• Re: [PATCH 2/2] xfs: inode and free block counters need to use __percpu_counter_compare
  • From: Brian Foster <bfoster@xxxxxxxxxx>
• Re: [PATCH 2/2] xfsprogs: Add new sb_meta_uuid field, update userspace tools to manipulate it
  • From: Brian Foster <bfoster@xxxxxxxxxx>
• Re: [PATCH 1/2] xfs: create new metadata UUID field and incompat flag
  • From: Brian Foster <bfoster@xxxxxxxxxx>
• Re: xfs_repair fails
  • From: Brian Foster <bfoster@xxxxxxxxxx>
• xfs_repair fails
  • From: "Rhorer, Leslie" <Leslie.Rhorer@xxxxxxxxxx>
• [PATCH] xfs_repair: properly detect reserved attribute names
  • From: Eric Sandeen <sandeen@xxxxxxxxxx>
• Re: [ANNOUNCE, DISCUSS] xfsprogs: libxfs-4.1-update branch created
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: [PATCH 1/2] percpu_counter: batch size aware __percpu_counter_compare()
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• [PATCH] xfs: don't cast string literals
  • From: Eric Sandeen <sandeen@xxxxxxxxxx>
• Re: [ANNOUNCE, DISCUSS] xfsprogs: libxfs-4.1-update branch created
  • From: Eric Sandeen <sandeen@xxxxxxxxxxx>
• Re: [ANNOUNCE, DISCUSS] xfsprogs: libxfs-4.1-update branch created
  • From: Eric Sandeen <sandeen@xxxxxxxxxxx>
• Re: [ANNOUNCE, DISCUSS] xfsprogs: libxfs-4.1-update branch created
  • From: Eric Sandeen <sandeen@xxxxxxxxxxx>
• Re: [PATCH v2] xfs: log record crc mismatch test
  • From: Alexander Tsvetkov <alexander.tsvetkov@xxxxxxxxxx>
• Re: [PATCH 1/2] percpu_counter: batch size aware __percpu_counter_compare()
  • From: Tejun Heo <tj@xxxxxxxxxx>
• Re: any chance for xfs shrinking?
  • From: greg.freemyer@xxxxxxxxx
• [PATCH 2/2] xfs: inode and free block counters need to use __percpu_counter_compare
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• [PATCH 1/2] percpu_counter: batch size aware __percpu_counter_compare()
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• [PATCH 0/2 v2] percpu_counter: xfs requires custom compare batch size
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: any chance for xfs shrinking?
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• [PATCH 2/2] xfsprogs: Add new sb_meta_uuid field, update userspace tools to manipulate it
  • From: Eric Sandeen <sandeen@xxxxxxxxxxx>
• [PATCH 1/2] xfs: create new metadata UUID field and incompat flag
  • From: Eric Sandeen <sandeen@xxxxxxxxxxx>
• [PATCH 0/2 V3] allow UUID changes on V5/CRC filesystems
  • From: Eric Sandeen <sandeen@xxxxxxxxxxx>
• Re: any chance for xfs shrinking?
  • From: Andrey Korolyov <andrey@xxxxxxx>
• Re: any chance for xfs shrinking?
  • From: Stefan Priebe - Profihost AG <s.priebe@xxxxxxxxxxxx>
• Re: any chance for xfs shrinking?
  • From: Eric Sandeen <sandeen@xxxxxxxxxxx>
• Re: any chance for xfs shrinking?
  • From: Dewangga Bachrul Alam <dewanggaba@xxxxxxxxxxxxxxx>
• any chance for xfs shrinking?
  • From: Stefan Priebe - Profihost AG <s.priebe@xxxxxxxxxxxx>
• Re: [PATCH 1/2] xfs: create new metadata UUID field and incompat flag
  • From: Brian Foster <bfoster@xxxxxxxxxx>
• Re: [PATCH 4/5] xfs: saner xfs_trans_commit interface
  • From: Christoph Hellwig <hch@xxxxxx>
• Re: [PATCH 1/2] xfs: create new metadata UUID field and incompat flag
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: [PATCH 1/2] xfs: create new metadata UUID field and incompat flag
  • From: Eric Sandeen <sandeen@xxxxxxxxxxx>
• Re: [ANNOUNCE, DISCUSS] xfsprogs: libxfs-4.1-update branch created
  • From: Eric Sandeen <sandeen@xxxxxxxxxxx>
• Re: [PATCH 1/2] xfs: create new metadata UUID field and incompat flag
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: Inode and dentry cache behavior
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: [ANNOUNCE, DISCUSS] xfsprogs: libxfs-4.1-update branch created
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: Inode and dentry cache behavior
  • From: Shrinand Javadekar <shrinand@xxxxxxxxxxxxxx>
• Re: [PATCH 4/5] xfs: saner xfs_trans_commit interface
  • From: Brian Foster <bfoster@xxxxxxxxxx>
• Re: [PATCH 1/2] xfs: create new metadata UUID field and incompat flag
  • From: Eric Sandeen <sandeen@xxxxxxxxxxx>
• Re: [PATCH 1/2] xfs: create new metadata UUID field and incompat flag
  • From: Brian Foster <bfoster@xxxxxxxxxx>
• Re: [ceph-users] xfs corruption, data disaster!
  • From: Eric Sandeen <sandeen@xxxxxxxxxxx>
• Re: [ANNOUNCE, DISCUSS] xfsprogs: libxfs-4.1-update branch created
  • From: Eric Sandeen <sandeen@xxxxxxxxxxx>
• Re: [ceph-users] xfs corruption, data disaster!
  • From: Ric Wheeler <rwheeler@xxxxxxxxxx>
• Re: [ANNOUNCE, DISCUSS] xfsprogs: libxfs-4.1-update branch created
  • From: Eric Sandeen <sandeen@xxxxxxxxxxx>
• Re: [ANNOUNCE, DISCUSS] xfsprogs: libxfs-4.1-update branch created
  • From: Brian Foster <bfoster@xxxxxxxxxx>
• Re: [ANNOUNCE, DISCUSS] xfsprogs: libxfs-4.1-update branch created
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: [ANNOUNCE, DISCUSS] xfsprogs: libxfs-4.1-update branch created
  • From: Brian Foster <bfoster@xxxxxxxxxx>
• Re: [ANNOUNCE] xfsprogs: master branch updated to v3.2.3-rc1
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: [ANNOUNCE, DISCUSS] xfsprogs: libxfs-4.1-update branch created
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• Re: [ANNOUNCE] xfsprogs: master branch updated to v3.2.3-rc1
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• [ANNOUNCE] xfsprogs: master branch updated to v3.2.3-rc1
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• [ANNOUNCE, DISCUSS] xfsprogs: libxfs-4.1-update branch created
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• [PATCH 5/5] xfs: fix xfs_log_done interface
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH 4/5] xfs: saner xfs_trans_commit interface
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH 3/5] xfs: remove the flags argument to xfs_trans_cancel
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH 2/5] xfs: pass a boolean flag to xfs_trans_free_items
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH 1/5] xfs: switch remaining xfs_trans_dup users to xfs_trans_roll
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH 2/2 V2] xfsprogs: Add new sb_meta_uuid field, and userspace tools to manipulate it
  • From: Eric Sandeen <sandeen@xxxxxxxxxxx>
• Re: [PATCH 2/2] xfsprogs: Add new sb_meta_uuid field, and userspace tools to manipulate it
  • From: Eric Sandeen <sandeen@xxxxxxxxxxx>
• [PATCH 2/2] xfsprogs: Add new sb_meta_uuid field, and userspace tools to manipulate it
  • From: Eric Sandeen <sandeen@xxxxxxxxxxx>
• [PATCH 1/2] xfs: create new metadata UUID field and incompat flag
  • From: Eric Sandeen <sandeen@xxxxxxxxxxx>
• [PATCH 0/2] allow UUID changes on V5/CRC filesystems
  • From: Eric Sandeen <sandeen@xxxxxxxxxx>
• Re: Valid Benchmark Value & Methods
  • From: Dewangga Bachrul Alam <dewanggaba@xxxxxxxxxxxxxxx>
• Re: Valid Benchmark Value & Methods
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: Valid Benchmark Value & Methods
  • From: Martin Steigerwald <martin@xxxxxxxxxxxx>
• Re: Valid Benchmark Value & Methods
  • From: Dewangga <dewanggaba@xxxxxxxxxxxxxxx>
• Re: Valid Benchmark Value & Methods
  • From: Martin Steigerwald <martin@xxxxxxxxxxxx>
• Re: Valid Benchmark Value & Methods
  • From: Martin Steigerwald <martin@xxxxxxxxxxxx>
• Valid Benchmark Value & Methods
  • From: Dewangga <dewanggaba@xxxxxxxxxxxxxxx>
• Re: SGI Version 1 XFS on Linux
  • From: Emmanuel Florac <eflorac@xxxxxxxxxxxxxx>
• Re: SGI Version 1 XFS on Linux
  • From: Eric Sandeen <sandeen@xxxxxxxxxxx>
• RE: [PATCH v10 12/12] manpage: update FALLOC_FL_INSERT_RANGE flag in fallocate
  • From: Namjae Jeon <namjae.jeon@xxxxxxxxxxx>
• RE: SGI Version 1 XFS on Linux
  • From: "Scott, Edmund J @ SSG - Link" <edmund.scott@xxxxxxxxxx>
• Re: [PATCH v6 00/18] xfs: sparse inode chunks
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: [PATCH] mkfs: inode/block size error messages confusing
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: SGI Version 1 XFS on Linux
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: SGI Version 1 XFS on Linux
  • From: Ben Myers <bpm@xxxxxxx>
• RE: SGI Version 1 XFS on Linux
  • From: "Scott, Edmund J @ SSG - Link" <edmund.scott@xxxxxxxxxx>
• Re: SGI Version 1 XFS on Linux
  • From: Ben Myers <bpm@xxxxxxx>
• SGI Version 1 XFS on Linux
  • From: "Scott, Edmund J @ SSG - Link" <edmund.scott@xxxxxxxxxx>
• Re: [PATCH v6 00/18] xfs: sparse inode chunks
  • From: Brian Foster <bfoster@xxxxxxxxxx>
• Re: [PATCH v10 12/12] manpage: update FALLOC_FL_INSERT_RANGE flag in fallocate
  • From: "Michael Kerrisk (man-pages)" <mtk.manpages@xxxxxxxxx>
• Re: [PATCH] mkfs: inode/block size error messages confusing
  • From: Brian Foster <bfoster@xxxxxxxxxx>
• Re: [PATCH 1/2] percpu_counter: batch size aware __percpu_counter_compare()
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: [PATCH 1/2] percpu_counter: batch size aware __percpu_counter_compare()
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: [PATCH 2/2] xfs: inode counter needs to use __percpu_counter_compare
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: [PATCH 1/2] percpu_counter: batch size aware __percpu_counter_compare()
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: [PATCH 2/2] xfs: xfs_attr_inactive leaves inconsistent attr fork state behind
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• Re: [PATCH 1/2] percpu_counter: batch size aware __percpu_counter_compare()
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• Re: [PATCH 2/2] xfs: inode counter needs to use __percpu_counter_compare
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• Re: [PATCH 1/2] percpu_counter: batch size aware __percpu_counter_compare()
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• [PATCH] mkfs: inode/block size error messages confusing
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: [PATCH 01/12] xfs:Make the function,xfs_alloc_lookup_eq static
  • From: nick <xerofoify@xxxxxxxxx>
• Re: [PATCH] xfs: enforce imax_pct when we have per-cpu SB accounting
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: [PATCH 01/12] xfs:Make the function,xfs_alloc_lookup_eq static
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• [PATCH 1/2] percpu_counter: batch size aware __percpu_counter_compare()
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• [PATCH 2/2] xfs: inode counter needs to use __percpu_counter_compare
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• [PATCH 0/2] xfs: fix inode count underrun
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• [PATCH] xfs: enforce imax_pct when we have per-cpu SB accounting
  • From: "Darrick J. Wong" <darrick.wong@xxxxxxxxxx>
• Re: [PATCH 01/12] xfs:Make the function,xfs_alloc_lookup_eq static
  • From: nick <xerofoify@xxxxxxxxx>
• Re: [PATCH 01/12] xfs:Make the function,xfs_alloc_lookup_eq static
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH 12/12] xfs:Make the function,xfs_alloc_fix_freelist static
  • From: Nicholas Krause <xerofoify@xxxxxxxxx>
• [PATCH 11/12] xfs:Make the function,xfs_free_ag_extent static
  • From: Nicholas Krause <xerofoify@xxxxxxxxx>
• [PATCH 10/12] xfs:Make the function, xfs_alloc_find_best_extent static
  • From: Nicholas Krause <xerofoify@xxxxxxxxx>
• [PATCH 09/12] xfs:Make the function,xfs_alloc_ag_vextent static
  • From: Nicholas Krause <xerofoify@xxxxxxxxx>
• [PATCH 06/12] xfs:Make the function,xfs_alloc_fixup_trees static
  • From: Nicholas Krause <xerofoify@xxxxxxxxx>
• [PATCH 08/12] xfs:Make the function,xfs_alloc_update_counters static
  • From: Nicholas Krause <xerofoify@xxxxxxxxx>
• [PATCH 07/12] xfs:Make the function,xfs_alloc_read_agfl static
  • From: Nicholas Krause <xerofoify@xxxxxxxxx>
• [PATCH 05/12] xfs:Make the function, xfs_alloc_fix_minleft static
  • From: Nicholas Krause <xerofoify@xxxxxxxxx>
• [PATCH 02/12] xfs:Make the function,xfs_alloc_update static
  • From: Nicholas Krause <xerofoify@xxxxxxxxx>
• [PATCH 04/12] xfs:Make the function,xfs_alloc_fix_len static
  • From: Nicholas Krause <xerofoify@xxxxxxxxx>
• [PATCH 03/12] xfs:Make the function,xfs_alloc_compute_aligned static
  • From: Nicholas Krause <xerofoify@xxxxxxxxx>
• [PATCH 01/12] xfs:Make the function,xfs_alloc_lookup_eq static
  • From: Nicholas Krause <xerofoify@xxxxxxxxx>
• [PATCH] xfs: fix quota block reservation leak when tp allocates and frees blocks
  • From: Brian Foster <bfoster@xxxxxxxxxx>
• Re: [PATCH 2/2] xfs: xfs_attr_inactive leaves inconsistent attr fork state behind
  • From: Brian Foster <bfoster@xxxxxxxxxx>
• Re: [PATCH 1/2] xfs: extent size hints can round up extents past MAXEXTLEN
  • From: Brian Foster <bfoster@xxxxxxxxxx>
• Re: [V2] mkfs: default to CRC enabled filesystems
  • From: Brian Foster <bfoster@xxxxxxxxxx>
• Re: [PATCH] xfs_db: report FINOBT in version output
  • From: Brian Foster <bfoster@xxxxxxxxxx>
• Re: [PATCH 0/5 v2 RESEND] fs: Fixes for removing xid bits and security labels
  • From: Jan Kara <jack@xxxxxxx>
• Re: [PATCH 0/5 v2 RESEND] fs: Fixes for removing xid bits and security labels
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• [PATCH 0/2] xfs: couple of corruption fixes...
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• [PATCH 2/2] xfs: xfs_attr_inactive leaves inconsistent attr fork state behind
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• [PATCH 1/2] xfs: extent size hints can round up extents past MAXEXTLEN
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• [ANNOUNCE] xfs: master and for-next branches updated to v4.1-rc2
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• [V2] mkfs: default to CRC enabled filesystems
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: xfstests: what's the difference between generic/043 and generic/044
  • From: Wang Sheng-Hui <shhuiw@xxxxxxxxxxx>
• Re: xfstests: what's the difference between generic/043 and generic/044
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• xfstests: what's the difference between generic/043 and generic/044
  • From: "Wang Sheng-Hui" <shhuiw@xxxxxxxxxxx>
• Re: optimize inline symlink handling
  • From: Al Viro <viro@xxxxxxxxxxxxxxxxxx>
• [PATCH 5/5] xfs: optimize inline symlinks
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH 4/5] xfs: use ->readlink to implement the readlink_by_handle ioctl
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH 3/5] xfs: set up inode operation vectors later
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH 2/5] xfs: factor out a helper to initialize a local format inode fork
  • From: Christoph Hellwig <hch@xxxxxx>
• optimize inline symlink handling
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH] xfstests/common/renameat2: pass the renameat2 flags from _rename_tests to _rename_tests_source_dest
  • From: Wang Sheng-Hui <shhuiw@xxxxxxxxxxx>
• [PATCH] common/renameat2: pass the renameat2 flags from _rename_tests to _rename_tests_source_dest
  • From: Wang Sheng-Hui <shhuiw@xxxxxxxxxxx>
• Re: [PATCH] xfstests/common/renameat2: pass the renameat2 flags from _rename_tests, to _rename_tests_source_dest
  • From: shhuiw <shhuiw@xxxxxxxxxxx>
• [PATCH] xfstests/common/renameat2: pass the renameat2 flags from _rename_tests, to _rename_tests_source_dest
  • From: shhuiw <shhuiw@xxxxxxxxxxx>
• [PATCH] generic/204: use more space for inode allocation
  • From: Eryu Guan <eguan@xxxxxxxxxx>
• Re: question re: xfs inode to inode copy implementation
  • From: "Darrick J. Wong" <darrick.wong@xxxxxxxxxx>
• Re: generic/204 failure due to e88b64e xfs: use generic percpu counters for free inode counter
  • From: Eryu Guan <eguan@xxxxxxxxxx>
• Re: question re: xfs inode to inode copy implementation
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: [PATCH RFC 1/2] xfs: add sb_meta_uuid field to superblock
  • From: Eric Sandeen <sandeen@xxxxxxxxxxx>
• [PATCH RFC 2/2] xfsprogs: add support for sb_meta_uuid
  • From: Eric Sandeen <sandeen@xxxxxxxxxxx>
• [PATCH RFC 1/2] xfs: add sb_meta_uuid field to superblock
  • From: Eric Sandeen <sandeen@xxxxxxxxxxx>
• [PATCH] xfs_db: report FINOBT in version output
  • From: Eric Sandeen <sandeen@xxxxxxxxxx>
• Re: question re: xfs inode to inode copy implementation
  • From: xfs@xxxxxxxxxxx
• Re: Proposal/RFC: new metadata-specific UUID for V5 supers
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: Proposal/RFC: new metadata-specific UUID for V5 supers
  • From: Eric Sandeen <sandeen@xxxxxxxxxxx>
• Re: Inode and dentry cache behavior
  • From: Shrinand Javadekar <shrinand@xxxxxxxxxxxxxx>
• Re: xfsprogs compile warnings: _BSD_SOURCE is deprecated in glibc 2.20.
  • From: Jan Tulak <jtulak@xxxxxxxxxx>
• [PATCH] xfsprogs: Removing deprecated _BSD_SOURCE definition.
  • From: Jan Ťulák <jtulak@xxxxxxxxxx>
• Re: Inode and dentry cache behavior
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: Inode and dentry cache behavior
  • From: Shrinand Javadekar <shrinand@xxxxxxxxxxxxxx>
• Re: xfsprogs compile warnings: _BSD_SOURCE is deprecated in glibc 2.20.
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: question: are the metadata crc elements ready for general use?
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: generic/204 failure due to e88b64e xfs: use generic percpu counters for free inode counter
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• question: are the metadata crc elements ready for general use?
  • From: Joe Landman <joe.landman@xxxxxxxxx>
• generic/204 failure due to e88b64e xfs: use generic percpu counters for free inode counter
  • From: Eryu Guan <eguan@xxxxxxxxxx>
• xfsprogs compile warnings: _BSD_SOURCE is deprecated in glibc 2.20.
  • From: Jan Ťulák <jtulak@xxxxxxxxxx>
• Re: Proposal/RFC: new metadata-specific UUID for V5 supers
  • From: Eric Sandeen <sandeen@xxxxxxxxxxx>
• Re: Proposal/RFC: new metadata-specific UUID for V5 supers
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: Proposal/RFC: new metadata-specific UUID for V5 supers
  • From: "Carlos E. R." <carlos.e.r@xxxxxxxxxxxx>
• Re: Proposal/RFC: new metadata-specific UUID for V5 supers
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: Proposal/RFC: new metadata-specific UUID for V5 supers
  • From: Eric Sandeen <sandeen@xxxxxxxxxxx>
• Re: [PATCH] xfs: log record crc mismatch test
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: Proposal/RFC: new metadata-specific UUID for V5 supers
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Proposal/RFC: new metadata-specific UUID for V5 supers
  • From: Eric Sandeen <sandeen@xxxxxxxxxxx>
• Re: [PATCH] xfs: log record crc mismatch test
  • From: Eric Sandeen <sandeen@xxxxxxxxxxx>
• [PATCH] xfs: log record crc mismatch test
  • From: Alexander Tsvetkov <alexander.tsvetkov@xxxxxxxxxx>
• Re: [PATCH] xfs: call xfs_idestroy_fork() in xfs_ilock() critical section
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: question re: xfs inode to inode copy implementation
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: [PATCH 5/6] xfs: move non-inline symlinks to the pagecache
  • From: Al Viro <viro@xxxxxxxxxxxxxxxxxx>
• Re: [PATCH 5/6] xfs: move non-inline symlinks to the pagecache
  • From: Christoph Hellwig <hch@xxxxxx>
• Re: [PATCH 5/6] xfs: move non-inline symlinks to the pagecache
  • From: Al Viro <viro@xxxxxxxxxxxxxxxxxx>
• Re: [PATCH 5/6] xfs: move non-inline symlinks to the pagecache
  • From: Al Viro <viro@xxxxxxxxxxxxxxxxxx>
• Re: [PATCH 5/6] xfs: move non-inline symlinks to the pagecache
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH v3] xfs: always log the inode on unwritten extent conversion
  • From: Brian Foster <bfoster@xxxxxxxxxx>
• Re: [PATCH] xfs: call xfs_idestroy_fork() in xfs_ilock() critical section
  • From: Brian Foster <bfoster@xxxxxxxxxx>
• Kernel Trace at boot on fs/xfs/linux-2.6/xfs_aops.c:1008
  • From: Matteo Chesi <chesi@xxxxxxx>
• Re: [PATCH 5/6] xfs: move non-inline symlinks to the pagecache
  • From: Christoph Hellwig <hch@xxxxxx>
• Re: Inode and dentry cache behavior
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: Inode and dentry cache behavior
  • From: Shrinand Javadekar <shrinand@xxxxxxxxxxxxxx>
• Re: Inode and dentry cache behavior
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: [PATCH v2] xfs: always log the inode on unwritten extent conversion
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: [PATCH 5/6] xfs: move non-inline symlinks to the pagecache
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: [PATCH] xfs: call xfs_idestroy_fork() in xfs_ilock() critical section
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Inode and dentry cache behavior
  • From: Shrinand Javadekar <shrinand@xxxxxxxxxxxxxx>
• [PATCH 6/6] xfs: optimize inline symlinks
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH 5/6] xfs: move non-inline symlinks to the pagecache
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH 3/6] xfs: set up inode operation vectors later
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH 4/6] xfs: use ->readlink to implement the readlink_by_handle ioctl
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH 2/6] xfs: factor out a helper to initialize a local format inode fork
  • From: Christoph Hellwig <hch@xxxxxx>
• optimize symlink handling
  • From: Christoph Hellwig <hch@xxxxxx>
• Re: [PATCH] xfs: call xfs_idestroy_fork() in xfs_ilock() critical section
  • From: Waiman Long <waiman.long@xxxxxx>
• [PATCH v2] xfs: always log the inode on unwritten extent conversion
  • From: Brian Foster <bfoster@xxxxxxxxxx>
• Re: [PATCH] xfs: call xfs_idestroy_fork() in xfs_ilock() critical section
  • From: Brian Foster <bfoster@xxxxxxxxxx>
• Re: question re: xfs inode to inode copy implementation
  • From: "Darrick J. Wong" <darrick.wong@xxxxxxxxxx>
• [GIT PULL] xfs: updates for 4.1-rc1
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: question re: xfs inode to inode copy implementation
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: question re: xfs inode to inode copy implementation
  • From: "Darrick J. Wong" <darrick.wong@xxxxxxxxxx>
• Re: [PATCH] xfs: call xfs_idestroy_fork() in xfs_ilock() critical section
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: [PATCH] xfs: don't trigger fsync log force based on inode pin count
  • From: Brian Foster <bfoster@xxxxxxxxxx>
• Re: [PATCH] xfs: don't trigger fsync log force based on inode pin count
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• Re: [PATCH] xfs: don't trigger fsync log force based on inode pin count
  • From: Brian Foster <bfoster@xxxxxxxxxx>
• Re: [PATCH] xfs: don't trigger fsync log force based on inode pin count
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: [PATCH] xfs: call xfs_idestroy_fork() in xfs_ilock() critical section
  • From: Waiman Long <waiman.long@xxxxxx>
• Re: [PATCH] xfs: call xfs_idestroy_fork() in xfs_ilock() critical section
  • From: Brian Foster <bfoster@xxxxxxxxxx>
• Re: 4.0 kernel XFS filesystem crash when running AIM7's disk workload
  • From: Waiman Long <waiman.long@xxxxxx>
• [PATCH] xfs: call xfs_idestroy_fork() in xfs_ilock() critical section
  • From: Waiman Long <Waiman.Long@xxxxxx>
• Re: [PATCH] xfs: don't trigger fsync log force based on inode pin count
  • From: Brian Foster <bfoster@xxxxxxxxxx>
• Re: [PATCH] xfs: don't trigger fsync log force based on inode pin count
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• [PATCH] xfs: don't trigger fsync log force based on inode pin count
  • From: Brian Foster <bfoster@xxxxxxxxxx>
• Re: XFS_WANT_CORRUPTED_GOTO at line 1545 of file fs/xfs/xfs_alloc.c
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: question re: xfs inode to inode copy implementation
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: 4.0 kernel XFS filesystem crash when running AIM7's disk workload
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: 4.0 kernel XFS filesystem crash when running AIM7's disk workload
  • From: Waiman Long <waiman.long@xxxxxx>
• Re: [PATCH] xfsdump: fix instalation for symlinked /usr
  • From: Jan Tulak <jtulak@xxxxxxxxxx>
• [PATCH] xfsdump: fix instalation for symlinked /usr
  • From: Jan Ťulák <jtulak@xxxxxxxxxx>
• Re: XFS_WANT_CORRUPTED_GOTO at line 1545 of file fs/xfs/xfs_alloc.c
  • From: Mark Tinguely <tinguely@xxxxxxx>
• Re: XFS_WANT_CORRUPTED_GOTO at line 1545 of file fs/xfs/xfs_alloc.c
  • From: Emmanuel Florac <eflorac@xxxxxxxxxxxxxx>
• Re: question re: xfs inode to inode copy implementation
  • From: "Darrick J. Wong" <darrick.wong@xxxxxxxxxx>
• XFS_WANT_CORRUPTED_GOTO at line 1545 of file fs/xfs/xfs_alloc.c
  • From: beebol <ww103421245@xxxxxxx>
• question re: xfs inode to inode copy implementation
  • From: xfs@xxxxxxxxxxx
• linux-next: build failure after merge of the xfs tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the xfs tree with Linus' tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: [PATCH v2] xfs: extent size hints can round up extents past MAXEXTLEN
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: [PATCH v2] xfs: extent size hints can round up extents past MAXEXTLEN
  • From: Brian Foster <bfoster@xxxxxxxxxx>
• Re: [PATCH v2] xfs: extent size hints can round up extents past MAXEXTLEN
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: 4.0 kernel XFS filesystem crash when running AIM7's disk workload
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: [PATCH v3 3/3] NFSD: Add support for encoding multiple segments
  • From: "J. Bruce Fields" <bfields@xxxxxxxxxxxx>
• 4.0 kernel XFS filesystem crash when running AIM7's disk workload
  • From: Waiman Long <waiman.long@xxxxxx>
• Re: [PATCH v2] xfs: extent size hints can round up extents past MAXEXTLEN
  • From: Brian Foster <bfoster@xxxxxxxxxx>
• Re: [PATCH v2] xfs: extent size hints can round up extents past MAXEXTLEN
  • From: Brian Foster <bfoster@xxxxxxxxxx>
• Re: [PATCH] xfs: use percpu_counter_compare instead of naive comparing
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• [PATCH v2] xfs: use percpu_counter_read_positive for mp->m_icount
  • From: xuw2015@xxxxxxxxx
• Re: [PATCH] xfs: use percpu_counter_compare instead of naive comparing
  • From: 王旭 <xuw2015@xxxxxxxxx>
• Re: [PATCH] xfs: use percpu_counter_compare instead of naive comparing
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• [PATCH] xfs: use percpu_counter_compare instead of naive comparing
  • From: xuw2015@xxxxxxxxx
• Re: [PATCH v2] xfs: extent size hints can round up extents past MAXEXTLEN
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: [PATCH v2] xfs: extent size hints can round up extents past MAXEXTLEN
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: [PATCH] xfs: xfs_iozero can return positive errno
  • From: Brian Foster <bfoster@xxxxxxxxxx>
• Re: [PATCH v2] xfs: extent size hints can round up extents past MAXEXTLEN
  • From: Brian Foster <bfoster@xxxxxxxxxx>
• [ANNOUNCE] xfs: for-next branch updated to 542c311
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• [PATCH] xfs: xfs_iozero can return positive errno
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: [PATCH 5/8] xfs: add DAX file operations support
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: [PATCH 5/8] xfs: add DAX file operations support
  • From: Boaz Harrosh <boaz@xxxxxxxxxxxxx>
• Re: [PATCH 7/8] xfs: add DAX IO path support
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: [PATCH 5/8] xfs: add DAX file operations support
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• [PATCH v2] xfs: extent size hints can round up extents past MAXEXTLEN
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: 4.1 lockdep problem
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: [PATCH] xfs: extent size hints can round up extents past MAXEXTLEN
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: [PATCH v3 3/3] NFSD: Add support for encoding multiple segments
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: [PATCH v3 3/3] NFSD: Add support for encoding multiple segments
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: [PATCH] xfs: extent size hints can round up extents past MAXEXTLEN
  • From: Eric Sandeen <sandeen@xxxxxxxxxxx>
• Re: [PATCH v3 3/3] NFSD: Add support for encoding multiple segments
  • From: "J. Bruce Fields" <bfields@xxxxxxxxxxxx>
• Re: [PATCH v3 3/3] NFSD: Add support for encoding multiple segments
  • From: "J. Bruce Fields" <bfields@xxxxxxxxxxxx>
• Re: [PATCH v3 3/3] NFSD: Add support for encoding multiple segments
  • From: Anna Schumaker <Anna.Schumaker@xxxxxxxxxx>
• 4.1 lockdep problem
  • From: Eric Paris <eparis@xxxxxxxxxx>
• Re: [PATCH 5/9] xfs: DIO writes within EOF don't need an ioend
  • From: Brian Foster <bfoster@xxxxxxxxxx>
• Re: [PATCH 4/9] xfs: handle DIO overwrite EOF update completion correctly
  • From: Brian Foster <bfoster@xxxxxxxxxx>
• Re: [PATCH 1/9] xfs: factor DIO write mapping from get_blocks
  • From: Brian Foster <bfoster@xxxxxxxxxx>
• Re: [PATCH 9/9] xfs: extent size hints can round up extents past MAXEXTLEN
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• [PATCH 5/9] xfs: DIO writes within EOF don't need an ioend
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• [PATCH 9/9] xfs: extent size hints can round up extents past MAXEXTLEN
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• [PATCH 6/9] xfs: DIO write completion size updates race
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• [PATCH 0/8 v3] xfs: fix direct IO completion issues
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• [PATCH 7/9] xfs: direct IO EOF zeroing needs to drain AIO
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• [PATCH 4/9] xfs: handle DIO overwrite EOF update completion correctly
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• [PATCH 3/9] xfs: DIO needs an ioend for writes
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• [PATCH 1/9] xfs: factor DIO write mapping from get_blocks
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• [PATCH 8/9] xfs: using generic_file_direct_write() is unnecessary
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• [PATCH 2/9] xfs: move DIO mapping size calculation
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• [PATCH] xfs: extent size hints can round up extents past MAXEXTLEN
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: [PATCH 5/5] xfs: Correctly lock inode when removing suid and security marks
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: [PATCH 5/8] xfs: DIO writes within EOF don't need an ioend
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: [PATCH 4/8] xfs: handle DIO overwrite EOF update completion correctly
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: [PATCH 1/8] xfs: factor DIO write mapping from get_blocks
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: [PATCH 5/5] xfs: Correctly lock inode when removing suid and security marks
  • From: Eric Sandeen <sandeen@xxxxxxxxxxx>
• Re: [PATCH 4/8] xfs: handle DIO overwrite EOF update completion correctly
  • From: Brian Foster <bfoster@xxxxxxxxxx>
• Re: [PATCH 8/8] xfs: using generic_file_direct_write() is unnecessary
  • From: Brian Foster <bfoster@xxxxxxxxxx>
• Re: [PATCH 7/8] xfs: direct IO EOF zeroing needs to drain AIO
  • From: Brian Foster <bfoster@xxxxxxxxxx>
• Re: [PATCH 6/8] xfs: DIO write completion size updates race
  • From: Brian Foster <bfoster@xxxxxxxxxx>
• Re: [PATCH 5/8] xfs: DIO writes within EOF don't need an ioend
  • From: Brian Foster <bfoster@xxxxxxxxxx>
• Re: [PATCH 4/8] xfs: handle DIO overwrite EOF update completion correctly
  • From: Brian Foster <bfoster@xxxxxxxxxx>
• Re: [PATCH 3/8] xfs: DIO needs an ioend for writes
  • From: Brian Foster <bfoster@xxxxxxxxxx>
• Re: [PATCH 2/8] xfs: move DIO mapping size calculation
  • From: Brian Foster <bfoster@xxxxxxxxxx>
• Re: [PATCH 1/8] xfs: factor DIO write mapping from get_blocks
  • From: Brian Foster <bfoster@xxxxxxxxxx>
• [PATCH 4/8] xfs: handle DIO overwrite EOF update completion correctly
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• [PATCH 6/8] xfs: DIO write completion size updates race
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• [PATCH 5/8] xfs: DIO writes within EOF don't need an ioend
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• [PATCH 8/8] xfs: using generic_file_direct_write() is unnecessary
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• [PATCH 0/8 v2] xfs: fix direct IO completion issues
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• [PATCH 1/8] xfs: factor DIO write mapping from get_blocks
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• [PATCH 3/8] xfs: DIO needs an ioend for writes
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• [PATCH 7/8] xfs: direct IO EOF zeroing needs to drain AIO
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• [PATCH 2/8] xfs: move DIO mapping size calculation
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• linux-next: manual merge of the vfs tree with the xfs tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: [PATCH 2/5] xfs: direct IO needs to use append ioends
  • From: Brian Foster <bfoster@xxxxxxxxxx>
• [ANNOUNCE] xfs: master branch updated to 21c3ea1
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: linux-next: manual merge of the vfs tree with the xfs tree
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• linux-next: manual merge of the vfs tree with the xfs tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• [ANNOUNCE] xfsprogs: master branch updated to 502544b
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: [PATCH] libhandle: document the need for path_to_handle
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: [PATCH 2/5] xfs: direct IO needs to use append ioends
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: [PATCH 0/5] xfs: fix direct IO completion issues
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: [PATCH 2/2][v2] blk-plug: don't flush nested plug lists
  • From: Jeff Moyer <jmoyer@xxxxxxxxxx>
• [PATCH 2/2][v2] blk-plug: don't flush nested plug lists
  • From: Jeff Moyer <jmoyer@xxxxxxxxxx>
• Re: [f2fs-dev] [PATCH 2/2][v2] blk-plug: don't flush nested plug lists
  • From: nick <xerofoify@xxxxxxxxx>
• Re: [PATCH 2/2][v2] blk-plug: don't flush nested plug lists
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: [PATCH 2/2][v2] blk-plug: don't flush nested plug lists
  • From: Christoph Hellwig <hch@xxxxxx>
• Re: [RFC PATCH 0/5] Remove rw parameter from direct_IO()
  • From: Al Viro <viro@xxxxxxxxxxxxxxxxxx>
• Re: [PATCH 0/5] xfs: fix direct IO completion issues
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• Re: [PATCH 2/5] xfs: direct IO needs to use append ioends
  • From: Brian Foster <bfoster@xxxxxxxxxx>
• Re: [PATCH 2/5] xfs: direct IO needs to use append ioends
  • From: Brian Foster <bfoster@xxxxxxxxxx>
• Re: xfs---Book printing schedule
  • From: "Miss Colleen" <Colleen@xxxxxxxxxxxxxxxxx>
• Re: [PATCH 2/5] xfs: direct IO needs to use append ioends
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: [PATCH 1/5] xfs: DIO requires an ioend for writes
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: [PATCH 5/5] xfs: using generic_file_direct_write() is unnecessary
  • From: Brian Foster <bfoster@xxxxxxxxxx>
• Re: [PATCH 4/5] xfs: direct IO EOF zeroing needs to drain AIO
  • From: Brian Foster <bfoster@xxxxxxxxxx>
• Re: [PATCH 3/5] xfs: DIO write completion size updates race
  • From: Brian Foster <bfoster@xxxxxxxxxx>
• Re: [PATCH 2/5] xfs: direct IO needs to use append ioends
  • From: Brian Foster <bfoster@xxxxxxxxxx>
• Re: [PATCH 1/5] xfs: DIO requires an ioend for writes
  • From: Brian Foster <bfoster@xxxxxxxxxx>
• Re: hard reboot, no XFS messages
  • From: Carlos Maiolino <cmaiolino@xxxxxxxxxx>
• [PATCH 0/5] xfs: fix direct IO completion issues
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• [PATCH 2/5] xfs: direct IO needs to use append ioends
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• [PATCH 1/5] xfs: DIO requires an ioend for writes
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• [PATCH 3/5] xfs: DIO write completion size updates race
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• [PATCH 5/5] xfs: using generic_file_direct_write() is unnecessary
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• [PATCH 4/5] xfs: direct IO EOF zeroing needs to drain AIO
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: XFS Syncd
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: xfs_metadump requested by xfs_check
  • From: Brian Foster <bfoster@xxxxxxxxxx>
• xfs_metadump requested by xfs_check
  • From: Frédéric Bernard <fred.pa.bernard@xxxxxxxxx>
• Re: XFS Syncd
  • From: Shrinand Javadekar <shrinand@xxxxxxxxxxxxxx>
• Re: XFS Syncd
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: XFS Syncd
  • From: Shrinand Javadekar <shrinand@xxxxxxxxxxxxxx>
• Re: XFS Syncd
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: interesting MD-xfs bug
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: interesting MD-xfs bug
  • From: Roman Mamedov <rm@xxxxxxxxxxx>
• XFS Syncd
  • From: Shrinand Javadekar <shrinand@xxxxxxxxxxxxxx>
• Re: interesting MD-xfs bug
  • From: NeilBrown <neilb@xxxxxxx>
• Re: interesting MD-xfs bug
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: interesting MD-xfs bug
  • From: NeilBrown <neilb@xxxxxxx>
• Re: interesting MD-xfs bug
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: interesting MD-xfs bug
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: interesting MD-xfs bug
  • From: Joe Landman <joe.landman@xxxxxxxxx>
• Re: interesting MD-xfs bug
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• interesting MD-xfs bug
  • From: Joe Landman <joe.landman@xxxxxxxxx>
• [PATCH v2] xfs: use spin lock to prevent i_size race on dio write completion
  • From: Brian Foster <bfoster@xxxxxxxxxx>
• Re: Errors from basic open_by_handle operations
  • From: Mark Hills <mark.hills@xxxxxxxxxxxxxx>
• Re: Errors from basic open_by_handle operations
  • From: Roger Willcocks <roger@xxxxxxxxxxxxxxxx>
• Re: Errors from basic open_by_handle operations
  • From: Mark Hills <mark.hills@xxxxxxxxxxxxxx>
• [PATCH] libhandle: document the need for path_to_handle
  • From: tinguely@xxxxxxx
• Re: Errors from basic open_by_handle operations
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: Errors from basic open_by_handle operations
  • From: Roger Willcocks <roger@xxxxxxxxxxxxxxxx>
• Errors from basic open_by_handle operations
  • From: Mark Hills <mark.hills@xxxxxxxxxxxxxx>
• Re: [PATCH] xfs_repair: junk last entry in sf dir if name starts beyond dir size
  • From: Rui Gomes <rgomes@xxxxxx>
• Re: hard reboot, no XFS messages
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• hard reboot, no XFS messages
  • From: Malte Gell <mailinglisten@xxxxxxxxx>
• Re: 回复： XFS direct IO problem
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: [PATCH] xfs: unlock i_mutex in xfs_break_layouts
  • From: "J. Bruce Fields" <bfields@xxxxxxxxxxxx>
• Re: [PATCH] xfs: unlock i_mutex in xfs_break_layouts
  • From: Christoph Hellwig <hch@xxxxxx>
• Re: [PATCH] xfs: unlock i_mutex in xfs_break_layouts
  • From: Christoph Hellwig <hch@xxxxxx>
• Re: XFS direct IO problem
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• XFS direct IO problem
  • From: "YeYin" <eyniy@xxxxxx>
• Re: [PATCH] xfs: unlock i_mutex in xfs_break_layouts
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: [PATCH] xfs: unlock i_mutex in xfs_break_layouts
  • From: bfields@xxxxxxxxxxxx (J. Bruce Fields)
• [PATCH] xfs: use i_lock to prevent i_size race on dio write completion
  • From: Brian Foster <bfoster@xxxxxxxxxx>
• [PATCH] xfs: unlock i_mutex in xfs_break_layouts
  • From: Christoph Hellwig <hch@xxxxxx>
• Re: finest and rhel/centos 7.1
  • From: Eric Sandeen <sandeen@xxxxxxxxxxx>
• finest and rhel/centos 7.1
  • From: Charles Weber <chaweber@xxxxxxxxx>
• [PATCH V2] xfs_db: disallow sb UUID write on v5 filesystems
  • From: Eric Sandeen <sandeen@xxxxxxxxxxx>
• Re: [PATCH] xfs_db: disallow sb UUID write on v5 filesystems
  • From: Brian Foster <bfoster@xxxxxxxxxx>
• Re: [PATCH] xfsprogs: remove unreachable code in libxfs_inode_alloc
  • From: Brian Foster <bfoster@xxxxxxxxxx>
• Re: [RFC 1/2] xfs_db: enable blockget for v5 filesystems
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: [PATCH] libhandle: add fd_to_handle to handle.h
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• [PATCH] libhandle: add fd_to_handle to handle.h
  • From: Sage Weil <sage@xxxxxxxxxx>
• Re: [PATCH 8/8] xfs: add initial DAX support
  • From: Brian Foster <bfoster@xxxxxxxxxx>
• Re: [PATCH 7/8] xfs: add DAX IO path support
  • From: Brian Foster <bfoster@xxxxxxxxxx>
• Re: [PATCH 6/8] xfs: add DAX truncate support
  • From: Brian Foster <bfoster@xxxxxxxxxx>
• Re: [PATCH 5/8] xfs: add DAX file operations support
  • From: Brian Foster <bfoster@xxxxxxxxxx>
• Re: [PATCH 4/8] xfs: add DAX block zeroing support
  • From: Brian Foster <bfoster@xxxxxxxxxx>
• Re: [PATCH 1/8] xfs: mmap lock needs to be inside freeze protection
  • From: Brian Foster <bfoster@xxxxxxxxxx>
• [PATCH] xfsprogs: remove unreachable code in libxfs_inode_alloc
  • From: Eric Sandeen <sandeen@xxxxxxxxxx>
• [PATCH] xfs_db: disallow sb UUID write on v5 filesystems
  • From: Eric Sandeen <sandeen@xxxxxxxxxx>
• Bug#782012: xfs_admin: Changing UUID destroys Filesystem
  • From: Eric Sandeen <sandeen@xxxxxxxxxxx>
• Bug#782012: xfs_admin: Changing UUID destroys Filesystem
  • From: "F. Stoyan" <fstoyan@xxxxxxxxx>
• Re: xfs corruption issue
  • From: Danny Shavit <danny@xxxxxxxxxxxxxxxxx>
• LPC2015: File and Storage Systems uconf
  • From: "Darrick J. Wong" <darrick.wong@xxxxxxxxxx>
• Re: FYI: xfstests generic/019 result panic. 4.0.0-rc5
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: Slightly Urgent: XFS No Space Left On Device
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: Slightly Urgent: XFS No Space Left On Device
  • From: Grozdan <neutrino8@xxxxxxxxx>
• Re: Slightly Urgent: XFS No Space Left On Device
  • From: Grozdan <neutrino8@xxxxxxxxx>
• Re: Slightly Urgent: XFS No Space Left On Device
  • From: Dave Hall <kdhall@xxxxxxxxxxxxxx>
• FYI: xfstests generic/019 result panic. 4.0.0-rc5
  • From: Dmitry Monakhov <dmonakhov@xxxxxxxxxx>
• Re: Slightly Urgent: XFS No Space Left On Device
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: Slightly Urgent: XFS No Space Left On Device
  • From: Dave Hall <kdhall@xxxxxxxxxxxxxx>
• Re: xfs corruption issue
  • From: Eric Sandeen <sandeen@xxxxxxxxxxx>