public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Ashley Oviatt <ashovi@gmail.com>
To: xfs@oss.sgi.com
Subject: xfs_repair
Date: Thu, 19 Jun 2008 13:27:14 -0600	[thread overview]
Message-ID: <485AB312.4040608@gmail.com> (raw)

I am having the same problem as the person in this thread (Which problem 
is xfs_repair has been running for 16 hours on a 1 TB raid array):

http://www.linux.sgi.com/archives/xfs/2007-03/msg00061.html

It gave the same errors as this thread, saying that it could not use any 
of the super blocks it found. The last email in the thread says:

-----------------------------------------

xfs-repair did find candidate secondary superblocks - it discarded them
for some reason or another. If they were ok, all repair would have done
is copied them to block zero and then continued.

I'm suggesting that you manually do this step, and then see if repair
will run.

>/    Before wrapping this up, if you could just clarify a couple things.  If I/
>/    look at the bytes at the beginning of each physical part of the LVM's,/
>/    what am I looking for?  "XFSB"?/

yes.

>/    If I do find that byte string, why/
>/    couldn't xfs_repair find it when it did the scan and what do I do with it/
>/    if I do find one?/

As I said above, xfs-repair did find some, but rejected them for some
(unknown) reason. if you find one, copy it over block zero of the partition,
and see if repair will run. Like I said, though, you'll probably want to
back up th partition first, or at least run repair in no-modify mode.

--------------------------------------

The poster, Dave Chinner, says to manually copy the superblock to the 
right place, but not how to do it. I am familiar with dd, but would like 
to know the exact command or steps to take to replace the primary 
superblock manually with a secondary superblock.

I am using slackware linux 10 with an intel raid card.

Ashley


[[HTML alternate version deleted]]

             reply	other threads:[~2008-06-19 19:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-19 19:27 Ashley Oviatt [this message]
  -- strict thread matches above, loose matches on Subject: below --
2013-11-14 17:51 xfs_repair Roman Hlynovskiy
2013-11-14 18:04 ` xfs_repair 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=485AB312.4040608@gmail.com \
    --to=ashovi@gmail.com \
    --cc=xfs@oss.sgi.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox