xfs
[Top] [All Lists]

RE: xfs data loss

To: "Passerone, Daniele" <Daniele.Passerone@xxxxxxx>
Subject: RE: xfs data loss
From: Christian Kujau <lists@xxxxxxxxxxxxxxx>
Date: Thu, 27 Aug 2009 03:09:43 -0700 (PDT)
Cc: "xfs@xxxxxxxxxxx" <xfs@xxxxxxxxxxx>
In-reply-to: <B9A7B002C7FAFC469D4229539E909760308DA65237@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
References: <B9A7B002C7FAFC469D4229539E909760308DA651DE@xxxxxxxxxxxxxxxxxxxxxxxxxxx> <alpine.DEB.2.01.0908270232540.5744@xxxxxxxxxxxxxxxxxx> <B9A7B002C7FAFC469D4229539E909760308DA65237@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
User-agent: Alpine 2.01 (DEB 1266 2009-07-14)
On Thu, 27 Aug 2009 at 11:47, Passerone, Daniele wrote:
> Unfortunately xfs_ncheck was not killed, it went "D" state.
> The box has 16Gb.

"D" as in "waiting for I/O to complete". Were you able to confirm that, 
i.e. was there really noticable disk i/o happening during xfs_ncheck or 
was the process perhaps "stuck in D state"? I seem to remember that in 
those cases the output of sysrq-w could be interesting.

> Can I do something with my xfs_metadump [please be polite :-) ]

You've put the dump online, let's hope some XFS wizard finds time to have 
a look at this...I certainly can't read this :-\

Christian.
-- 
BOFH excuse #228:

That function is not currently supported, but Bill Gates assures us it will be 
featured in the next upgrade.

<Prev in Thread] Current Thread [Next in Thread>