From: Nicolas Stransky <nico@stransky.cx>
To: linux-xfs@oss.sgi.com
Subject: Re: Filesystem corrupted: "Sorry, could not find valid secondary superblock"
Date: Fri, 29 Jan 2010 11:06:48 -0500 [thread overview]
Message-ID: <hjv12n$r2o$1@ger.gmane.org> (raw)
In-Reply-To: <4B63010D.1080608@sandeen.net>
On 1/29/10 10:38 AM, Eric Sandeen wrote:
> xfs_repair needs to be smarter about this; I at least wish it'd say
> -why- the candidate was not valid.
>
> Can you include the whole repair output? Then maybe we can direct
> you to some xfs_db jujitsu to examine the fs.
>
> Trying newer xfsprogs would not be a -bad- idea...
>
> -Eric
The output is as follows:
# xfs_repair /dev/sda
Phase 1 - find and verify superblock...
bad primary superblock - bad magic number !!!
attempting to find secondary superblock...
......................
found candidate secondary superblock...
unable to verify superblock, continuing...
......................
found candidate secondary superblock...
unable to verify superblock, continuing...
......................
[The previous one repeats hundreds of times over many hours]
......................
Sorry, could not find valid secondary superblock
Exiting now.
I am trying right now xfsprogs 3.1.0 from Debian testing, will see what
it gives...
Thanks!
NS
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2010-01-29 16:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-29 14:42 Filesystem corrupted: "Sorry, could not find valid secondary superblock" Nicolas STRANSKY
2010-01-29 15:38 ` Eric Sandeen
2010-01-29 16:06 ` Nicolas Stransky [this message]
2010-01-29 17:12 ` Eric Sandeen
2010-01-29 17:41 ` Nicolas Stransky
2010-01-29 18:16 ` Eric Sandeen
2010-01-29 19:58 ` Nicolas Stransky
2010-02-01 17:29 ` Nicolas Stransky
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='hjv12n$r2o$1@ger.gmane.org' \
--to=nico@stransky.cx \
--cc=linux-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