Messages in this thread | | | Date | Thu, 22 Jun 2006 12:56:40 +1000 | From | Nathan Scott <> | Subject | Re: XFS crashed twice, once in 2.6.16.20, next in 2.6.17, reproducable |
| |
On Tue, Jun 20, 2006 at 01:20:39AM -0700, Avuton Olrich wrote: > On 6/19/06, Nathan Scott <nathans@sgi.com> wrote: > > No - its in CVS (for a long time); I'll go get the ftp area updated, > > looks like thats been forgotten about again.
FWIW, I've updated the ftp area now.
> OK, just compiled from CVS HEAD (xfs_repair 2.8.2) and it still fails:
Is this a large filesystem? Any chance we can get access to it somehow (e.g. xfs_copy to a sparse file, then send me a pointer to it) to reproduce the problem locally?
> fatal error -- can't read block 16777216 for directory inode > 1507133580
Once you save a copy of it for further analysis of xfs_repair, if you can, you can clear out this problem by directly poking at the device using xfs_db in expert mode. "xfs_db -x /dev/xxx"; then "inode 1507133580"; then "write core.mode 0"; and then try another xfs_repair run. Please try capture the fs for us first though (if possible) else we're going to struggle to improve on this aspect of xfs_repair. Send me some private mail if you do manage to grab the fs and put it someplace for me.
thanks.
-- Nathan - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |