public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: war <war@starband.net>
To: Mike Eldridge <diz@cafes.net>
Cc: Marcelo Borges Ribeiro <marcelo@datacom-telematica.com.br>,
	linux-kernel@vger.kernel.org
Subject: Re: Filesize limit on SMBFS
Date: Fri, 23 Nov 2001 18:19:16 -0500	[thread overview]
Message-ID: <3BFED974.CAB4513C@starband.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>

To put it simply, ext2 does not have a 2GB filesize limitation anymore, (in newer
distributions).

Mike Eldridge wrote:

> On Fri, Nov 23, 2001 at 09:10:24AM -0200, Marcelo Borges Ribeiro wrote:
> > I have fat32 partition, but the problem isn´t the size of partition it is
> > 8GB. The problem is that if you want to
> > create a cpio backup of a linux system 3.5GB (I did that to reformat a ext2
> > to a reiserfs) to an available fat32 space, in my case the backup size is
> > allways 2GB and when I tried to extract back I saw "unexpected end of file".
> > So I thought it was that famous kernel limitation of 2GB under any kind of
> > partition, but i was informed that fat has this limitation too. So the
> > kernel may suport files bigger than 2GB (I really don´t know, I just know
> > that in my case with fat32 it did not and I saw this too with some oracle
> > databases that could not be used when they grow and reach 2GB, may be a
> > library problem too).
>
> ext2 has a 2GB filesize limitation.
>
> -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
> --------------------------------------------------------------------------
> -
> 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/


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

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-22 18:53 Filesize limit on SMBFS 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 [this message]
2001-11-23 23:19           ` Andreas Dilger
2001-11-23 23:45             ` Mike Eldridge
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=3BFED974.CAB4513C@starband.net \
    --to=war@starband.net \
    --cc=diz@cafes.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo@datacom-telematica.com.br \
    /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