From: Carlos Maiolino <cmaiolino@redhat.com>
To: xfs@oss.sgi.com
Subject: Re: Superblock restore takes too long
Date: Thu, 19 Jul 2012 10:58:57 -0300 [thread overview]
Message-ID: <20120719135857.GA30881@andromeda.usersys.redhat.com> (raw)
In-Reply-To: <5C7FE4A5ADF52D46989166B4083DFF8F21ECE1C6@ilmbx02.IL.NDS.com>
On Thu, Jul 19, 2012 at 09:30:59AM +0000, Zak, Semion wrote:
> Hi,
>
> Corrupted Superblock restore takes too long because xfs_restore searches the
> disc for reserved Superblock.
>
> Is it possible accelerate the search, for example by giving to xfs_restore some
> hint (reserved Superblock LBA)?
>
Afaik there is no way to tell xfs_repair which superblock to use, but to be
honest how would you know which secondary superblock isn't corrupted? I can be
very wrong in this though
--
--Carlos
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2012-07-19 13:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-19 9:30 Superblock restore takes too long Zak, Semion
2012-07-19 13:58 ` Carlos Maiolino [this message]
2012-07-19 16:00 ` Eric Sandeen
2012-07-20 0:21 ` Dave Chinner
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=20120719135857.GA30881@andromeda.usersys.redhat.com \
--to=cmaiolino@redhat.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