From: Andreas Dilger <adilger@turbolabs.com>
To: Marcelo Borges Ribeiro <marcelo@datacom-telematica.com.br>
Cc: Tyler BIRD <birdty@uvsc.edu>, linux-kernel@vger.kernel.org
Subject: Re: Filesize limit on SMBFS
Date: Thu, 22 Nov 2001 12:57:59 -0700 [thread overview]
Message-ID: <20011122125759.K1308@lynx.no> (raw)
In-Reply-To: <sbfce764.052@MAIL-SMTP.uvsc.edu> <001501c1738b$2a4be5b0$1300a8c0@marcelo>
In-Reply-To: <001501c1738b$2a4be5b0$1300a8c0@marcelo>; from marcelo@datacom-telematica.com.br on Thu, Nov 22, 2001 at 05:23:13PM -0200
On Nov 22, 2001 17:23 -0200, Marcelo Borges Ribeiro wrote:
> This limit is a kernel´s limit not a file system´s limit. Even vfat has a
> limitation of 2GB under linux. I thought with kernel 2.4.x this will be
> over.
Totally incorrect. 2.4 allows files larger than 2GB, and with a patch,
you can do this on 2.2 as well. If you are having problems with a 2GB
limit, then either your shell, libc, or tools is causing the problem.
VFAT does have a 2GB limit, AFAIK, but I could be wrong.
> ----- Original Message -----
> From: "Tyler BIRD" <birdty@uvsc.edu>
> > Ext2 Filesystems I believe have the limit of 2 GB. Ext3 Extends that
> > Limit to something??
No, the ext2 and ext3 limits are exactly the same, about 4TB right
now, but they would be larger with a bit of bug fixing (up to 16TB).
Note that the kernel has a limit of 2TB for a single device.
> > is maximum file size on SMBFS really 2GB? I cannot create file
> > bigger than that.
As for SMBFS, I don't know, but it can obviously not be larger than the
limit on the server.
Cheers, Andreas
--
Andreas Dilger
http://sourceforge.net/projects/ext2resize/
http://www-mddsp.enel.ucalgary.ca/People/adilger/
next prev parent reply other threads:[~2001-11-22 19:59 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 [this message]
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
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=20011122125759.K1308@lynx.no \
--to=adilger@turbolabs.com \
--cc=birdty@uvsc.edu \
--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