[Top] [All Lists]

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

To: xfs@xxxxxxxxxxx
Subject: Re: xfs_growfs: XFS_IOC_FSGROWFSDATA xfsctl failed: Argument list too long
From: Benjamin Lau <benjamin.a.lau@xxxxxxxxx>
Date: Thu, 29 Apr 2010 21:34:30 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:content-type :content-transfer-encoding; bh=qtkGWA9gP/Aur4/9zAU3z/YBZ8BQTSUyvIO+z/+YSy4=; b=suajWchwpFMGHm9DM+4Z6bwWfJm6dt/QbpN+fcdvHv0l6B2nX3WIQVFi/1xdQ1zDU/ M0ut9fqoe1rXLHZJ1EU33EbB6lI5gkGijrpncsvEZMxyQiOL+0r+JEINQbae+F0Ds5o+ dL6OR+q38p6qHCqFyiI8ROHZhwxP/ioyGtYV4=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; b=ZmO6t6Kz4RW/TR6wzF+0RjsDLSUbltTYAR1wDgZoJcKxqpw7m9Fkx1UWviHvT6iEvu 1fu0qVSSac3Krs+8JhPZ8L9QSxdqO3yRzOtAKVDQtaXawIHnWP0LF2/t17abD2zHqttJ aL8jeosEMCuAMwLnnBuhY03ACqKTM76AX4mBg=
In-reply-to: <4BDA4DC8.6020408@xxxxxxxxxxxxxxxxx>
References: <i2hdb2d1ee61004291707k9ffebed2k4ff6eb72354cbe63@xxxxxxxxxxxxxx> <p2y25446eb91004291741k7e8e72cejc72093caf9cc99aa@xxxxxxxxxxxxxx> <4BDA4DC8.6020408@xxxxxxxxxxxxxxxxx>
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.



On Thu, Apr 29, 2010 at 8:26 PM, Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx> 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@xxxxxxxxxxx
> http://oss.sgi.com/mailman/listinfo/xfs

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