From: David Chinner <dgc@sgi.com>
To: Mark Magpayo <mmagpayo@purevideo.com>
Cc: xfs@oss.sgi.com
Subject: Re: Repairing a possibly incomplete xfs_growfs command?
Date: Wed, 23 Jan 2008 08:13:11 +1100 [thread overview]
Message-ID: <20080122211311.GA155259@sgi.com> (raw)
In-Reply-To: <9CE70E6ED2C2F64FB5537A2973FA4F0253596D@pvn-3001.purevideo.local>
On Tue, Jan 22, 2008 at 11:40:52AM -0800, Mark Magpayo wrote:
> Any ideas on how long the xfs_repair is supposed to take on 18TB? I
> started it Friday nite, and it's now Tuesday afternoon. It's stuck
> here:
>
> Phase 5 - rebuild AG headers and trees...
> - reset superblock...
> Phase 6 - check inode connectivity...
> - resetting contents of realtime bitmap and summary inodes
> - traversing filesystem ...
>
> I figure traversing a filesystem of 18TB takes a while, but does 4 days
> sound right?
Yes, it can if it's swapping like mad because you don't have enough
RAM in the machine. Runtime is also detemrined by how many inodes there
are in the filesystem - do you know how many there are? Also, more
recent xfs_repair versions tend to be faster - what version are you
using again?
Cheers,
Dave.
--
Dave Chinner
Principal Engineer
SGI Australian Software Group
next prev parent reply other threads:[~2008-01-22 21:13 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-16 23:19 Repairing a possibly incomplete xfs_growfs command? Mark Magpayo
2008-01-17 2:31 ` Eric Sandeen
2008-01-17 3:01 ` David Chinner
2008-01-17 17:29 ` Mark Magpayo
2008-01-17 19:10 ` Eric Sandeen
2008-01-17 20:04 ` Mark Magpayo
2008-01-17 22:19 ` Eric Sandeen
2008-01-17 22:47 ` Nathan Scott
2008-01-17 23:15 ` David Chinner
2008-01-17 23:29 ` Mark Magpayo
2008-01-17 23:46 ` David Chinner
2008-01-18 17:50 ` Mark Magpayo
2008-01-18 18:34 ` Eric Sandeen
2008-01-19 0:40 ` David Chinner
2008-01-22 19:40 ` Mark Magpayo
2008-01-22 21:13 ` David Chinner [this message]
2008-01-22 21:46 ` Mark Magpayo
2008-01-22 22:48 ` Mark Goodwin
2008-01-22 22:50 ` Mark Magpayo
2008-01-23 2:57 ` Barry Naujok
2008-01-23 17:24 ` Mark Magpayo
2008-01-24 1:02 ` Barry Naujok
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=20080122211311.GA155259@sgi.com \
--to=dgc@sgi.com \
--cc=mmagpayo@purevideo.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