Re: invalid directory entry - bad magic number on inode

Lachlan McIlroy
2006-12-12T00:41:16Z

Martin Steigerwald wrote:
> Am Montag 11 Dezember 2006 15:05 schrieb Lachlan McIlroy:
>
>
>>>Any hints on what I could try if it ever happens again? Suppose I can
>>>save out the bad inode contents before I let xfs_repair fix it...
>>
>>If you see it again could you run xfs_check in verbose mode (ie
>>xfs_check -v /dev/hda5 and xfs_check -v -i <inode number> /dev/hda5)?
>
>
> Hello Lachlan,
>
> thanks for the hints. So far it didn't occur again (at least not that I am
> aware of) - well I don't expect it to happen often and am not really sure
> whether it will happen again at all.
>
>
>>Thanks for reporting this problem.
>
>
> You are welcome. Without further info reporting it to the bugtracker
> doesn't make much sense to me. I will keep an eye on it. If it happens
> again, I will try the hints you gave me. I run xfs_check anyway and thus
> can easily give it a "-v >xfs_check.txt". I thought I would have to use
> xfs_db stuff to get further info.

Now that you mention it, printing out the inode in xfs_db might be useful.

>
> Regards,