From: David Chinner <dgc@sgi.com>
To: Mark Magpayo <mmagpayo@purevideo.com>
Cc: xfs@oss.sgi.com
Subject: Re: Repairing a possibly incomplete xfs_growfs command?
Date: Fri, 18 Jan 2008 10:46:04 +1100 [thread overview]
Message-ID: <20080117234604.GG155407@sgi.com> (raw)
In-Reply-To: <9CE70E6ED2C2F64FB5537A2973FA4F0253595A@pvn-3001.purevideo.local>
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 2.6.16.55-c1 #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:
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=20f4ebf2bf2f57c1a9abb3655391336cc90314b3
[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).
Cheers,
Dave.
--
Dave Chinner
Principal Engineer
SGI Australian Software Group
next prev parent reply other threads:[~2008-01-17 23:46 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-16 23:19 Repairing a possibly incomplete xfs_growfs command? Mark Magpayo
2008-01-17 2:31 ` Eric Sandeen
2008-01-17 3:01 ` David Chinner
2008-01-17 17:29 ` Mark Magpayo
2008-01-17 19:10 ` Eric Sandeen
2008-01-17 20:04 ` Mark Magpayo
2008-01-17 22:19 ` Eric Sandeen
2008-01-17 22:47 ` Nathan Scott
2008-01-17 23:15 ` David Chinner
2008-01-17 23:29 ` Mark Magpayo
2008-01-17 23:46 ` David Chinner [this message]
2008-01-18 17:50 ` Mark Magpayo
2008-01-18 18:34 ` Eric Sandeen
2008-01-19 0:40 ` David Chinner
2008-01-22 19:40 ` Mark Magpayo
2008-01-22 21:13 ` David Chinner
2008-01-22 21:46 ` Mark Magpayo
2008-01-22 22:48 ` Mark Goodwin
2008-01-22 22:50 ` Mark Magpayo
2008-01-23 2:57 ` Barry Naujok
2008-01-23 17:24 ` Mark Magpayo
2008-01-24 1:02 ` Barry Naujok
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080117234604.GG155407@sgi.com \
--to=dgc@sgi.com \
--cc=mmagpayo@purevideo.com \
--cc=xfs@oss.sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.