From: Michael Monnerie <michael.monnerie@is.it-management.at>
To: xfs@oss.sgi.com
Cc: Hanne Munkholm <hanne@binf.ku.dk>
Subject: Re: "Corrupt dinode 6242615, (btree extents). This is a bug."
Date: Mon, 8 Aug 2011 13:58:38 +0200 [thread overview]
Message-ID: <201108081358.43727@zmi.at> (raw)
In-Reply-To: <alpine.OSX.1.00.1108081203550.26464@pegasus.binf.ku.dk>
[-- Attachment #1.1: Type: Text/Plain, Size: 1264 bytes --]
On Montag, 8. August 2011 Hanne Munkholm wrote:
> a) Does it look like clearing the log with -L would be a good
> idea? To me it looks like a lot of errors that are not log
> errors is found?
Yes, mount -L/umount once to replay the log, when you are sure the block
device works correctly again.
> b) What's with the segfault? What happens when the "real" repair
> with no -n gets to the segfault? Is it dangerous to try it if it
> segfaults somewhere halfway? (More dangerous than it would
> normally be).
>
> It is a 6TB file system and I am running a terribly old Xen
> kernel: 2.6.26-2-xen-amd64 #1 SMP Mon Jun 13 18:44:16 UTC 2011
> x86_64 GNU/Linux
Try to get the newest xfsprogs, maybe that's a bug in xfs_repair itself
that has been fixed. If that doesn't help, a newer kernel might solve
your problem.
Generally I've been able to fix all problems, and if not, xfsprogs has
received an update to fix a bug. But it's been a long time since the
latest bug, so an actual xfs_repair might help you.
--
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
next prev parent reply other threads:[~2011-08-08 11:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-08 10:05 "Corrupt dinode 6242615, (btree extents). This is a bug." Hanne Munkholm
2011-08-08 11:58 ` Michael Monnerie [this message]
2011-08-08 12:53 ` "Corrupt dinode 6242615, (btree extents). This is a bug."<o Hanne Munkholm
2011-08-08 13:12 ` Michael Monnerie
2011-08-08 23:58 ` "Corrupt dinode 6242615, (btree extents). This is a bug." Dave Chinner
2011-08-09 8:47 ` Hanne Munkholm
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=201108081358.43727@zmi.at \
--to=michael.monnerie@is.it-management.at \
--cc=hanne@binf.ku.dk \
--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