All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@sandeen.net>
To: Jan Engelhardt <jengelh@computergmbh.de>
Cc: xfs@oss.sgi.com
Subject: Re: Volume too big
Date: Sun, 20 Jan 2008 16:03:57 -0600	[thread overview]
Message-ID: <4793C54D.7060003@sandeen.net> (raw)
In-Reply-To: <47926087.3020600@sandeen.net>

Eric Sandeen wrote:
> Jan Engelhardt wrote:
>> On Jan 19 2008 10:15, Eric Sandeen wrote:
>>>> 16:51 localhost:~ # strace -e mount mount /dev/md0 /mnt
>>>> mount("/dev/md0", "/mnt", "xfs", MS_MGC_VAL, NULL) = -1 E2BIG (Argument 
>>>> list too long)
>>>> mount: Argument list too long
>>>>
>>>> 16:51 localhost:~ # uname -a
>>>> Linux localhost 2.6.23.14-ccj63-regular #1 SMP 2007/10/26 14:17:15 UTC 
>>>> i686 athlon i386 GNU/Linux
>>>>
>>>> CONFIG_LBD=y. Do I need an extra flag for mkfs?
>>> Nope; this is probably that you can't do > 16T on a 32 bit box (core
>>> linux restriction, pretty much)
>>> get an x86_64, I think :)
>> Hm, JFS fails too.
>> But btrfs 0.11 can mount it.
> 
> It's possible that btrfs can cope with this somehow - but also quite
> possible that it's just missing the right checks :)

re: btrfs...

[15:50]  <mason> sandeen_: mkfs will work on >16TB, but the limiting
factor is the 32 bit radix tree ops on the page cache
[15:50]  <mason> so yes, it is missing a check ;)

:)

-Eric

      parent reply	other threads:[~2008-01-20 22:04 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-19 15:53 Volume too big Jan Engelhardt
2008-01-19 16:15 ` Eric Sandeen
2008-01-19 17:29   ` Justin Piszcz
2008-01-19 18:04     ` Jan Engelhardt
2008-01-19 17:53   ` Jan Engelhardt
2008-01-19 20:12     ` Eric Sandeen
2008-01-19 20:41     ` Eric Sandeen
2008-01-19 21:01       ` Jan Engelhardt
2008-01-19 21:26         ` Eric Sandeen
2008-01-20 22:03       ` 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=4793C54D.7060003@sandeen.net \
    --to=sandeen@sandeen.net \
    --cc=jengelh@computergmbh.de \
    --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.