Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[PATCH\s+repair\:\s+do\s+not\s+walk\s+the\s+unlinked\s+inode\s+list\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[PATCH\s+repair\:\s+do\s+not\s+walk\s+the\s+unlinked\s+inode\s+list\s*$/: 3 ]

Total 3 documents matching your query.

1. [PATCH repair: do not walk the unlinked inode list (score: 1): Author: Christoph Hellwig <hch@xxxxxxxxxxxxx>; Date: Wed, 9 Nov 2011 03:37:29 -0500; Stefan Pfetzing reported a bug where xfs_repair got stuck eating 100% CPU in phase3. We track it down to a loop in the unlinked inode list, apparently caused by memory corruption on an iSCSI target.; /archives/xfs/2011-11/msg00198.html (13,461 bytes)
2. Re: [PATCH repair: do not walk the unlinked inode list (score: 1): Author: Dave Chinner <david@xxxxxxxxxxxxx>; Date: Thu, 10 Nov 2011 10:11:33 +1100; You're making the assumption that log recovery has done the correct thing any only replayed entire unlink transactions and hence the filesystem is otherwise consistent (i.e that there are no other re; /archives/xfs/2011-11/msg00214.html (10,220 bytes)
3. Re: [PATCH repair: do not walk the unlinked inode list (score: 1): Author: Christoph Hellwig <hch@xxxxxxxxxxxxx>; Date: Mon, 14 Nov 2011 13:55:59 -0500; We add inodes to the uncertain list if any of the following applies a) are found in an inode btree record reachable from the root in phase2, but they are suspect based on certain factors - else we ad; /archives/xfs/2011-11/msg00281.html (10,297 bytes)

Current List: 1 - 3
Page: [1]