xfs superblock corrupt,how to find next one!

xfs superblock corrupt,how to find next one!

[Bhaskar Chowdhury]

[-- Attachment #1: Type: text/plain, Size: 1136 bytes --]

  Hey Dave/Darrick,

  I was stumbled over this last week and ended up recreating(huh!) the
  fs from the scratch . Internet was littered with the information which
  I hardly could use. Oh, btw, I did stumble also in old google group
  where you suggested few stuff to do . 

  But alas, none come to handy. I have tried xfs_db and it spit out lots
  of info including AGS ,but..I had  a simple requirement , just to
  replace the corrupted super block with another good one. Which,
  everyone including you know it very well that can done in ext in a blink of an
  eye(my lack of understanding and exposure are pardonable I believe).

  But I couldn't find an easy way to recover the fs.I followed the
  repair ..get into db as I said ...

  Is it lurking somewhere which I failed to discover or it has been
  implemented in different way , which is not easily decipherable by
  ordinary users...not sure though.

  Kindly ,point out ,which route should one take , when they encounter
  that kind of a situation. Recreating the fs is not an or probably the
  least option to opt for. 


  Thanks,
  Bhaskar

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

Re: xfs superblock corrupt,how to find next one!

[Eric Sandeen]

[-- Attachment #1.1: Type: text/plain, Size: 1666 bytes --]

On 4/26/20 10:30 PM, Bhaskar Chowdhury wrote:
>  Hey Dave/Darrick,
> 
>  I was stumbled over this last week and ended up recreating(huh!) the
>  fs from the scratch . Internet was littered with the information which
>  I hardly could use. Oh, btw, I did stumble also in old google group
>  where you suggested few stuff to do .
>  But alas, none come to handy. I have tried xfs_db and it spit out lots
>  of info including AGS ,but..I had  a simple requirement , just to
>  replace the corrupted super block with another good one. Which,
>  everyone including you know it very well that can done in ext in a blink of an
>  eye(my lack of understanding and exposure are pardonable I believe).
> 
>  But I couldn't find an easy way to recover the fs.I followed the
>  repair ..get into db as I said ...
> 
>  Is it lurking somewhere which I failed to discover or it has been
>  implemented in different way , which is not easily decipherable by
>  ordinary users...not sure though.
> 
>  Kindly ,point out ,which route should one take , when they encounter
>  that kind of a situation. Recreating the fs is not an or probably the
>  least option to opt for.

(dropping LKML & personal emails from cc:)

You've provided a lot of general narrative here, but you have not provided any
particularly useful or detailed info about the problem you've run into.

I don't think anyone can help you yet, as you have not clearly stated the problem
you have encountered.

From your narrative, I assume that repair tells you the primary superblock is bad.

xfs_repair automatically scans for backup superblocks, though it can be slow.

-Eric


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 873 bytes --]