- 1. xfs_repair misses an fs error? (score: 1)
- Author: Keith Keller <kkeller@xxxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Mon, 15 Apr 2013 16:47:32 -0700
- Hi all, I recently had a filesystem stop, and went through the usual umount, mount, umount, xfs_repair path. xfs_repair didn't find any errors, but I noticed that I was still getting some strange iss
- /archives/xfs/2013-04/msg00345.html (11,104 bytes)
- 2. Re: xfs_repair misses an fs error? (score: 1)
- Author: Dave Chinner <david@xxxxxxxxxxxxx>
- Date: Wed, 17 Apr 2013 02:25:57 +1000
- Not recently. What version of xfs_repair are you using? xfs_repair -n is the usual way to find broken stuff without modifying anything.... Cheers, Dave. -- Dave Chinner david@xxxxxxxxxxxxx
- /archives/xfs/2013-04/msg00364.html (9,069 bytes)
- 3. Re: xfs_repair misses an fs error? (score: 1)
- Author: Keith Keller <kkeller@xxxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Tue, 16 Apr 2013 11:44:54 -0700
- Hmm, perhaps this is a difference. I believe (though, again I did very poor logging, and I apologize) that the initial repair used 3.1.1. The recent successful repair definitely used 3.1.10. Is it po
- /archives/xfs/2013-04/msg00369.html (7,952 bytes)
- 4. Re: xfs_repair misses an fs error? (score: 1)
- Author: Roger Willcocks <roger@xxxxxxxxxxxxxxxx>
- Date: Tue, 16 Apr 2013 20:19:50 +0100
- Yes, we had a system here for which xfs_repair 3.1.6 reported for 30 or so files: data fork in regular inode 3238731555 claims used block 1080914355 correcting nblocks for inode 3238731555, was 304 -
- /archives/xfs/2013-04/msg00370.html (9,233 bytes)
- 5. Re: xfs_repair misses an fs error? (score: 1)
- Author: Dave Chinner <david@xxxxxxxxxxxxx>
- Date: Wed, 17 Apr 2013 08:05:26 +1000
- Yes - there have been problems like this fixed since 3.1.1... Cheers, Dave. -- Dave Chinner david@xxxxxxxxxxxxx
- /archives/xfs/2013-04/msg00372.html (8,719 bytes)
This search system is powered by
Namazu