From: Paul DuBois <dubois@primate.wisc.edu>
To: Jon Howell <jonh@cs.dartmouth.edu>, linuxppc-dev@lists.linuxppc.org
Subject: Re: installer default inode count
Date: Tue, 30 Nov 1999 20:21:47 -0600 [thread overview]
Message-ID: <19991130202147.20629@primate.wisc.edu> (raw)
In-Reply-To: <Pine.GSO.3.96.991130201013.24058E-100000@sitka.cs.dartmouth.edu>; from Jon Howell on Tue, Nov 30, 1999 at 08:15:28PM -0500
On Tue, Nov 30, 1999 at 08:15:28PM -0500, Jon Howell wrote:
> I recently installed LinuxPPC 1999 Q3, and today I ran out of inodes.
> My 3G disk is only 67% full. It turns out my inode ratio is about
> one inode per 32KB. The default for mk2efs is 4KB (-i 4096).
> 32KB seems extreme. Indeed, I see from the mailing list archive
> that someone else ran into the same problem in September
> (http://lists.linuxppc.org/listarcs/linuxppc-dev/199911/msg00047.html).
This happened to me a couple of weeks ago, and the problem went away
when I reduced the size of the affected partition to be less than 2GB.
I assumed that perhaps some integer overflow problem occurred in
the math that computes the number of inodes, because that number
was ridiculously low.
> Hollis' reply hints that the installer does this on purpose, but
> I couldn't tell for sure. Could whoever maintains the installer look
> into changing the inode ratio to something lower, or is the 32KB ratio
> intentional (but unfortunate)?
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~1999-12-01 2:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-12-01 1:15 installer default inode count Jon Howell
1999-12-01 1:46 ` Hollis R Blanchard
1999-12-01 2:21 ` Paul DuBois [this message]
1999-12-01 2:36 ` Jon Howell
1999-12-01 2:40 ` Hollis R Blanchard
1999-12-01 4:09 ` Renaud Dreyer
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=19991130202147.20629@primate.wisc.edu \
--to=dubois@primate.wisc.edu \
--cc=jonh@cs.dartmouth.edu \
--cc=linuxppc-dev@lists.linuxppc.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).