From: Dave Chinner <david@fromorbit.com>
To: Marco Maisenhelder <marco@nethype.de>
Cc: xfs@oss.sgi.com
Subject: Re: fs corruption not detected by xfs_check or _repair
Date: Sat, 14 Aug 2010 09:05:25 +1000 [thread overview]
Message-ID: <20100813230525.GF10429@dastard> (raw)
In-Reply-To: <4C656149.6050604@nethype.de>
On Fri, Aug 13, 2010 at 05:14:17PM +0200, Marco Maisenhelder wrote:
> Hi list,
>
> I have a little bit of a problem after a catastrophic hardware
> failure (power supply went up in smoke and took half of my server
> with it - luckily only one of my raid5 disks though). My xfs data
> partition on my raid has some severe corruption that prevents me
> from accessing some files and directories on the partition. This is
> how the problem manifests itself:
>
> *marco:/etc# ls -lrt /store/xfs_corruption/x/
> ls: cannot access /store/xfs_corruption/x/db.backup2: Invalid argument
> ls: cannot access /store/xfs_corruption/x/db.backup1: Invalid argument
> total 0
> ?????????? ? ? ? ? ? db.backup2
> ?????????? ? ? ? ? ? db.backup1
What operation is returning EINVAL? strace should tell you that.
> *marco:/etc# xfs_info /store/
> meta-data=/dev/mapper/vgraid-rstore isize=256 agcount=48,
> agsize=11443904 blks
> = sectsz=512 attr=2
> data = bsize=4096 blocks=549307392, imaxpct=25
> = sunit=64 swidth=192 blks
> naming =version 2 bsize=4096
> log =internal bsize=4096 blocks=32768, version=2
> = sectsz=512 sunit=64 blks, lazy-count=1
> realtime =none extsz=4096 blocks=0, rtextents=0
>
> There's nothing in any of the system logs that would hint to the
> filesystem being corrupt.
>From the xfs_db output, all the directories look valid, so I'm not
sure what is causing the problem, yet. What kernel version and
xfs_repair version are you running?
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2010-08-13 23:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-13 15:14 fs corruption not detected by xfs_check or _repair Marco Maisenhelder
2010-08-13 20:40 ` Eric Sandeen
2010-08-13 23:05 ` Dave Chinner [this message]
[not found] ` <20100814183537.GA13734@puku.stupidest.org>
2010-08-14 22:53 ` Marco Maisenhelder
2010-08-15 9:22 ` 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=20100813230525.GF10429@dastard \
--to=david@fromorbit.com \
--cc=marco@nethype.de \
--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.