From: Eric Sandeen <sandeen@sandeen.net>
To: Nicolas Stransky <nico@stransky.cx>
Cc: linux-xfs@oss.sgi.com
Subject: Re: Filesystem corrupted: "Sorry, could not find valid secondary superblock"
Date: Fri, 29 Jan 2010 12:16:02 -0600 [thread overview]
Message-ID: <4B6325E2.2040703@sandeen.net> (raw)
In-Reply-To: <hjv6l0$j2g$1@ger.gmane.org>
Nicolas Stransky wrote:
> OK here is a bunch of new stuff:
>
> # xfs_repair /dev/sda1
> Phase 1 - find and verify superblock...
> Phase 2 - using internal log
> - zero log...
> ERROR: The filesystem has valuable metadata changes in a log which needs
> to be replayed. Mount the filesystem to replay the log, and unmount it
> before re-running xfs_repair. If you are unable to mount the
> filesystem, then use the -L option to destroy the log and attempt a repair.
> Note that destroying the log may cause corruption -- please attempt a
> mount of the filesystem before doing this.
>
> # mount/ dev/sda1
> mount: Structure needs cleaning
dmesg at this point would be good
>
> Is the use of -L the only way to go? I wonder, since it will cause data
> loss...
if you can't mount it, yeah
>
> Also here is the output of xfs_db:
>
> # xfs_db /dev/sda1
> xfs_db> sb 0
> xfs_db> p
> magicnum = 0x58465342
ok, odd; you got:
>> # xfs_repair /dev/sda
>> Phase 1 - find and verify superblock...
>> bad primary superblock - bad magic number !!!
but this magic number is fine ...
-Eric
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2010-01-29 18:14 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
2010-01-29 17:12 ` Eric Sandeen
2010-01-29 17:41 ` Nicolas Stransky
2010-01-29 18:16 ` Eric Sandeen [this message]
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=4B6325E2.2040703@sandeen.net \
--to=sandeen@sandeen.net \
--cc=linux-xfs@oss.sgi.com \
--cc=nico@stransky.cx \
/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