Date: Wed, 13 Jun 2001 13:49:20 -0700 (PDT) From: Matt Dillon <dillon@earth.backplane.com> To: Dave Uhring <duhring@charter.net> Cc: Jaye Mathisen <mrcpu@internetcds.com>, stable@FreeBSD.ORG Subject: Re: Can't newfs big filesystem (twe/4.3-stable) Message-ID: <200106132049.f5DKnKZ10363@earth.backplane.com> References: <20010613104512.M51977@apocalypse.cdsnet.net> <01061315423100.00790@dave.uhring.com>
next in thread | previous in thread | raw e-mail | index | archive | help
:> newsfeed-inn# newfs -i 67108864 /dev/twed0d
:> [stuff deleted]
:> 1048576032, 1048641568, 1048707104, 1048772640, 1048838176, 1048903712,
:> 1048969248, 1049034784, 1049100320, 1049165856, 1049231392, 1049296928,
:> 1049362464, 1049428000, 1049493536, 1049559072, 1049624608, 1049690144,
:> 1049755680, 1049821216, 1049886752, 1049952288, 1050017824, 1050083360,
:> 1050148896, 1050214432, 1050279968, 1050345504, 1050411040, 1050476576,
:> 1050542112, 1050607648, 1050673184, 1050738720, 1050804256, 1050869792,
:> 1050935328
:> fsinit: inode value out of range (2).
:>
:> Tried larger -i parameters, same thing.
:>
:> Can't newfs figure this out before it gets to this point that something
:> isn't going to work?
:>
:> I'll try some different block/frag sizes, see if it helps.
Specifying a byte-to-inode ratio that large is kind of silly. I
usually use something like -i 262144 -b 16384 -f 2048 on my larger
filesystems. A couple of million would also probably work, but beyond
that you aren't really saving anything, not even fsck time. I'm not
surprised that 67 million doesn't work.
-Matt
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200106132049.f5DKnKZ10363>