All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bhaskar Chowdhury <unixbhaskar@gmail.com>
To: david@fromorbit.com
Cc: LinuxKernel <linux-kernel@vger.kernel.org>,
	linux-xfs@vger.kernel.org, darrick.wong@oracle.com
Subject: xfs superblock corrupt,how to find next one!
Date: Mon, 27 Apr 2020 09:00:23 +0530	[thread overview]
Message-ID: <20200427033023.GA30304@Slackware> (raw)

[-- 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 --]

             reply	other threads:[~2020-04-27  3:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-27  3:30 Bhaskar Chowdhury [this message]
2020-04-27 13:30 ` xfs superblock corrupt,how to find next one! Eric Sandeen

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=20200427033023.GA30304@Slackware \
    --to=unixbhaskar@gmail.com \
    --cc=darrick.wong@oracle.com \
    --cc=david@fromorbit.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-xfs@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.