From: Eric Sandeen <sandeen@sandeen.net>
To: Andreas Vogler <andreas.vogler@geneon.de>
Cc: "xfs@oss.sgi.com" <xfs@oss.sgi.com>
Subject: Re: bad version from xfs_repair after raid crash
Date: Sat, 11 Aug 2012 16:45:52 -0500 [thread overview]
Message-ID: <5026D290.10209@sandeen.net> (raw)
In-Reply-To: <27CE2179D1925A4F9F4874725C3B4E0F0C5EFB6E94@COSMOS.nbg.geneon.de>
On 8/11/12 9:59 AM, Andreas Vogler wrote:
> Hi all,
>
> we had a crash of a raid 5 system. After rebuilding we could access one of two partitions. Upon mounting the second parttion we got an error "mount: Structure needs cleaning". So we tried using xfs_repair.
>
> Xfs_repair returns: "bad primary superblock - bad version number !!!"
>
> and tries to find a secondary superblock but gives up after scanning the volume.
>
> Looking at the superblock with xfs_db looks good as far as I can tell. Can anybody give me a hint what "bad version number" means?
There is a version number in the superblock itself, which must have features recognized by repair.
Is your xfsprogs version up to date?
You could also include another email with the output from xfs_db -c "sb 0" -c "p" /dev/blah
-Eric
> Thank you very much in advance.
>
> Andreas Vogler
>
> _______________________________________________
> xfs mailing list
> xfs@oss.sgi.com
> http://oss.sgi.com/mailman/listinfo/xfs
>
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2012-08-11 21:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-11 14:59 bad version from xfs_repair after raid crash Andreas Vogler
2012-08-11 21:45 ` Eric Sandeen [this message]
2012-08-12 7:49 ` AW: " Andreas Vogler
2012-08-12 21:37 ` Dave Chinner
2012-08-13 11:02 ` AW: " Andreas Vogler
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=5026D290.10209@sandeen.net \
--to=sandeen@sandeen.net \
--cc=andreas.vogler@geneon.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