From: Thomas Walker <walker@stsci.edu>
To: David Chinner <dgc@sgi.com>
Cc: xfs@oss.sgi.com
Subject: Re: Should xfs_repair take this long?
Date: Fri, 16 Mar 2007 11:15:12 -0400 [thread overview]
Message-ID: <45FAB480.908@stsci.edu> (raw)
In-Reply-To: <20070315231031.GP6095633@melbourne.sgi.com>
I see in other posts that "parted" is sometimes a culprit in these
problems. Indeed, in my case I did use "parted" to create a gpt
partition table on these xfs volumes and I was asked my parted to use
the secondary signature.
--- snip ---
i also remember something about parted (maybe...) finding a backup gpt
signature at the end of a disk, and "helpfully" copying it over the
front end if so. This was a bug. sgi guys do you remember?
But for this one has to invoke parted, and commit the operations done,
am I right?
if I recall, even invoking parted could do this.
--- snip ---
So maybe I got bit the same way. parted may be overwritten something
at the head of the volume. Is there any way to repair the super block
though? It seems that everyone agrees xfs can't do anything until it
has a super block somewhere and I don't seem to have one. If there's no
way to repair, then what about recovery? I see mention of possibly
doing an xfs dump to another disk, reformat the original volume, and
then xfs restore back. Is there any online procedure for how to do that
if it applies to me here?
Thomas Walker
David Chinner wrote:
>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....
>
>
>
>
next prev parent reply other threads:[~2007-03-16 15:15 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-15 11:27 Should xfs_repair take this long? Thomas Walker
2007-03-15 14:04 ` Emmanuel Florac
2007-03-15 14:06 ` Thomas Walker
[not found] ` <20070315160309.652a6e0c@harpe.intellique.com>
[not found] ` <45F96150.50001@stsci.edu>
2007-03-15 15:23 ` Emmanuel Florac
2007-03-15 15:27 ` Thomas Walker
2007-03-15 23:10 ` David Chinner
2007-03-16 15:15 ` Thomas Walker [this message]
2007-03-16 19:37 ` David Chinner
-- strict thread matches above, loose matches on Subject: below --
2007-03-16 0:20 Thomas Walker
2007-03-16 1:32 ` David Chinner
2007-03-16 11:15 ` Thomas Walker
2007-03-16 19:20 ` David Chinner
2007-03-16 19:30 ` Eric Sandeen
2007-03-16 20:09 Thomas Walker
2007-03-16 20:52 ` David 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=45FAB480.908@stsci.edu \
--to=walker@stsci.edu \
--cc=dgc@sgi.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