Re: Repairing a possibly incomplete xfs_growfs command?

[Mark Goodwin <markgw@sgi.com>]

Mark Magpayo wrote:
>> -----Original Message-----
>> From: xfs-bounce@oss.sgi.com [mailto:xfs-bounce@oss.sgi.com] On Behalf
> Of
>> David Chinner
>> Sent: Tuesday, January 22, 2008 1:13 PM
>> To: Mark Magpayo
>> Cc: xfs@oss.sgi.com
>> Subject: Re: Repairing a possibly incomplete xfs_growfs command?
>>
>> 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?
> 
> Using version 2.9.4.  I may have forgotten to allocate more swap space
> (as was told in the manual given to me by the vendor), so would breaking
> out of the repair and restarting with more swap help out, or am I too
> deep (4 days) into it and should just let it run?

cat /proc/meminfo for this machine and post it here. If it's swapping,
adding more swap wont speed it up. If it runs out of swap the repair
will stop anyway ;-)

Cheers
-- 

  Mark Goodwin                                  markgw@sgi.com
  Engineering Manager for XFS and PCP    Phone: +61-3-99631937
  SGI Australian Software Group           Cell: +61-4-18969583
-------------------------------------------------------------