xfs
[Top] [All Lists]

Re: 8.2TB->16.4TB xfs_growfs problem

To: sgixfs@xxxxxxxxxxxxxx
Subject: Re: 8.2TB->16.4TB xfs_growfs problem
From: Eric Sandeen <sandeen@xxxxxxxxxxx>
Date: Mon, 26 Feb 2007 13:07:12 -0600
Cc: xfs@xxxxxxxxxxx
In-reply-to: <Pine.OSX.4.64.0702261301250.1185@powerbook.localdomain>
References: <Pine.OSX.4.64.0702261301250.1185@powerbook.localdomain>
Sender: xfs-bounce@xxxxxxxxxxx
User-agent: Thunderbird 1.5.0.9 (X11/20070212)
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


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