http://oss.sgi.com/bugzilla/show_bug.cgi?id=326
trisk+sgi@xxxxxxxxxxx changed:
What |Removed |Added
----------------------------------------------------------------------------
Priority| |P1
------- Additional Comments From trisk+sgi@xxxxxxxxxxx 2006-05-04 07:43 CST
-------
I'm experiencing a similar problem with xfs_repair from xfsprogs 2.7.11:
rebuilding directory inode 128
corrupt dinode 25633485, extent total = 2, nblocks = 1. This is a bug.
Please report it to linux-xfs@xxxxxxxxxxxx
fatal error -- couldn't map inode 25633485, err = 990
This is on a filesystem on a machine running Linux 2.6.16 that was rebooted
uncleanly.
Interestingly, I'm also observing the corrupted filenames (first char replaced
with '/') mentioned in #229. I don't have a copy of the oops produced earlier
by accessing that inode, but I can try to generate one if needed.
I've included the xfs_repair and xfs_info output as attachments.
--
Configure bugmail: http://oss.sgi.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
|