From: Andreas Schwab <schwab@suse.de>
To: mru@kth.se (Måns Rullgård)
Cc: linux-kernel@vger.kernel.org
Subject: Re: Large-FAT32-Filesystem Bug
Date: Sat, 06 Dec 2003 02:10:23 +0100 [thread overview]
Message-ID: <je8ylqda4g.fsf@sykes.suse.de> (raw)
In-Reply-To: <yw1x1xri3hbu.fsf@kth.se> ( =?iso-8859-1?q?M=E5ns_Rullg=E5rd's_message_of?= "Sat, 06 Dec 2003 01:44:53 +0100")
mru@kth.se (Måns Rullgård) writes:
> Andreas Schwab <schwab@suse.de> writes:
>
>>>>> No problem. I put this patch together quite a while ago for
>>>>> my own use and never got around to sending it in. It removes
>>>>> a number of artificial fat32 limits, and allows files up to 4GB,
>>>>
>>>> Why only 4gb?
>>>
>>> That's what the 32 in fat32 means.
>>
>> No, it doesn't. It's about the number of bits in a cluster number, thus
>> the size of the filesystem. And that 32 is actually 28.
>
> OK, my mistake, but there is a 32 as in file size, right?
Yes, the size has always been a 32 bit field, even with fat12.
Andreas.
--
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux AG, Maxfeldstraße 5, 90409 Nürnberg, Germany
Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2003-12-06 1:10 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-05 9:52 Large-FAT32-Filesystem Bug Torsten Scheck
2003-12-05 13:17 ` jdow
2003-12-07 12:26 ` Helge Hafting
2003-12-07 12:20 ` Tomasz Torcz
2003-12-08 9:54 ` Helge Hafting
2003-12-08 14:10 ` Gene Heskett
2003-12-08 16:19 ` Randy.Dunlap
2003-12-07 13:56 ` Gene Heskett
2003-12-05 15:26 ` Eduard Bloch
2003-12-05 16:07 ` Erik Andersen
2003-12-05 17:54 ` Torsten Scheck
2003-12-05 22:10 ` Erik Andersen
2003-12-05 22:45 ` Mike Fedyk
2003-12-05 23:26 ` Måns Rullgård
2003-12-06 0:04 ` Andreas Schwab
2003-12-06 0:44 ` Måns Rullgård
2003-12-06 1:10 ` Andreas Schwab [this message]
2004-02-06 14:43 ` Torsten Scheck
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=je8ylqda4g.fsf@sykes.suse.de \
--to=schwab@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mru@kth.se \
/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;
as well as URLs for NNTP newsgroup(s).