Re: Should xfs_repair take this long?

[Thomas Walker <walker@xxxxxxxxx>]

  Ok, here's the output of the command you wanted.  I ran it on both of the xfs 
file systems we have, both say bad superblock when trying to mount;

[root@hla-ags ~]# dd if=/dev/mapper/vg0-hladata3 bs=512 count=1 iflag=direct 2> 
/dev/null | od -Ax -x
000000

[root@hla-ags ~]# dd if=/dev/mapper/vg1-hladata2 bs=512 count=1 iflag=direct 2> 
/dev/null | od -Ax -x
000000

   [root@hla-ags ~]# mount /hladata2
mount: wrong fs type, bad option, bad superblock on /dev/vg0/hladata3,
       or too many mounted file systems

  Thomas Walker


---- Original message ----
>Date: Fri, 16 Mar 2007 10:10:31 +1100
>From: David Chinner <dgc@xxxxxxx>  
>Subject: Re: Should xfs_repair take this long?  
>To: Thomas Walker <walker@xxxxxxxxx>
>Cc: Emmanuel Florac <eflorac@xxxxxxxxxxxxxx>, xfs@xxxxxxxxxxx
>
>On Thu, Mar 15, 2007 at 10:06:42AM -0400, Thomas Walker wrote:
>> 
>>     The terminal shows a lot of "." dots running across the screen 
>> quickly, and every few hours it says this;
>> 
>> 
>> .....................................................found candidate 
>> secondary superblock...
>> unable to verify superblock, continuing...
>> found candidate secondary superblock...
>> unable to verify superblock, continuing...
>
>The primary superblock is not good, and it's trying to find a valid
>secondary superblock. Doesn't sound promising so far - reapir can't
>start until a valid superblok is found....
>
>Can you dump the first sector of the device the fielsystem is
>on:
>
># dd if=/dev/mapper/vg0-hladata3 bs=512 count=1 iflag=direct 2> /dev/null | od 
>-Ax -x
>
>So we can see if that really holds a primary XFS superblock?
>
>Cheers,
>
>Dave.
>-- 
>Dave Chinner
>Principal Engineer
>SGI Australian Software Group