From: Dan Merillat <harik@chaos.ao.net>
To: linux-kernel@vger.kernel.org
Cc: joelbeach@optushome.com.au
Subject: Re: Maximum (efficient) partition sizes for various filesystem types...
Date: Tue, 20 Nov 2001 14:24:46 -0500 [thread overview]
Message-ID: <200111201924.fAKJOkYR000837@vulpine.ao.net> (raw)
Joel Beach writes:
> 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."
They're right... for home users, with unreliable power or lots of reboots.
when you have to fsck an 18 gig /home partition you really feel it.
One of the reasons all my large drives are running reiserfs now.
And I don't even like to think about how long it takes to check my 56 gig
RAID5 on one server. Hell, it takes a long time just to mount it read/write
when it's clean! Thank god for 2-year uptimes.
So yes, the guide is accurate. And hopefully there will be a reiserfs/ext3
version of the debian install set out in the near future (There's one listed
as "try at your own risk", havn't done it yet.)
(as an aside, woody install is broken: pppoe requires libpcap, which dosn't get
installed initially, so the post-setup fails. It can be worked around, but
not by newbies. Lots of vi required)
--Dan
next reply other threads:[~2001-11-20 19:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-20 19:24 Dan Merillat [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-11-19 8:26 Joel Beach
2001-11-19 9:58 ` Alan Cox
2001-11-19 10:22 ` Joel Beach
2001-11-19 23:56 ` Mike Fedyk
2001-11-22 20:30 ` Stephen C. Tweedie
2001-11-23 9:09 ` Hans Reiser
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=200111201924.fAKJOkYR000837@vulpine.ao.net \
--to=harik@chaos.ao.net \
--cc=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
all inboxes | Powered by JetHome®