[Top] [All Lists]

Re: Repairing a possibly incomplete xfs_growfs command?

To: Mark Magpayo <mmagpayo@xxxxxxxxxxxxx>
Subject: Re: Repairing a possibly incomplete xfs_growfs command?
From: David Chinner <dgc@xxxxxxx>
Date: Fri, 18 Jan 2008 10:46:04 +1100
Cc: xfs@xxxxxxxxxxx
In-reply-to: <9CE70E6ED2C2F64FB5537A2973FA4F0253595A@xxxxxxxxxxxxxxxxxxxxxxxx>
References: <9CE70E6ED2C2F64FB5537A2973FA4F0253594C@xxxxxxxxxxxxxxxxxxxxxxxx> <20080117030111.GH155259@xxxxxxx> <9CE70E6ED2C2F64FB5537A2973FA4F02535951@xxxxxxxxxxxxxxxxxxxxxxxx> <20080117231517.GF155407@xxxxxxx> <9CE70E6ED2C2F64FB5537A2973FA4F0253595A@xxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xfs-bounce@xxxxxxxxxxx
User-agent: Mutt/
On Thu, Jan 17, 2008 at 03:29:17PM -0800, Mark Magpayo wrote:
> This is quite a relief to know that this is a fairly straightforward
> fix!  What luck that you had encountered it recently, I really
> appreciate the help.  Here's my uname output:
> Linux purenas #1 SMP Fri Oct 19 16:45:15 EDT 2007 x86_64
> GNU/Linux
> Maybe you guys fixed the bug already?

/me breathes a sigh of relief

I think we have:


[XFS] Make growfs work for amounts greater than 2TB
> iirc, I may have run xfs_growfs with an older version of xfsprogs, then
> was advised to update to the newest and try it again.  I may have run it
> on a version that still contained the bug?

Kernel bug, not userspace bug, AFAICT.

> So is this all I need then prior to an xfs_repair?:
> > # for i in `seq 0 1 63`; do
> > > xfs_db -x -c "sb $i" -c 'write agcount 64' -c 'write dblock 4761733120'
> > /dev/vg0/lv0

Yes, I think that is all that is necessary (that+repair was what fixed
the problem at the customer site successfully).


Dave Chinner
Principal Engineer
SGI Australian Software Group

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