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 11:12:36 -0600
Cc: linux-xfs@xxxxxxxxxxx
In-reply-to: <hjv12n$r2o$1@xxxxxxxxxxxxx>
References: <hjus58$6oi$1@xxxxxxxxxxxxx> <4B63010D.1080608@xxxxxxxxxxx> <hjv12n$r2o$1@xxxxxxxxxxxxx>
User-agent: Thunderbird 2.0.0.23 (Macintosh/20090812)
Nicolas Stransky wrote:
> 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 !!!

xfs_db /dev/sda
xfs_db> sb 0
xfs_db> p

might be interesting to see what's there.

-Eric

> 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@xxxxxxxxxxx
> http://oss.sgi.com/mailman/listinfo/xfs
> 

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