From: Richard Hartmann <richih.mailinglist@gmail.com>
To: Eric Sandeen <sandeen@sandeen.net>
Cc: linux-xfs@oss.sgi.com, Nicolas Stransky <nico@stransky.cx>
Subject: Re: xfs_repair on a 1.5 TiB image has been hanging for about an hour, now
Date: Fri, 12 Feb 2010 21:01:11 +0100 [thread overview]
Message-ID: <2d460de71002121201q224d3bc8xe48089eccdf6f6a@mail.gmail.com> (raw)
In-Reply-To: <4B7594D3.6040304@sandeen.net>
On Fri, Feb 12, 2010 at 18:50, Eric Sandeen <sandeen@sandeen.net> wrote:
> hard to say without knowing for sure what version you're using, and
> what exactly "this" is that you're seeing :)
3.0.4 - I stated that in another subthread so it might have gotten lost.
> Providing an xfs_metadump of the corrupted fs that hangs repair
> is also about the best thing you could do for investigation,
> if you've already determined that the latest release doesn't help.
http://dediserver.eu/misc/mailstore_metadata_obscured__after_xfs_repair_hang.bz2
http://dediserver.eu/misc/mailstore_metadata_obscured.bz2
These logs will stay up for at least a week or three.
Richard
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2010-02-12 20:00 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-12 14:07 xfs_repair on a 1.5 TiB image has been hanging for about an hour, now Richard Hartmann
2010-02-12 15:28 ` Eric Sandeen
2010-02-12 16:45 ` Richard Hartmann
2010-02-12 17:02 ` Richard Hartmann
2010-02-12 17:31 ` Nicolas Stransky
2010-02-12 17:50 ` Eric Sandeen
2010-02-12 18:16 ` Nicolas Stransky
2010-02-12 20:30 ` Nicolas Stransky
2010-02-12 20:39 ` Richard Hartmann
2010-02-12 22:21 ` Nicolas Stransky
2010-02-12 20:48 ` Eric Sandeen
2010-02-12 22:27 ` Nicolas Stransky
2010-02-12 20:01 ` Richard Hartmann [this message]
2010-02-12 20:11 ` Eric Sandeen
2010-02-12 22:19 ` Eric Sandeen
[not found] ` <20100212165801.GA7323@puku.stupidest.org>
2010-02-12 17:04 ` Richard Hartmann
2010-02-12 17:06 ` Richard Hartmann
2010-02-12 17:13 ` Eric Sandeen
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=2d460de71002121201q224d3bc8xe48089eccdf6f6a@mail.gmail.com \
--to=richih.mailinglist@gmail.com \
--cc=linux-xfs@oss.sgi.com \
--cc=nico@stransky.cx \
--cc=sandeen@sandeen.net \
/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