Messages in this thread |  | | | Date | Mon, 08 Oct 2007 09:54:28 +0800 | | From | Max Waterman <> | | Subject | Re: XFS internal error |
| |
David Chinner wrote: >> 1994 of file fs/xfs/xfs_da_btree.c. Caller 0xffffffff889b2de4 >> > > Did you ever run 2.6.17-2.6.17.6? I guess so, since I've been upgrading steadily since I installed FC6 some time ago. > If so, this implies: > > http://oss.sgi.com/projects/xfs/faq.html#dir2 > Ah. I did see that, but stopped reading when I read it was fixed in later versions ... didn't get to the part where it still needed to be repaired/etc.
>> I am fairly sure there is nothing I can do about this, but I thought it >> prudent to mention it. Searching turned up some similar issues, but they >> seem related to a previous kernel version and claimed to be fixed in >> subsequent versions. >> > > Yes, but those previous corruptions get left on disk as a landmine > for you to trip over some time later, even on a kernel that has the > bug fixed. > ah, ok. > I suggest that you run xfs_check on the filesystem and if that > shows up errors, run xfs_repair onteh filesystem to correct them. > It did, and I did, and another xfs_check produced no output.
Do I need to do anything else to correct it? xfs_repair produced a whole bunch of stuff that I don't understand...this is the bit that looks most significant :
> Phase 6 - check inode connectivity... > - resetting contents of realtime bitmap and summary inodes > - traversing filesystem ... > can't read freespace block 16777216 for directory inode 2095141277 > rebuilding directory inode 2095141277 > free block 16777216 for directory inode 2100841732 bad nused > rebuilding directory inode 2100841732 > free block 16777216 for directory inode 2102199514 bad nused > rebuilding directory inode 2102199514 > free block 16777216 for directory inode 2102200124 bad nused > rebuilding directory inode 2102200124 > free block 16777216 for directory inode 2102905843 bad nused > rebuilding directory inode 2102905843 > free block 16777216 for directory inode 3277510927 bad nused > rebuilding directory inode 3277510927 > free block 16777216 for directory inode 3277524487 bad nused > rebuilding directory inode 3277524487 > free block 16777216 for directory inode 3379886019 bad nused > rebuilding directory inode 3379886019 > - traversal finished ... > - moving disconnected inodes to lost+found ... That last line looks suspicious...furthermore, when I mount the filesystem, I don't see a 'lost+found' directory (which I've been used to seeing on IRIX). Ah, perhaps the '...' with *nothing* after it means it didn't do any moving. Am I right?
Max. - 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/
|  |