All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@sandeen.net>
To: James Braid <jamesb@loreland.org>
Cc: Benjamin Lau <benjamin.a.lau@gmail.com>, xfs@oss.sgi.com
Subject: Re: xfs_growfs: XFS_IOC_FSGROWFSDATA xfsctl failed: Argument list too	long
Date: Thu, 29 Apr 2010 22:11:59 -0500	[thread overview]
Message-ID: <4BDA4A7F.7040404@sandeen.net> (raw)
In-Reply-To: <p2y25446eb91004291741k7e8e72cejc72093caf9cc99aa@mail.gmail.com>

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

  parent reply	other threads:[~2010-04-30  3:09 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-30  0:07 xfs_growfs: XFS_IOC_FSGROWFSDATA xfsctl failed: Argument list too long Benjamin Lau
2010-04-30  0:41 ` James Braid
2010-04-30  2:15   ` Benjamin Lau
2010-04-30  3:11   ` Eric Sandeen [this message]
2010-04-30  3:26   ` Stan Hoeppner
2010-04-30  4:34     ` Benjamin Lau

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=4BDA4A7F.7040404@sandeen.net \
    --to=sandeen@sandeen.net \
    --cc=benjamin.a.lau@gmail.com \
    --cc=jamesb@loreland.org \
    --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.