xfs
[Top] [All Lists]

Re: Filesystem corrupted: "Sorry, could not find valid secondary superbl

To: Nicolas Stransky <nico@xxxxxxxxxxx>
Subject: Re: Filesystem corrupted: "Sorry, could not find valid secondary superblock"
From: Eric Sandeen <sandeen@xxxxxxxxxxx>
Date: Fri, 29 Jan 2010 12:16:02 -0600
Cc: linux-xfs@xxxxxxxxxxx
In-reply-to: <hjv6l0$j2g$1@xxxxxxxxxxxxx>
References: <hjus58$6oi$1@xxxxxxxxxxxxx> <4B63010D.1080608@xxxxxxxxxxx> <hjv12n$r2o$1@xxxxxxxxxxxxx> <4B631704.8080902@xxxxxxxxxxx> <hjv6l0$j2g$1@xxxxxxxxxxxxx>
User-agent: Thunderbird 2.0.0.23 (Macintosh/20090812)
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

<Prev in Thread] Current Thread [Next in Thread>