xfs_growfs: XFS_IOC_FSGROWFSDATA xfsctl failed: Argument list too long

xfs_growfs: XFS_IOC_FSGROWFSDATA xfsctl failed: Argument list too long

[Benjamin Lau]

Hello,

I've been using XFS for about a decade and have never run across this
error before... then again I've never grown a file system to as large
as size as this one either.

First a little about the setup.  I have a large disk array that I use
for storing media.  I've been growing it a bit at a time over the past
2 years.  To accomplish this I have setup a collection of RAIDed
drives that are then bound together using LVM so I can increase the
size of the array as I acquire new disks.  So far this process has
worked fine while growing the array from it's initial size of 2TB to
approximately 9TB.

Today I was adding another collection of drives (6 2TB drives in a
RAID-5 configuration for an additional 10TB or storage) and performed
the usual steps[1] to grow extend the LVM group and grow the file
system using xfs_growfs.  When I encountered the following error:

xfs_growfs: XFS_IOC_FSGROWFSDATA xfsctl failed: Argument list too long [2]

I'm guessing something about my configuration is funky... but I'm not
sure what and was wondering if anybody on this list had any thoughts
or suggestions of things to try.  I'm not sure what information I
should provide to help with tracking down this issue... but I can
provide anything that is requested.  I've included some additional
data below.

Everything is working fine otherwise and the file system is up and
running and able to provide the usual services.

Thanks in advance,

Ben

[1] Usual set of commands to grow the filesystem:
pvcreate /dev/md7
vgextend vg00 /dev/md7
lvextend --extents +100%FREE /dev/vg00/lv_raid
xfs_growfs /dev/vg00/lv_raid

[2] Full output of xfs_growfs:
meta-data=/dev/mapper/vg00-lv_raid isize=256    agcount=40, agsize=61047552 blks
            =                       sectsz=512   attr=2
data     =                       bsize=4096   blocks=2441868288, imaxpct=25
         =                       sunit=0      swidth=0 blks
naming   =version 2              bsize=4096
log      =internal               bsize=4096   blocks=32768, version=2
         =                       sectsz=512   sunit=0 blks, lazy-count=0
realtime =none                   extsz=4096   blocks=0, rtextents=0
xfs_growfs: XFS_IOC_FSGROWFSDATA xfsctl failed: Argument list too long

OS/Kernel Info:
Debian Lenny
Linux bigmama 2.6.30-2-686-bigmem #1 SMP Sat Sep 26 02:30:18 UTC 2009
i686 GNU/Linux

Custom kernel with bigmem enabled to allow access to memory about 4GB
on a 32-bit CPU

/proc/cpuinfo:


processor	: 0
vendor_id	: GenuineIntel
cpu family	: 15
model		: 4
model name	: Intel(R) Xeon(TM) CPU 3.20GHz
stepping	: 1
cpu MHz		: 3200.222
cache size	: 1024 KB
physical id	: 0
siblings	: 2
core id		: 0
cpu cores	: 1
apicid		: 0
initial apicid	: 0
fdiv_bug	: no
hlt_bug		: no
f00f_bug	: no
coma_bug	: no
fpu		: yes
fpu_exception	: yes
cpuid level	: 5
wp		: yes
flags		: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov
pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx lm
constant_tsc pebs bts pni dtes64 monitor ds_cpl cid cx16 xtpr
bogomips	: 6400.44
clflush size	: 64
power management:

processor	: 1
vendor_id	: GenuineIntel
cpu family	: 15
model		: 4
model name	: Intel(R) Xeon(TM) CPU 3.20GHz
stepping	: 1
cpu MHz		: 3200.222
cache size	: 1024 KB
physical id	: 0
siblings	: 2
core id		: 0
cpu cores	: 1
apicid		: 1
initial apicid	: 1
fdiv_bug	: no
hlt_bug		: no
f00f_bug	: no
coma_bug	: no
fpu		: yes
fpu_exception	: yes
cpuid level	: 5
wp		: yes
flags		: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov
pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx lm
constant_tsc pebs bts pni dtes64 monitor ds_cpl cid cx16 xtpr
bogomips	: 6400.66
clflush size	: 64
power management:

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

Re: xfs_growfs: XFS_IOC_FSGROWFSDATA xfsctl failed: Argument list too long

[James Braid]

On Fri, Apr 30, 2010 at 01:07, Benjamin Lau <benjamin.a.lau@gmail.com> wrote:
> [2] Full output of xfs_growfs:
> meta-data=/dev/mapper/vg00-lv_raid isize=256    agcount=40, agsize=61047552 blks
>            =                       sectsz=512   attr=2
> data     =                       bsize=4096   blocks=2441868288, imaxpct=25
>         =                       sunit=0      swidth=0 blks
> naming   =version 2              bsize=4096
> log      =internal               bsize=4096   blocks=32768, version=2
>         =                       sectsz=512   sunit=0 blks, lazy-count=0
> realtime =none                   extsz=4096   blocks=0, rtextents=0
> xfs_growfs: XFS_IOC_FSGROWFSDATA xfsctl failed: Argument list too long
>
> OS/Kernel Info:
> Debian Lenny
> Linux bigmama 2.6.30-2-686-bigmem #1 SMP Sat Sep 26 02:30:18 UTC 2009
> i686 GNU/Linux

Filesystems >16TB aren't supported on 32-bit machines - it looks like
your growfs is going to exceed that limit. Time to upgrade! ;)

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

Re: xfs_growfs: XFS_IOC_FSGROWFSDATA xfsctl failed: Argument list too long

[Benjamin Lau]

Ah,,, okay well that's good to know... I guess it is time to upgrade then...

Thanks,

Ben

On Thu, Apr 29, 2010 at 5:41 PM, James Braid <jamesb@loreland.org> wrote:
> On Fri, Apr 30, 2010 at 01:07, Benjamin Lau <benjamin.a.lau@gmail.com> wrote:
>> [2] Full output of xfs_growfs:
>> meta-data=/dev/mapper/vg00-lv_raid isize=256    agcount=40, agsize=61047552 blks
>>            =                       sectsz=512   attr=2
>> data     =                       bsize=4096   blocks=2441868288, imaxpct=25
>>         =                       sunit=0      swidth=0 blks
>> naming   =version 2              bsize=4096
>> log      =internal               bsize=4096   blocks=32768, version=2
>>         =                       sectsz=512   sunit=0 blks, lazy-count=0
>> realtime =none                   extsz=4096   blocks=0, rtextents=0
>> xfs_growfs: XFS_IOC_FSGROWFSDATA xfsctl failed: Argument list too long
>>
>> OS/Kernel Info:
>> Debian Lenny
>> Linux bigmama 2.6.30-2-686-bigmem #1 SMP Sat Sep 26 02:30:18 UTC 2009
>> i686 GNU/Linux
>
> Filesystems >16TB aren't supported on 32-bit machines - it looks like
> your growfs is going to exceed that limit. Time to upgrade! ;)
>

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

Re: xfs_growfs: XFS_IOC_FSGROWFSDATA xfsctl failed: Argument list too long

[Eric Sandeen]

James Braid wrote:
> On Fri, Apr 30, 2010 at 01:07, Benjamin Lau <benjamin.a.lau@gmail.com> wrote:
>> [2] Full output of xfs_growfs:
>> meta-data=/dev/mapper/vg00-lv_raid isize=256    agcount=40, agsize=61047552 blks
>>            =                       sectsz=512   attr=2
>> data     =                       bsize=4096   blocks=2441868288, imaxpct=25
>>         =                       sunit=0      swidth=0 blks
>> naming   =version 2              bsize=4096
>> log      =internal               bsize=4096   blocks=32768, version=2
>>         =                       sectsz=512   sunit=0 blks, lazy-count=0
>> realtime =none                   extsz=4096   blocks=0, rtextents=0
>> xfs_growfs: XFS_IOC_FSGROWFSDATA xfsctl failed: Argument list too long
>>
>> OS/Kernel Info:
>> Debian Lenny
>> Linux bigmama 2.6.30-2-686-bigmem #1 SMP Sat Sep 26 02:30:18 UTC 2009
>> i686 GNU/Linux
> 
> Filesystems >16TB aren't supported on 32-bit machines - it looks like
> your growfs is going to exceed that limit. Time to upgrade! ;)

We probably should, though, change the error from E2BIG to EFBIG so we
get "File too large" instead of "Argument list too long..."

-Eric

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

Re: xfs_growfs: XFS_IOC_FSGROWFSDATA xfsctl failed: Argument list too long

[Stan Hoeppner]

James Braid put forth on 4/29/2010 7:41 PM:

>> OS/Kernel Info:
>> Debian Lenny
>> Linux bigmama 2.6.30-2-686-bigmem #1 SMP Sat Sep 26 02:30:18 UTC 2009
>> i686 GNU/Linux
> 
> Filesystems >16TB aren't supported on 32-bit machines - it looks like
> your growfs is going to exceed that limit. Time to upgrade! ;)

Benjamin Lau put forth on 4/29/2010 7:07 PM:

> flags		: fpu vme de pse tsc msr pae mce cx8 apic
> sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr
> sse sse2 ss ht tm pbe nx *lm*

You're in luck Ben.  That trailing "lm" flag stands for "long mode" which is
the x86-64 native 64 bit mode.  Your Xeon appears to be a 64 bit CPU.  It
looks like the Nacona core from around 2004.  It's a netburst model (yuck)
with Intel64 extensions.

This is good news.  Fixing this max 16TB problem should be as simple as
rolling a new kernel with a few different settings and installing it if
you're a roll your own kernel kinda guy.

Run make menuconfig and:
1.  Select the Opteron/.../K8 cpu type
2.  Set high memory support to off
3.  Uncheck PAE
4.  Save and exit
5.  You know the rest of the steps if you roll your own

That should be all that's required to solve your issue.  You can leave your
user space as 32 bit if/until you're ready to do a dist upgrade to a 64 bit
user space.

Or you could just aptitude install one of the 64 bit Lenny kernels from the
mirrors.  That would be quicker, though not necessarily better.  I can't
tell exactly from your post which camp you fall into, though it looks like
the roll your own camp.

Hope this helps.

-- 
Stan

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

Re: xfs_growfs: XFS_IOC_FSGROWFSDATA xfsctl failed: Argument list too long

[Benjamin Lau]

Definitely in the roll my own camp though I try to avoid it on my
machines at the office (but I have no problem with it for my own
systems at home... which is where this server lives).

I'll give this a try and see how it goes.

Thanks!

Ben

On Thu, Apr 29, 2010 at 8:26 PM, Stan Hoeppner <stan@hardwarefreak.com> wrote:
> James Braid put forth on 4/29/2010 7:41 PM:
>
>>> OS/Kernel Info:
>>> Debian Lenny
>>> Linux bigmama 2.6.30-2-686-bigmem #1 SMP Sat Sep 26 02:30:18 UTC 2009
>>> i686 GNU/Linux
>>
>> Filesystems >16TB aren't supported on 32-bit machines - it looks like
>> your growfs is going to exceed that limit. Time to upgrade! ;)
>
> Benjamin Lau put forth on 4/29/2010 7:07 PM:
>
>> flags         : fpu vme de pse tsc msr pae mce cx8 apic
>> sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr
>> sse sse2 ss ht tm pbe nx *lm*
>
> You're in luck Ben.  That trailing "lm" flag stands for "long mode" which is
> the x86-64 native 64 bit mode.  Your Xeon appears to be a 64 bit CPU.  It
> looks like the Nacona core from around 2004.  It's a netburst model (yuck)
> with Intel64 extensions.
>
> This is good news.  Fixing this max 16TB problem should be as simple as
> rolling a new kernel with a few different settings and installing it if
> you're a roll your own kernel kinda guy.
>
> Run make menuconfig and:
> 1.  Select the Opteron/.../K8 cpu type
> 2.  Set high memory support to off
> 3.  Uncheck PAE
> 4.  Save and exit
> 5.  You know the rest of the steps if you roll your own
>
> That should be all that's required to solve your issue.  You can leave your
> user space as 32 bit if/until you're ready to do a dist upgrade to a 64 bit
> user space.
>
> Or you could just aptitude install one of the 64 bit Lenny kernels from the
> mirrors.  That would be quicker, though not necessarily better.  I can't
> tell exactly from your post which camp you fall into, though it looks like
> the roll your own camp.
>
> Hope this helps.
>
> --
> Stan
>
> _______________________________________________
> xfs mailing list
> xfs@oss.sgi.com
> http://oss.sgi.com/mailman/listinfo/xfs
>

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs