xfs
[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: Eric Sandeen <sandeen@xxxxxxxxxxx>
Date: Fri, 18 Jan 2008 12:34:31 -0600
Cc: David Chinner <dgc@xxxxxxx>, xfs@xxxxxxxxxxx
In-reply-to: <9CE70E6ED2C2F64FB5537A2973FA4F0253595B@pvn-3001.purevideo.local>
References: <9CE70E6ED2C2F64FB5537A2973FA4F0253595A@pvn-3001.purevideo.local> <20080117234604.GG155407@sgi.com> <9CE70E6ED2C2F64FB5537A2973FA4F0253595B@pvn-3001.purevideo.local>
Sender: xfs-bounce@xxxxxxxxxxx
User-agent: Thunderbird 2.0.0.9 (X11/20071115)
Mark Magpayo wrote:
>>> 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).
>>
> 
> Is this supposed to be the proper output to the command above?
> 
> purenas:~# 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; done
> agcount = 64
> field dblock not found

...

I think dave had a typo, should be dblocks with an "s" on the end.

Feel free to wait for his confirmation, though, since this is surgery,
after all :)

-eric


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