From: Eric Sandeen <sandeen@sandeen.net>
To: Michael Monnerie <michael.monnerie@is.it-management.at>
Cc: xfs mailing list <xfs@oss.sgi.com>
Subject: Re: bad fs - xfs_repair 3.01 crashes on it
Date: Sun, 12 Jul 2009 13:52:20 -0500 [thread overview]
Message-ID: <4A5A30E4.6090309@sandeen.net> (raw)
In-Reply-To: <200907031320.48358@zmi.at>
Michael Monnerie wrote:
> Tonight our server rebooted, and I found in /var/log/warn that he was crying
> a lot about xfs since June 7 already:
>
> Jun 7 03:06:31 orion.i.zmi.at kernel: Filesystem "dm-0": corrupt inode 3857051697 ((a)extents = 5). Unmount and run xfs_repair.
> Jun 7 03:06:31 orion.i.zmi.at kernel: Pid: 23230, comm: xfs_fsr Tainted: G 2.6.27.21-0.1-xen #1
> Jun 7 03:06:31 orion.i.zmi.at kernel:
Hm, the other sort of interesting thing here is that a recently-reported
RH bug:
[Bug 510823] "Structure needs cleaning" when reading files from an XFS
partition (extent count for ino XYZ data fork too low (6) for file format)
also seems to -possibly- be related to an xfs_fsr run, and also is
related to extents in the wrong format. In that case it was the
opposite; an inode was found in btree format which had few enough
extents that it should have been in the extents format in the inode; in
your case, it looks like there were too many extents to fit in the
format it had...
Just out of curiosity, it looks like you have rather a lot of extended
attributes on at least the inode above, is that accurate? Or maybe
that's part of the corruption?
I'll focus on getting xfs_repair to cope first, but I wonder what
happened here...
Thanks,
-Eric
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2009-07-12 18:51 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-03 11:20 bad fs - xfs_repair 3.01 crashes on it Michael Monnerie
2009-07-03 18:34 ` Eric Sandeen
2009-07-04 5:43 ` Eric Sandeen
2009-07-12 17:02 ` Michael Monnerie
2009-07-12 18:09 ` Eric Sandeen
2009-07-12 18:52 ` Eric Sandeen [this message]
2009-07-12 22:08 ` Michael Monnerie
2009-07-14 4:13 ` [PATCH] xfs_repair - do not attempt to set shortform attr header when clearing Eric Sandeen
2009-07-14 5:42 ` Josef 'Jeff' Sipek
2009-07-14 6:05 ` Michael Monnerie
2009-07-14 6:16 ` Eric Sandeen
-- strict thread matches above, loose matches on Subject: below --
2009-08-31 6:40 bad fs - xfs_repair 3.01 crashes on it Michael Monnerie
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=4A5A30E4.6090309@sandeen.net \
--to=sandeen@sandeen.net \
--cc=michael.monnerie@is.it-management.at \
--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