xfs
[Top] [All Lists]

RE: Repairing a possibly incomplete xfs_growfs command?

To: "Barry Naujok" <bnaujok@xxxxxxx>
Subject: RE: Repairing a possibly incomplete xfs_growfs command?
From: "Mark Magpayo" <mmagpayo@xxxxxxxxxxxxx>
Date: Wed, 23 Jan 2008 09:24:17 -0800
Cc: <xfs@xxxxxxxxxxx>
In-reply-to: <op.t5c3ubfg3jf8g2@pc-bnaujok.melbourne.sgi.com>
References: <9CE70E6ED2C2F64FB5537A2973FA4F0253595A@pvn-3001.purevideo.local> <20080117234604.GG155407@sgi.com> <9CE70E6ED2C2F64FB5537A2973FA4F0253595B@pvn-3001.purevideo.local> <20080119004018.GH155407@sgi.com> <9CE70E6ED2C2F64FB5537A2973FA4F0253596D@pvn-3001.purevideo.local> <op.t5c3ubfg3jf8g2@pc-bnaujok.melbourne.sgi.com>
Sender: xfs-bounce@xxxxxxxxxxx
Thread-index: AchdauQ1LMoKfLlGTMic03LLn0M+6gAeoQ+w
Thread-topic: Repairing a possibly incomplete xfs_growfs command?
> 
> Was it stuck on Phase 6 all that time? With only 1GB of RAM (from your
> meminfo output) and 18TB filesystem, Phases 3 and 4 will take a very
> long time due to swapping.

It's been stuck on Phase 6 since I came back to check on it on Monday.  


> 
> Phase 6 in your scenario should be relatively quick and light on
> memory usage (500MB as reported in your other email).
> 
> It is feasible it is deadlocked by trying to double-access a buffer,
> or access a buffer that wasn't released. This is an unlikely scenario,
> but it is possible.

Could I break out of the process here?  Seems like most of the repair
work has been done...  Then again, I imagine traversing the filesystem
is a pretty important step.

Are there any more phases after this by the way?

Thanks,

Mark



<Prev in Thread] Current Thread [Next in Thread>