public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@sandeen.net>
To: sgixfs@foxengines.net
Cc: xfs@oss.sgi.com
Subject: Re: 8.2TB->16.4TB xfs_growfs problem
Date: Mon, 26 Feb 2007 13:07:12 -0600	[thread overview]
Message-ID: <45E32FE0.4070204@sandeen.net> (raw)
In-Reply-To: <Pine.OSX.4.64.0702261301250.1185@powerbook.localdomain>

XFS User wrote:
> Hello,
> 
> I am experiencing a problem that I'm not sure how to resolve. I do not see
> this in the FAQ, nor have I found it in Bugzilla or the mailing lists, 
> (they both seemed to be having search problems last week which prevented 
> me from using them, I used Google to search into the site so I might've missed 
> something).
> 
> In summary, I have an 8.2TB filesystem on an 16.4TB LVM2 volume on a
> Linux 2.6.18 x86_64 with 4GB RAM.
> If I issue the 'xfs_growfs /mounted_volume' command, the command will
> complete without printing any errors and the command exits on 0.
> 
> I can umount, then mount again, see the new 16TB volume.
> 
> If for any reason, I run xfs_repair, all changes will be lost and the
> filesystem size will revert to it's original size (e.g it'll shrink
> back down to 8.2TB).

There have been userspace & kernelspace fixes to growfs lately...

TAKE 959492 - xfs_growfs should return an error on failure
http://oss.sgi.com/archives/xfs/2006-12/msg00224.html

TAKE 959978 - growing an XFS filesystem by more than 2TB is broken
http://oss.sgi.com/archives/xfs/2007-01/msg00082.html

I'd make sure you have those fixes, first.

-Eric

      reply	other threads:[~2007-02-26 19:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-26 18:09 8.2TB->16.4TB xfs_growfs problem XFS User
2007-02-26 19:07 ` Eric Sandeen [this message]

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=45E32FE0.4070204@sandeen.net \
    --to=sandeen@sandeen.net \
    --cc=sgixfs@foxengines.net \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox