From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: with ECARTIS (v1.0.0; list xfs); Sat, 19 Jan 2008 12:41:30 -0800 (PST) Received: from cuda.sgi.com (cuda2.sgi.com [192.48.168.29]) by oss.sgi.com (8.12.11.20060308/8.12.11/SuSE Linux 0.7) with ESMTP id m0JKfPsD016139 for ; Sat, 19 Jan 2008 12:41:26 -0800 Received: from sandeen.net (localhost [127.0.0.1]) by cuda.sgi.com (Spam Firewall) with ESMTP id 8044453B039 for ; Sat, 19 Jan 2008 12:41:44 -0800 (PST) Received: from sandeen.net (sandeen.net [209.173.210.139]) by cuda.sgi.com with ESMTP id a5aPBIushxcBwQzf for ; Sat, 19 Jan 2008 12:41:44 -0800 (PST) Message-ID: <47926087.3020600@sandeen.net> Date: Sat, 19 Jan 2008 14:41:43 -0600 From: Eric Sandeen MIME-Version: 1.0 Subject: Re: Volume too big References: <4792223E.7080805@sandeen.net> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: xfs-bounce@oss.sgi.com Errors-to: xfs-bounce@oss.sgi.com List-Id: xfs To: Jan Engelhardt Cc: xfs@oss.sgi.com 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 :) -Eric