All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Stephen C. Tweedie" <sct@redhat.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Joel Beach <joelbeach@optushome.com.au>, linux-kernel@vger.kernel.org
Subject: Re: Maximum (efficient) partition sizes for various filesystem types...
Date: Thu, 22 Nov 2001 20:30:00 +0000	[thread overview]
Message-ID: <20011122203000.B11821@redhat.com> (raw)
In-Reply-To: <001401c170d3$ea40cc10$1e50a8c0@kinslayer> <E165lCN-00061N-00@the-village.bc.nu>
In-Reply-To: <E165lCN-00061N-00@the-village.bc.nu>; from alan@lxorguk.ukuu.org.uk on Mon, Nov 19, 2001 at 09:58:43AM +0000

Hi,

On Mon, Nov 19, 2001 at 09:58:43AM +0000, Alan Cox wrote:
> > 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

The largest filesystem I use with ext3 at the moment is 40GB, and it
is 98% full and is used *constantly* (it contains my main build
trees).  I'm not sure where the 6-7GB limit idea comes from but I've
got very few filesystems smaller than that, and they are still all
ext3.

Cheers,
 Stephen

  parent reply	other threads:[~2001-11-22 20:30 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
2001-11-19 23:56     ` Mike Fedyk
2001-11-22 20:30   ` Stephen C. Tweedie [this message]
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=20011122203000.B11821@redhat.com \
    --to=sct@redhat.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.