From: PVotruba@Chemoprojekt.cz
To: joelbeach@optushome.com.au
Cc: linux-kernel@vger.kernel.org
Subject: RE: Maximum (efficient) partition sizes for various filesystem ty pes...
Date: Mon, 19 Nov 2001 13:02:57 +0100 [thread overview]
Message-ID: <35E64A70B5ACD511BCB0000000004CA1095D08@NT_CHEMO> (raw)
Hmm it looks like that Debians want's to avoid user impatience during
excessive e2fsck job at startup. But technically, one can hardly expect
problems - if there were any, they surely appeared already in this list :)
Compared to *some* other OSes, linux makes fs checking after certain number
of rw mounts. When thinks like that happen, some less enlightened users tend
to be "derailed", because they don't expect that. :)
Regards,
Petr
> -----Původní zpráva-----
> Od: Joel Beach [SMTP:joelbeach@optushome.com.au]
> Odesláno: 19. listopadu 2001 11:23
> Komu: linux-kernel@vger.kernel.org
> Předmět: Re: Maximum (efficient) partition sizes for various
> filesystem types...
>
> 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)
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
next reply other threads:[~2001-11-19 13:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-19 12:02 PVotruba [this message]
2001-11-22 20:32 ` Stephen C. Tweedie
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=35E64A70B5ACD511BCB0000000004CA1095D08@NT_CHEMO \
--to=pvotruba@chemoprojekt.cz \
--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®