From: DervishD <lkml@dervishd.net>
To: Sergio Monteiro Basto <sergio@sergiomb.no-ip.org>
Cc: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>,
The Peach <smartart@tiscali.it>,
linux-kernel@vger.kernel.org
Subject: Re: [OT] Re: bug? VFAT copy problem
Date: Thu, 23 Nov 2006 10:13:01 +0100 [thread overview]
Message-ID: <20061123091301.GC21908@DervishD> (raw)
In-Reply-To: <1164243385.3525.19.camel@monteirov>
Hi Sérgio :)
* Sergio Monteiro Basto <sergio@sergiomb.no-ip.org> dixit:
> On Wed, 2006-11-22 at 15:53 +0100, DervishD wrote:
> > * Sergio Monteiro Basto <sergio@sergiomb.no-ip.org> dixit:
> > > Have vfat a limit of a file size when copy ?
> >
> > 2GB, if I recall correctly. FAT32 itself has a limit of 4GB-1 for
> > file size, but Linux restricts it even more (don't ask me why).
>
> May I say that FAT32 have a bigger limit (at least on last Windows).
I really don't know, but from microsoft technical information
(the first or second hit when googling for "FAT32 size limit"), the
limit they specify in FAT32 is 2^32-1.
I may be wrong, but with 32 bits you cannot address more than
2^32 bytes, I don't know how can you create a bigger-than-4Gb file in
a FAT32 filesystem without resorting to tricks like this:
forum.doom9.org/archive/index.php/t-20689.html
Looks like FAT-32 (don't ask me how because I don't know the
internals) can store a file bigger than 4GB, but you cannot *save*
it. So you won't be able to put the file you have back to any FAT32
filesystem, I'm afraid.
> Have you a solution for the case ? Now I have the file in ext3 and
> I couldn't copy to any vfat :)
No, I don't have any idea about how to do it, sorry :(
> I have a solution with cifs or smbmount, but in same computer ?
I doubt. That limit is a hard limit as far as I know. Google for
"FAT32 limit" and you'll get a lot of answers telling it. I don't
really know how did you get a bigger than 4GB file saved in a FAT32
filesystem in the first place ;))
Raúl Núñez de Arenas Coronado
--
Linux Registered User 88736 | http://www.dervishd.net
It's my PC and I'll cry if I want to... RAmen!
next prev parent reply other threads:[~2006-11-23 9:12 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-20 15:42 bug? VFAT copy problem The Peach
2006-11-20 17:32 ` OGAWA Hirofumi
2006-11-20 17:49 ` The Peach
2006-11-21 15:46 ` OGAWA Hirofumi
2006-11-22 14:02 ` [OT] " Sergio Monteiro Basto
2006-11-22 14:53 ` DervishD
2006-11-22 16:07 ` OGAWA Hirofumi
2006-11-22 18:21 ` DervishD
2006-11-23 0:56 ` Sergio Monteiro Basto
2006-11-23 9:13 ` DervishD [this message]
2006-11-23 11:26 ` The Peach
2006-11-23 15:43 ` DervishD
2006-11-23 11:38 ` OGAWA Hirofumi
2006-11-23 11:50 ` [OT] " Renato S. Yamane
2006-11-23 11:59 ` OGAWA Hirofumi
2006-11-23 19:21 ` Sergio Monteiro Basto
2006-11-22 15:30 ` The Peach
2006-11-22 16:15 ` OGAWA Hirofumi
2006-11-22 19:10 ` The Peach
2006-11-22 19:29 ` OGAWA Hirofumi
2006-11-22 19:38 ` The Peach
2006-11-22 19:51 ` OGAWA Hirofumi
2006-11-22 22:21 ` The Peach
2006-11-23 11:32 ` OGAWA Hirofumi
2006-11-23 3:50 ` junjiec
2006-11-23 11:08 ` OGAWA Hirofumi
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=20061123091301.GC21908@DervishD \
--to=lkml@dervishd.net \
--cc=hirofumi@mail.parknet.co.jp \
--cc=linux-kernel@vger.kernel.org \
--cc=sergio@sergiomb.no-ip.org \
--cc=smartart@tiscali.it \
/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