From: Christoph Hellwig <hch@infradead.org>
To: Arkadiusz Mi??kiewicz <arekm@maven.pl>
Cc: Christoph Hellwig <hch@infradead.org>, xfs@oss.sgi.com
Subject: Re: xfs_repair fails with corrupt dinode 17491441757, extent total = 1, nblocks = 0. This is a bug.
Date: Thu, 3 Nov 2011 06:48:50 -0400 [thread overview]
Message-ID: <20111103104850.GA26259@infradead.org> (raw)
In-Reply-To: <201111031140.46783.arekm@maven.pl>
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.
In the meantime is there any chance you could send the output of
xfs_repair -n -vv -m 1
for this filesystem?
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2011-11-03 10:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-31 10:56 xfs_repair fails with corrupt dinode 17491441757, extent total = 1, nblocks = 0. This is a bug Arkadiusz Miśkiewicz
2011-11-03 10:26 ` Christoph Hellwig
2011-11-03 10:40 ` Arkadiusz Miśkiewicz
2011-11-03 10:48 ` Christoph Hellwig [this message]
2011-11-03 10:57 ` Arkadiusz Miśkiewicz
2011-11-03 11:03 ` Christoph Hellwig
2011-11-03 11:54 ` Christoph Hellwig
2011-11-03 20:02 ` Arkadiusz Miśkiewicz
2011-11-03 20:21 ` Arkadiusz Miśkiewicz
2011-11-06 22:19 ` Arkadiusz Miśkiewicz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20111103104850.GA26259@infradead.org \
--to=hch@infradead.org \
--cc=arekm@maven.pl \
--cc=xfs@oss.sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox