Re: XFS crashed twice, once in 2.6.16.20, next in 2.6.17, reproducable

[asjo@xxxxxxxxxxxx (Adam Sjøgren)]

On Tue, 4 Jul 2006 11:47:21 +1000, Nathan wrote:

> On Sat, Jul 01, 2006 at 04:02:35PM +0200, Adam Sj?gren wrote:

>> I proceeded to run xfs_repair. In Phase 3 under '- agno 0' it said:

>> bad dir magic number 0x30 in inode 180 bno = 8388608

(That is my /lost+found/, 'ls -i' says).

>> It continued and in Phase 6 after saying '- traversing filesystem
>> starting at / ...' it said:

>> rebuilding directory inode 128

> Thats your root directory.  Its being rebuilt due to a lost+found
> directory being earlier unlinked, most likely.

Ah, ok - thanks.

>> And a flurry of "disconnected inode [number], moving to lost+found"
>> followed.

> Yeah, anything that was in lost+found after the first run, gets
> put back there each time.

I see - thanks.

>> Any hints on how to fully repair the filesystem, in place?

> It sounds like your filesystem is repaired at this point - you
> need to fix up (remove) lost+found, and you should get no issues
> reported thereafter.

I can't. 'rm' hangs in diskwait (ps says 'D') indefinitely (I let it
sit for several hours) if I try. Even 'ls /lost+found/' does so.

I've just run 'badblocks' and 'dd_rescue' (to /dev/null) on the disk
to double check that it isn't a physical problem. Neither reported
errors.


Any pointers on what to look at?


  Thanks!

    Adam

-- 
 "Subdued flamboyance"                                        Adam Sjøgren
                                                         asjo@xxxxxxxxxxxx