From: Michael Monnerie <michael.monnerie@is.it-management.at>
To: Drunkard Zhang <gongfan193@gmail.com>
Cc: xfs-masters@oss.sgi.com, Alex Elder <aelder@sgi.com>,
linux-kernel@vger.kernel.org, xfs@oss.sgi.com
Subject: Re: bug in xfs: can't recovery metadata log
Date: Tue, 7 Jun 2011 10:30:59 +0200 [thread overview]
Message-ID: <201106071031.02928@zmi.at> (raw)
In-Reply-To: <BANLkTikrmbe9X3Weyb8ikhn1RX_Tn_NuAg@mail.gmail.com>
[-- Attachment #1.1: Type: Text/Plain, Size: 725 bytes --]
On Dienstag, 7. Juni 2011 Drunkard Zhang wrote:
> Oops, I already did "xfs_repair -L", successed. It's in production
> environment, didn't have too much time to figure out why :-(
That was probably the only chance anyway.
I'm wondering about the crash. Even if the log is full of shit because
of a crash, xfs should not drive to hell but better report the fact and
exit. But maybe such strict checking is not worth the effort, as every
competent admin does xfs_repair then anyway?
--
mit freundlichen Grüssen,
Michael Monnerie, Ing. BSc
it-management Internet Services: Protéger
http://proteger.at [gesprochen: Prot-e-schee]
Tel: +43 660 / 415 6531
// Haus zu verkaufen: http://zmi.at/langegg/
[-- Attachment #1.2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
[-- Attachment #2: Type: text/plain, Size: 121 bytes --]
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
WARNING: multiple messages have this Message-ID (diff)
From: Michael Monnerie <michael.monnerie@is.it-management.at>
To: Drunkard Zhang <gongfan193@gmail.com>
Cc: xfs@oss.sgi.com, Alex Elder <aelder@sgi.com>,
xfs-masters@oss.sgi.com, linux-kernel@vger.kernel.org
Subject: Re: bug in xfs: can't recovery metadata log
Date: Tue, 7 Jun 2011 10:30:59 +0200 [thread overview]
Message-ID: <201106071031.02928@zmi.at> (raw)
In-Reply-To: <BANLkTikrmbe9X3Weyb8ikhn1RX_Tn_NuAg@mail.gmail.com>
[-- Attachment #1: Type: Text/Plain, Size: 725 bytes --]
On Dienstag, 7. Juni 2011 Drunkard Zhang wrote:
> Oops, I already did "xfs_repair -L", successed. It's in production
> environment, didn't have too much time to figure out why :-(
That was probably the only chance anyway.
I'm wondering about the crash. Even if the log is full of shit because
of a crash, xfs should not drive to hell but better report the fact and
exit. But maybe such strict checking is not worth the effort, as every
competent admin does xfs_repair then anyway?
--
mit freundlichen Grüssen,
Michael Monnerie, Ing. BSc
it-management Internet Services: Protéger
http://proteger.at [gesprochen: Prot-e-schee]
Tel: +43 660 / 415 6531
// Haus zu verkaufen: http://zmi.at/langegg/
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2011-06-07 8:31 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-07 5:20 bug in xfs: can't recovery metadata log Drunkard Zhang
2011-06-07 5:20 ` Drunkard Zhang
2011-06-07 6:36 ` Drunkard Zhang
2011-06-07 6:36 ` Drunkard Zhang
2011-06-07 7:43 ` Michael Monnerie
2011-06-07 7:43 ` Michael Monnerie
2011-06-07 7:56 ` Drunkard Zhang
2011-06-07 7:56 ` Drunkard Zhang
2011-06-07 8:30 ` Michael Monnerie [this message]
2011-06-07 8:30 ` Michael Monnerie
2011-06-07 10:32 ` Christoph Hellwig
2011-06-07 10:32 ` Christoph Hellwig
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=201106071031.02928@zmi.at \
--to=michael.monnerie@is.it-management.at \
--cc=aelder@sgi.com \
--cc=gongfan193@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=xfs-masters@oss.sgi.com \
--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.