Live data from Hacker News

The thinking behind the 32GB Windows Format limit on FAT32

theregister.com

11–20 of 75 posts

Re: The thinking behind the 32GB Windows Format limit on FAT32

#11
If my memory serves well, when 40+ GB HDDs started being common, you were either using Windows 2000 and NTFS already, or it was probably a good practice to have several partitions, given the overall unreliability of Windows 9x and the not so infrequent clean reinstallations. And then came Windows XP and the issue was moot.

It's a bit of a shame Microsoft didn't push and open up exFAT earlier and allowed FAT32 to become an issue again, only with removable flash drives and memory cards this time.

Re: The thinking behind the 32GB Windows Format limit on FAT32

#12
post #8
post #3

TIL: In 2019, Microsoft released the exFAT [1] specs to a large group of vendors [2], including prominent Linux vendors. I.e. exFAT should now be preferred over FAT/NTFS for media used across different operating systems. [1] https://en.wikipedia.org/wiki/ExFAT [2] https://en.wikipedia.org/wiki/Open_Invention_Network

Unfortunately, this only applies to systems that actually have this (i.e. they were updated after exFAT released or released after and included this update). There will be sadly many systems that will never receive this update. But for a fun fact, if you see many embedded systems that say they can only support an SD card up to 32 GB, it is a soft limitation due to the fact that media over 32 GB are pre-formatted to e…

> But for a fun fact, if you see many embedded systems that say they can only support an SD card up to 32 GB, it is a soft limitation due to the fact that media over 32 GB are pre-formatted to exFAT (and the system lacks support for exFAT).

There might also be the issue of the card reading hardware only supprting SDHC instead of SDXC (or SDUC).

Re: The thinking behind the 32GB Windows Format limit on FAT32

#13
post #7

The choice he made was probably a reasonable balance -- the alternative was reinventing the filesystem, which was probably a bit out of spec for implementing the GUI format dialog. And eventually happened, but it took a while.

Its not reinventing. Its just setting a limit on max cluster slack. Like he says in the video, you can totally use the CLI and format any disk size you want, its just a soft block

Re: The thinking behind the 32GB Windows Format limit on FAT32

#14

Earlier quoted context omitted.

Exactly. Just another case of "640K should be enough for anybody". But we have to admit that storage has leapt hugely in size and very rapidly . In 1990 or thereabouts, a common hard disk size was about 30 megabytes. Today I have files that are many times that size, and we think that that is quite normal. A mere five or so years later around 1996, that size had jumped to 4000 megabytes! These days my laptop has 6 mil…

I have a single file that is 6 million megabytes in size.

who/what reads that file?

Re: The thinking behind the 32GB Windows Format limit on FAT32

#16
post #6
post #3

TIL: In 2019, Microsoft released the exFAT [1] specs to a large group of vendors [2], including prominent Linux vendors. I.e. exFAT should now be preferred over FAT/NTFS for media used across different operating systems. [1] https://en.wikipedia.org/wiki/ExFAT [2] https://en.wikipedia.org/wiki/Open_Invention_Network

>TIL: In 2019, Microsoft released the exFAT [1] specs [...] I.e. exFAT should now be preferred over FAT/NTFS for media used across different operating systems. You seem to be very optimistic about how fast these get implemented into embedded devices.

I would imagine if embedded devices are being assembled and configured with filesize concerns, then exFAT would be the natural implementation they would opt for. Or do you mean updating/transitioning legacy embedded?

The spec doesn't mention backwards compat, but does mention as a goal

>Retain the simplicity of FAT-based file systems.

I would like to test out if an input embed system is exFAT compat. And what might be required to update.

Re: The thinking behind the 32GB Windows Format limit on FAT32

#18
post #12
post #8

Earlier quoted context omitted.

Unfortunately, this only applies to systems that actually have this (i.e. they were updated after exFAT released or released after and included this update). There will be sadly many systems that will never receive this update. But for a fun fact, if you see many embedded systems that say they can only support an SD card up to 32 GB, it is a soft limitation due to the fact that media over 32 GB are pre-formatted to e…

> But for a fun fact, if you see many embedded systems that say they can only support an SD card up to 32 GB, it is a soft limitation due to the fact that media over 32 GB are pre-formatted to exFAT (and the system lacks support for exFAT). There might also be the issue of the card reading hardware only supprting SDHC instead of SDXC (or SDUC).

That is true, though I have yet to run into that issue though for the devices I have tried it on (which admittedly is not a large sample size).

Re: The thinking behind the 32GB Windows Format limit on FAT32

#19
post #6
post #3

TIL: In 2019, Microsoft released the exFAT [1] specs to a large group of vendors [2], including prominent Linux vendors. I.e. exFAT should now be preferred over FAT/NTFS for media used across different operating systems. [1] https://en.wikipedia.org/wiki/ExFAT [2] https://en.wikipedia.org/wiki/Open_Invention_Network

>TIL: In 2019, Microsoft released the exFAT [1] specs [...] I.e. exFAT should now be preferred over FAT/NTFS for media used across different operating systems. You seem to be very optimistic about how fast these get implemented into embedded devices.

Maybe there are even capable embedded implementations even before Microsoft implements all supported features like ACLs in their OS.

Re: The thinking behind the 32GB Windows Format limit on FAT32

#20

If my memory serves well, when 40+ GB HDDs started being common, you were either using Windows 2000 and NTFS already, or it was probably a good practice to have several partitions, given the overall unreliability of Windows 9x and the not so infrequent clean reinstallations. And then came Windows XP and the issue was moot. It's a bit of a shame Microsoft didn't push and open up exFAT earlier and allowed FAT32 to beco…

The problem with removable drives is that no one came up with a better filesystem than FAT32 that could be implemented easily by everyone. All the *NIX filesystems embedded permissions that were useless on non-POSIX systems and caused issues on POSIX ones when you actually moved a drive from one computer to another. So MS extended FAT again and kept it under its IP hat, as was their wont[0] at the time.

[0] Non-native english speakers may be confused by this: https://www.merriam-webster.com/dictionary/as%20is%20someone...

Post reply on HN