From: "Arkadiusz Miśkiewicz" <arekm@maven.pl>
To: Christoph Hellwig <hch@infradead.org>
Cc: 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 21:21:16 +0100 [thread overview]
Message-ID: <201111032121.16891.arekm@maven.pl> (raw)
In-Reply-To: <20111103110306.GA8382@infradead.org>
On Thursday 03 of November 2011, Christoph Hellwig wrote:
> On Thu, Nov 03, 2011 at 11:57:38AM +0100, Arkadiusz Mi??kiewicz wrote:
> > > 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?
>
> Yes.
>
> I also looked at the memory heuristics and found some fairly obvious
> flaws. I'll have some test patches for you ASAP.
# LC_ALL=C ./xfs_repair -vv -m 1 /dev/vg_sys/lv_storage1
Phase 1 - find and verify superblock...
- max_mem = 1024, icount = 97495744, imem = 380842, dblock =
1884752896, dmem = 920289
Required memory for repair is greater that the maximum specified
with the -m option. Please increase it to at least 1319.
--
Arkadiusz Miśkiewicz PLD/Linux Team
arekm / maven.pl http://ftp.pld-linux.org/
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2011-11-03 20:21 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
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 [this message]
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=201111032121.16891.arekm@maven.pl \
--to=arekm@maven.pl \
--cc=hch@infradead.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.