xfs_repair fails with corrupt dinode 17491441757, extent total = 1, nblocks = 0. This is a bug.
Arkadiusz Miśkiewicz
arekm at maven.pl
Thu Nov 3 05:57:38 CDT 2011
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/
More information about the xfs
mailing list