From: Christoph Hellwig <hch@infradead.org>
To: Marco Maisenhelder <marco@nethype.de>
Cc: Chris Wedgwood <cw@f00f.org>, xfs@oss.sgi.com
Subject: Re: fs corruption not detected by xfs_check or _repair
Date: Sun, 15 Aug 2010 05:22:22 -0400 [thread overview]
Message-ID: <20100815092222.GA1801@infradead.org> (raw)
In-Reply-To: <4C671E83.4060106@nethype.de>
On Sun, Aug 15, 2010 at 12:53:55AM +0200, Marco Maisenhelder wrote:
> Chris Wedgwood wrote:
> >On Fri, Aug 13, 2010 at 05:14:17PM +0200, Marco Maisenhelder wrote:
> >
> >>*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
> >
> >where these created with inode64 and now mounted w/o that option? (in
> >which case inodes > 32-bit are inaccessible)
>
> I wasn't even aware of the option - I guess I should have spent more
> time reading the FAQ before trying to find a more complex problem :(
>
> inode64 was my problem - mouting the partition with -o inode64 fixes
> all weirdness.
FYI: starting from kernel 2.6.35 you can access all the inodes even
without -o inode64 and won't get these strange errors.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2010-08-15 9:22 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
[not found] ` <20100814183537.GA13734@puku.stupidest.org>
2010-08-14 22:53 ` Marco Maisenhelder
2010-08-15 9:22 ` Christoph Hellwig [this message]
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=20100815092222.GA1801@infradead.org \
--to=hch@infradead.org \
--cc=cw@f00f.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox