From: Thomas Walker <walker@stsci.edu>
To: Emmanuel Florac <eflorac@intellique.com>
Cc: xfs@oss.sgi.com
Subject: Re: Should xfs_repair take this long?
Date: Thu, 15 Mar 2007 10:06:42 -0400 [thread overview]
Message-ID: <45F952F2.6000008@stsci.edu> (raw)
In-Reply-To: <20070315150422.7bc5d178@harpe.intellique.com>
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...
Thomas Walker
Emmanuel Florac wrote:
>Le Thu, 15 Mar 2007 07:27:08 -0400
>Thomas Walker <walker@stsci.edu> écrivait:
>
>
>
>>xfs_repair -o assume_xfs /dev/mapper/vg0-hladata3
>>
>> This command has been running for two days now.
>>
>>
>
>Is there any output from xfs_repair ? This doesn't sound good. I've run
>xfs_repair on some badly corrupted fs up to 13 TB, and it never took
>more than a couple of minutes.
>
>
>
next prev parent reply other threads:[~2007-03-15 14:06 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 [this message]
[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
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=45F952F2.6000008@stsci.edu \
--to=walker@stsci.edu \
--cc=eflorac@intellique.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