http://bugzilla.kernel.org/show_bug.cgi?id=10421
------- Comment #8 from dgc@xxxxxxx 2008-04-10 18:03 -------
From comment #5, that error path indicates an invalid inode number in
the unlinked list. i.e. the inode being freed is being inserted into
the unlinked list, but the current inode the list points to is non-existent.
Given that the problem is not consistent and there is no corruption on
disk, this smells of a memory corruption of some kind. I think that turning
on all the memory debugging and poisoning would be a good idea.
Also if it happens again and xfs_repair puts a disconnected inode into
lost+found, can you dump the inode contents for us using:
# xfs_db -r -c 'inode <inode #>' -c p <dev>
The inode # is the name of the inode in lost+found.
--
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
|