From: Thomas Walker <walker@stsci.edu>
To: xfs@oss.sgi.com
Subject: Should xfs_repair take this long?
Date: Thu, 15 Mar 2007 07:27:08 -0400 [thread overview]
Message-ID: <45F92D8C.3090708@stsci.edu> (raw)
I am trying to restore a corrupt xfs partition. It is 6TB total, it
is an LVM of two 3TB fiber channel SAN volumes. The host is running
RHEL4, 2.6.9-42.0.2.ELsmp, and the version of xfsprogs is
xfsprogs-2.6.13-2. The host has four threaded AMD Opterons, 4GB of RAM
and 2GB of swap located on an internal SCSI disk. It is unclear how the
xfs partition was damaged, but it reports a bad superblock and will not
mount. I am running this command;
xfs_repair -o assume_xfs /dev/mapper/vg0-hladata3
This command has been running for two days now. There is cpu
activity and i/o activity on the physical SAN. There is some swapping
but not an unusual amount and swapon -s shows only a small amount in
use. I have seen information implying xfs_repair needs a large amount
of memory to work well, otherwise it will take a long time. My question
is, giving my setup, is there an estimate of how long I should wait
before expecting a result? Should I add swap space? Is there anything
else I should do?
thanks in advance for any help.
Thomas Walker
next reply other threads:[~2007-03-15 11:39 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-15 11:27 Thomas Walker [this message]
2007-03-15 14:04 ` Should xfs_repair take this long? 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
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=45F92D8C.3090708@stsci.edu \
--to=walker@stsci.edu \
--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