From: "Joel Beach" <joelbeach@optushome.com.au>
To: <linux-kernel@vger.kernel.org>
Subject: Re: Maximum (efficient) partition sizes for various filesystem types...
Date: Mon, 19 Nov 2001 21:22:38 +1100 [thread overview]
Message-ID: <001401c170e4$1d890d20$1e50a8c0@kinslayer> (raw)
In-Reply-To: <E165lCN-00061N-00@the-village.bc.nu>
I think I'll fix up that bit in the Debian manual myself then if they let
me....
For what it's worth, here's the paragraph from the "Woody" installation
manual:
"For new users, personal Debian boxes, home systems, and other single-user
setups, a single / partition (plus swap) is probably the easiest, simplest
way to go. It is possible to have problems with this idea, though, with
larger (20GB) disks. Based on limitations in how ext2 works, avoid any
single partition greater than 6GB or so."
Joel
----- Original Message -----
From: "Alan Cox" <alan@lxorguk.ukuu.org.uk>
To: "Joel Beach" <joelbeach@optushome.com.au>
Cc: <linux-kernel@vger.kernel.org>
Sent: Monday, November 19, 2001 8:58 PM
Subject: Re: Maximum (efficient) partition sizes for various filesystem
types...
> > For instance, the Debian guide says that, due to Ext2 efficiency,
partitions
> > greater than 6-7GB shouldn't be created. Is this true for Ext3/ReiserFS.
>
> I've run several 45-200Gb ext2 and ext3 partitions with no problem. I'm
not
> sure what the origin of the Debian guide comemnt is but I've never heard
> it from an ext2 developer
>
> Obviously pick a journalled fs for big partitions 8)
next prev parent reply other threads:[~2001-11-19 10:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-19 8:26 Maximum (efficient) partition sizes for various filesystem types Joel Beach
2001-11-19 9:58 ` Alan Cox
2001-11-19 10:22 ` Joel Beach [this message]
2001-11-19 23:56 ` Mike Fedyk
2001-11-22 20:30 ` Stephen C. Tweedie
2001-11-23 9:09 ` Hans Reiser
-- strict thread matches above, loose matches on Subject: below --
2001-11-20 19:24 Dan Merillat
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='001401c170e4$1d890d20$1e50a8c0@kinslayer' \
--to=joelbeach@optushome.com.au \
--cc=linux-kernel@vger.kernel.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