On Tue, Apr 25, 2006 at 10:17:43PM -0400, Yonathan Dossow wrote:
> corrupt dinode 48838848, extent total = 1, nblocks = 0. This is a bug.
> Please report it to linux-xfs@xxxxxxxxxxxx
>
> fatal error -- couldn't map inode 48838848, err = 990
This looks familiar. I had one machine that for the life of me I
couldn't figure out why every time it would shut down, one or two files
would have this problem. I had no recourse but to use xfs_db to manually
remove the files, then use xfs_repair again to fix the filesystem.
It was never fixed, despite best efforts on my end to report the problem
to the best of my knowledge. It's not a common bug, though, and now that
the particular machine has been retired I don't have an active system
with this problem.
You can search the archives[1] for my reports, with the 990 error as
keyword.
[1] http://archives.free.net.ph/list/linux-xfs.html
Cheers!
--> Jijo
--
Federico Vicente C. Sevilla III
Information Technology Consultant
Q Software Research Corporation
Website: http://jijo.free.net.ph
|