| To: | Mark Magpayo <mmagpayo@xxxxxxxxxxxxx> |
|---|---|
| Subject: | Re: Repairing a possibly incomplete xfs_growfs command? |
| From: | David Chinner <dgc@xxxxxxx> |
| Date: | Sat, 19 Jan 2008 11:40:18 +1100 |
| Cc: | David Chinner <dgc@xxxxxxx>, xfs@xxxxxxxxxxx |
| In-reply-to: | <9CE70E6ED2C2F64FB5537A2973FA4F0253595B@xxxxxxxxxxxxxxxxxxxxxxxx> |
| References: | <9CE70E6ED2C2F64FB5537A2973FA4F0253595A@xxxxxxxxxxxxxxxxxxxxxxxx> <20080117234604.GG155407@xxxxxxx> <9CE70E6ED2C2F64FB5537A2973FA4F0253595B@xxxxxxxxxxxxxxxxxxxxxxxx> |
| Sender: | xfs-bounce@xxxxxxxxxxx |
| User-agent: | Mutt/1.4.2.1i |
On Fri, Jan 18, 2008 at 09:50:37AM -0800, 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 > parsing error Ah - As eric pointed out, that should be "dblocks". Cheers, Dave. -- Dave Chinner Principal Engineer SGI Australian Software Group |
| Previous by Date: | 2.6.24-rc8: possible circular locking dependency detected, Christian Kujau |
|---|---|
| Next by Date: | Re: [REVIEW 1/2] Case insensitive support for XFS - kernel patch, Eric Sandeen |
| Previous by Thread: | Re: Repairing a possibly incomplete xfs_growfs command?, Eric Sandeen |
| Next by Thread: | RE: Repairing a possibly incomplete xfs_growfs command?, Mark Magpayo |
| Indexes: | [Date] [Thread] [Top] [All Lists] |