xfs
[Top] [All Lists]

Re: xfs_repair fails with corrupt dinode 17491441757, extent total = 1,

To: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Subject: Re: xfs_repair fails with corrupt dinode 17491441757, extent total = 1, nblocks = 0. This is a bug.
From: Arkadiusz Miśkiewicz <arekm@xxxxxxxx>
Date: Thu, 3 Nov 2011 11:57:38 +0100
Cc: xfs@xxxxxxxxxxx
In-reply-to: <20111103104850.GA26259@xxxxxxxxxxxxx>
References: <201110311156.20421.arekm@xxxxxxxx> <201111031140.46783.arekm@xxxxxxxx> <20111103104850.GA26259@xxxxxxxxxxxxx>
User-agent: KMail/1.13.7 (Linux/3.1.0-final-dirty; KDE/4.7.3; x86_64; ; )
On Thursday 03 of November 2011, Christoph Hellwig wrote:
> On Thu, Nov 03, 2011 at 11:40:46AM +0100, Arkadiusz Mi??kiewicz wrote:
> > This serwer has 16 various SATA disk connected to art-of-crap controller
> > - Promise SuperTrak EX16350.
> > 
> > The system exhibits funny issues with intel_idle driver
> > (https://lkml.org/lkml/2011/10/28/270).
> > 
> > It has only 8GB of ram which xfs_repair eats for breakfast causing
> > watchdog to reboot machine while xfs_repair was in progress (would be
> > nice if repair could estimate needed ram before it is too late).
> 
> Yes.  So far most of the issues are with the internal buffercache and I
> suspect we could do better sizing decisions there.  If you can provide
> some testing (xfs_repair -n should be enough) I'll happily send you
> some RFC patches as soon as I get time for it.

I can do some testing (on image though but that shouldn't matter).

> 
> In the meantime is there any chance you could send the output of
> 
>       xfs_repair -n -vv -m 1
> 
> for this filesystem?

Will such repair done on metadumped & restored image be enough for you?

-- 
Arkadiusz Miśkiewicz        PLD/Linux Team
arekm / maven.pl            http://ftp.pld-linux.org/

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