mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mike Eldridge <diz@cafes.net>
To: Andreas Dilger <adilger@turbolabs.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Filesize limit on SMBFS
Date: Fri, 23 Nov 2001 17:45:04 -0600	[thread overview]
Message-ID: <20011123174504.S21290@mail.cafes.net> (raw)
In-Reply-To: <Pine.LNX.4.42.0111231034330.15987-100000@boston.corp.fedex.com> <002801c1740f$7372f650$1300a8c0@marcelo> <20011123171157.Q21290@mail.cafes.net> <20011123161947.E1308@lynx.no>
In-Reply-To: <20011123161947.E1308@lynx.no>

On Fri, Nov 23, 2001 at 04:19:47PM -0700, Andreas Dilger wrote:
> On Nov 23, 2001  17:11 -0600, Mike Eldridge wrote:
> > ext2 has a 2GB filesize limitation.
> 
> Where do you get that idea from.  I have created files up to 4TB (sparse
> ones, of course) without problems.  After that you start hitting bugs in
> the VFS and ext2 _code_, but you should be able to have up to 16TB files
> on a 4kB block ext2 fs.
> 
> Please stop spreading misinformation.  Maybe there is a 2GB limitation
> in libc, or your tools, or in 2.2 ext2 _implementation_ (which is
> fixed if you apply the LFS patch for ext2), but no such limit in the
> design of ext2 itself.

oooh.  i apologize.  i remember reading in several different places that
little tidbit i rattled off.

i stand (majorly) corrected.

-mike

--------------------------------------------------------------------------
   /~\  The ASCII                       all that is gold does not glitter
   \ /  Ribbon Campaign                 not all those who wander are lost
    X   Against HTML                          -- jrr tolkien
   / \  Email!

          radiusd+mysql: http://www.cafes.net/~diz/kiss-radiusd           
--------------------------------------------------------------------------

  reply	other threads:[~2001-11-23 23:45 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-22 18:53 Tyler BIRD
2001-11-22 19:23 ` Marcelo Borges Ribeiro
2001-11-22 19:57   ` Andreas Dilger
2001-11-23  2:35     ` Jeff Chua
2001-11-23 11:10       ` Marcelo Borges Ribeiro
2001-11-23 12:00         ` Jeff Chua
2001-11-23 23:11         ` Mike Eldridge
2001-11-23 23:19           ` war
2001-11-23 23:19           ` Andreas Dilger
2001-11-23 23:45             ` Mike Eldridge [this message]
2001-11-24  1:16           ` Matti Aarnio
2001-11-24 20:43             ` Eric W. Biederman
2001-11-26 18:27           ` Alan Cox
2001-11-23  2:49     ` Anton Altaparmakov
2001-11-23  3:27       ` Jeff Chua
2001-11-23  7:09         ` OGAWA Hirofumi
2001-11-24  9:08   ` Albert D. Cahalan
  -- strict thread matches above, loose matches on Subject: below --
2001-11-22  9:10 Petr Tite(ra
2001-11-22 12:10 ` Urban Widmark
2001-11-22 13:01   ` Petr Titera
2001-11-22 20:58     ` Urban Widmark
2001-11-22 13:21   ` Anton Altaparmakov

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=20011123174504.S21290@mail.cafes.net \
    --to=diz@cafes.net \
    --cc=adilger@turbolabs.com \
    --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®