Re: Repairing a possibly incomplete xfs_growfs command?

["Barry Naujok" <bnaujok@xxxxxxx>]

On Thu, 24 Jan 2008 04:24:17 +1100, Mark Magpayo <mmagpayo@xxxxxxxxxxxxx>  
wrote:
> > 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.
Breaking repair is fine.

> Are there any more phases after this by the way?
Checking nlink counts in Phase 7 is the last.

I would run xfs_check to see if there are any errors remaining.

The other thing I can suggest is to run an older repair from the
2.8.x series (2.8.21) with the options "-M -o bhash=512". This
should finish.

Regards,
Barry.