Slashdot Mirror


USB Flash Drive Comparison Part 2 — FAT32 Vs. NTFS

Dampeal writes "Ok, a little while back I ran a somewhat large USB Flash Drive Comparison with 21 drives compared, today I got part two of that comparison. I've taken the 8gig and 4 gig drives, nine in total, and formatted them FAT32, NTFS and ExFAT and ran all of the tests over again for a comparison of how the file systems work on the drives." Good news — after some exhaustively graphed testing scenarios, the author comes to a nice conclusion for lazy people, writing "[I]n my opinion the all around best choice is FAT32, or the default for most all USB drives out there today, it seems to give us the best average performance overall."

40 of 198 comments (clear)

  1. Great by Chih · · Score: 4, Informative

    I'm lazy, so it's good to know that the default setting is the best.

    --
    For best results, avoid doing stupid things.
    1. Re:Great by Anonymous Coward · · Score: 2, Funny

      I'm too lazy to even care.

    2. Re:Great by Z00L00K · · Score: 4, Insightful

      What about ext2 and other filesystems then?

      --
      If builders built buildings the way programmers wrote programs, then the first woodpecker would destroy civilization.
    3. Re:Great by Anonymous Coward · · Score: 2, Funny

      I'm too lazy to even care.

      Morla, is that you?

    4. Re:Great by mollymoo · · Score: 3, Informative

      Define "best". The manufacturers will have selected FAT32 based on compatibility. The test shows that it's a good choice for performance too.

      --
      Chernobyl 'not a wildlife haven' - BBC News
    5. Re:Great by geminidomino · · Score: 3, Funny

      Wow... Neverending Story reference on Slashdot?

      Way to make me feel old, asshole. ;)

    6. Re:Great by afidel · · Score: 2, Interesting

      If you don't need to write to the drive from XP then UDF is a possibility, it's about 3x faster than even FAT16 under Vista for small files and is supported by almost all current OS's (OSX 10.5, Linux 2.6.10+, Vista/Win7, AIX, etc) so eventually it shouldn't be a problem unless you need to use it with an embedded type device. If MS asks too much for exFAT I can see embedded players supporting UDF for large filesystems.

      --
      There are 4 boxes to use in the defense of liberty: soap, ballot, jury, ammo. Use in that order. Starting now.
    7. Re:Great by Hucko · · Score: 2, Funny

      Thus Microsoft has the perfect way to EOF XP... Support UDF, Microsoft! It will force people to upgrade! s/force/encourage

      --
      Semi-automatic amateur armchair Australian philosopher; conjecture ready at any moment...
  2. No JFFS2? by garbletext · · Score: 3, Insightful

    Since interoperability is key in this context, anything besides FAT32 is hopelessly esoteric. So why not test the OSS solution as well?

  3. Same applies to SSDs? by gEvil+(beta) · · Score: 4, Interesting

    The question about filesystems has come up a few times over on the Dell Mini forums. Basically the question is which is better to use on machines with SSDs? If you're not dealing with >4GB files, several people have suggested that you're better off formatting the drive as FAT32. I'll need to take a better look at this article when I get a chance, but it seems to be suggesting the same thing.

    --
    This guy's the limit!
  4. not so fast by uberjoe · · Score: 5, Informative

    FAT32 is great, unless you want to exceed the 4gb filesize limit. In which case you will need an alternative.

    --

    The days of the digital watch are numbered.

    1. Re:not so fast by mweather · · Score: 2, Informative

      The only benefit of FAT32 is compatibility. exFAT does not have that.

    2. Re:not so fast by TemporalBeing · · Score: 3, Informative

      exFAT has as much in common with FAT32 as does NTFS. Microsoft made a big change with a purposeful break from backwards compatibility. So while it may be a 64-bit compatible FAT implementation, it doesn't share anything with the older FAT file systems - even FAT32. So no, no more compatibility whatsoever than NTFS.

      --
      Truth is like the sun. You can shut it out for a time, but it ain't goin' away. - Elvis Presley (source: imdb.com)
  5. NTFS patten? by jgtg32a · · Score: 2, Interesting

    I thought NTFS had a patten on it which is why they used FAT32 instead.

    1. Re:NTFS patten? by gEvil+(beta) · · Score: 5, Funny

      No, I think he meant "Patton". Having Patton on me is the last thing I'd want.

      --
      This guy's the limit!
    2. Re:NTFS patten? by Joe+Snipe · · Score: 4, Funny

      He did, unfortunately there is a patten on that word.

      --
      Sometimes, life itself is sarcasm...
    3. Re:NTFS patten? by QuasiEvil · · Score: 4, Funny

      You clearly mean treadmark. Which may have been left by a Patton, if he ran over your flash drive with his Jeep.

  6. Question by oldspewey · · Score: 3, Funny

    If I format one of these with ReiserFS, am I still okay to take it through airport security?

    --
    If libertarians are so opposed to effective government, why don't they all move to Somalia?
    1. Re:Question by the_humeister · · Score: 3, Funny

      Better question: Will the USB drive die faster with ReiserFS?

    2. Re:Question by Fred_A · · Score: 3, Funny

      You might have trouble finding your files on ReiserFS.

      Nah, you just have to dig around a bit in the directories. They're rarely very far from where you last saw them.

      --

      May contain traces of nut.
      Made from the freshest electrons.
    3. Re:Question by morgan_greywolf · · Score: 2, Funny

      Another Linux-related question: If I format the USB drive with ReiserFS, am I restricted to using it only in a chroot jail?

  7. incomplete tests by PatentMagus · · Score: 3, Interesting

    I wish there were tests covering "typical user mishaps". Things like inopportune powerdowns and flash drive yanking. My anecdotal evidence is that I've never had issues with FAT32 but have had entire NTFS partitions become unreadable. It's just anecdote though. Now throw a truecrypt file into the mix ...

    --
    I am a lawyer, but not yours. Anything I tell you might be a total lie intended to benefit my clients at your expense.
  8. Read vs Write by Hyppy · · Score: 2, Interesting

    It seems like the write time is the most variable out of all these. FAT32/NTFS/ExFAT scores for reading are all within a few % of each other.

    I wonder what makes NTFS so slow for writes? The journaling alone reduces it that far?

    1. Re:Read vs Write by Hal_Porter · · Score: 3, Interesting

      I'd guess it's because NTFS sucks on a removable device. On Windows, by default, hot pluggable devices are mounted with write through caching. NTFS supports this but not very efficiently.

      FAT32 and exFAT are simple enough that you can do safe access to a disk even without much write caching. FAT (and probably exFAT) actually defines a way to mark the volume as dirty in the first FAT entry at the start of each transaction where the FAT will be modified.

      If someone pulls the drive right in the middle of writing some clusters may be marked as used in the FAT but not actually in use by any files. Next time you insert the drive Vista checks the volume dirt flag and asks you for if you want to run chkdsk. If you run it it will find the 'lost clusters' and convert them to files in the root directory.

      Of course this scheme only ensures filesystem metadata consistency, recover user data that was being written when the drive was yanked. Mind you, NTFS journalling has the same limitation. Of course scanning for lost clusters on FAT is a painfuly slow process - you read the FAT into memory and make a bitmap of allocated clusters. Then you read every single directory and tick off the clusters used by each file. Any that are left over are lost. A journaled filesystem is much simpler - you just rollback any incomplete transations in the journal.

      Of course if you have to block waiting for write transactions to complete creating the journal entries, updating bitmaps, indexes and inodes and writing data, which you would have to do on a removable device with write through caching, a journaled filesystem like NTFS has a hefty overhead. NTFS structures are much more complex so plausibly extra disk writes are necessary to keep them updated and on small writes those extra writes dominate disk time. Write through caching makes this situation even worse.

      --
      echo -e 'global _start\n _start:\n mov eax, 2\n int 80h\n jmp _start' > a.asm; nasm a.asm -f elf; ld a.o -o a;
  9. Don't install your OS on FAT32... by js_sebastian · · Score: 5, Informative

    The question about filesystems has come up a few times over on the Dell Mini forums. Basically the question is which is better to use on machines with SSDs? If you're not dealing with >4GB files, several people have suggested that you're better off formatting the drive as FAT32. I'll need to take a better look at this article when I get a chance, but it seems to be suggesting the same thing.

    FAT32 is fine for a USB stick, but you shouldn't install an OS on it. The problem is that FAT32 has no concept of file ownership. So your operating system will be unable to restrict access to files based on the user, which is one of the building blocks of security on any modern OS. This way, any (malicious) process running on the system can overwrite critical system files to do arbitrary damage.

    Even if you run windows XP as adminstrator, not all processes on your system run as administrator so you will still be (slightly) decreasing security by having it on a FAT32 filesystem.

    1. Re:Don't install your OS on FAT32... by Anonymous Coward · · Score: 2, Insightful

      Permissions on XP are screwed and hurt more than they help. Being unable to delete/move some files even as Administrator in single user mode is bullshit.

    2. Re:Don't install your OS on FAT32... by repvik · · Score: 3, Informative

      Google "unlocker". Very useful tool.

    3. Re:Don't install your OS on FAT32... by Pentium100 · · Score: 2, Informative

      This.

      While all my computers are part of a domain (so my user name works on all of them and has full rights), I sometimes have problems with hard drives that I connect from other (people brought me to reinstall Windows). Now, ideally I would connect the drive to my PC, if the drive has enough free space left (>3GB), I would just move all current directories to a new one, say c:\__old, then install Windows. The owner of that PC would save what files are important to him and delete the rest of __old. However, if the drive is NTFS, sometimes I have problems moving or deleting the Windows directory because I do not have enough permissions and taking ownership does not work. Then I can only copy all other files to some other HDD or tape, format the drive in question and copy the files back. And then I just think how glad I am that the system drive of my main PC is FAT32.

      Also, FAT32 has a second copy of the FAT on the drive, so if anything bad happens (say, a bad sector) to the first copy, you can restore it. If a bad sector appears in the $MFT of NTFS - you just lost a number of files. Anyone know of a software solution that can keep an updated copy of the MFT somewhere on the drive (or on some other drive)?

      On the other hand, NTFS supports 64KB cluster size, while FAT32 supports only 32KB. That and >4GB file support made me use NTFS on some hard drives, because HD movies are usually >4GB in size...

  10. Important for me by david.given · · Score: 5, Interesting

    I'm currently on site at a customer's office. I have one of their PCs and one of ours; legal restrictions mean I can't copy our source onto their machines or their source onto ours.

    The solution to this is to put a copy of our source onto a USB stick and plug it into their machine, and then use a NTFS junction point (aka a symlink) to let their Windows-based build system see our source. This works very nicely, and I can just unplug the USB stick whenever I leave and the lawyers are happy.

    However:

    - I have to use NTFS. This is because the two machines are set to use different time zones, and frickin' FAT stores timestamps in the local time, which means that if I were to touch a file on one machine and the move the USB stick, the build system will go horribly wrong.

    - I have 'optimise for performance' turned on; the non-Windows world calls this write caching. This boosts performance on NTFS *hugely*. I see no mention of this in the review. I now have to remember to unmount the stick on the Windows machine before pulling it, but it's worth it.

    - You have to use the command line format.exe to format a removable drive as NTFS, because frickin' Windows doesn't let you do it from the GUI.

    - If you turn NTFS compression on, you get a tiny bit more speed boost. But while Linux will read compressed NTFS files, it won't write them.

    - You need to do something obscure with NTFS file permissions if you're going to move the stick between two Windows machines, because otherwise you'll be creating files on one machine you won't be allowed to edit on the other. Linux, of course, just ignores NTFS ACLs.

    I have investigated the Windows ext2 driver, but while it does work reasonably well, it's still pretty clunky, and ext2 isn't much better than NTFS. What I'd really like is a decent Windows JFS or XFS driver --- NTFS is *so* last century.

  11. Re:Size matters by pla · · Score: 4, Informative

    Did he run tests with 16GB files?

    FTA: "I've taken the 8gig and 4 gig drives, nine in total"


    FTA: "I used a 350MB .AVI Video file for all testing.".


    More importantly, he couldn't use a 16GB file, since FAT32 doesn't support single files over 4GB.

  12. Installing the ext2 driver? by tepples · · Score: 4, Informative

    What about ext2 and other filesystems then?

    Ninety percent of desktop PCs run Windows, and for interchange among the public, file systems that most PCs running Windows cannot read aren't worth testing. If you format your USB drive as ext2 and carry it to someone else's PC, you'll need to 1. carry a CD or a second USB drive with the ext2 driver and 2. get admin rights in order to install it on someone else's PC. It'd be like the Windows 9x days, when you needed to carry a floppy disk with the USB mass storage class driver whenever you used someone else's computer.

    1. Re:Installing the ext2 driver? by RiotingPacifist · · Score: 2, Interesting

      I use USB-pens to securly transfere my data from A -> B, gpg keys, documents, etc. Just because you use your USB-pens to spread viruses between windows pcs doesn't mean everybody does! I'd be quite interested to see ext2 vs reiserfs vs jfs vs fat.

      --
      IranAir Flight 655 never forget!
  13. You can partition flash drives by Rix · · Score: 3, Interesting

    So you could just have a small partition holding the ext2 driver. Not really worth the effort for that, but it makes sense for things like truecrypt.

  14. You have to use the command line format.exe by Anonymous Coward · · Score: 4, Informative

    Select the usb drive right click/hardware/policies select optimize for performance and the GUI formatter will now have NTFS as an option.

    After formatting you can reset the policy as needed.

    I personally turn optimize for performance off on USB drives as many times explorer or some other program will lock the drive preventing a safe removal.

  15. Re:Size matters by coolsnowmen · · Score: 5, Funny

    Did he run tests with 16GB files?

    ...
    More importantly, he couldn't use a 16GB file, since
    FAT32 doesn't support single files over 4GB.

    And because 4GB drives don't support files over 4GB.

  16. Filesystem for Slashdotters by Bromskloss · · Score: 2, Interesting

    I don't care for compatibility with Windows. I use exclusively free *nixes and so does all my friends (otherwise they wouldn't be real friends, would they?). So having this richer buffet of file systems than just the two in the article, what should I choose? I have heard someone say that ext2 means less wear on the drive than ext3 (something with journaling?).

    --
    Swedish plasma phys. PhD student; MSc EE; knows maths, programming, electronics; finance interest; seeks opportunities
  17. FAT32 and MS Backup by Dreben · · Score: 2, Informative

    Since many folks use their usb devices as backup media, it should be noted since fat32 has a file size limitation of about 4gb, fat32 is not an option if you wish to use MS Backup utility to create backup images larger than that.

  18. The first two things I look for in a jump drive by Doghouse+Riley · · Score: 2, Interesting

    (1) Does it have a cap I am likely to lose?

    (2) Can I attach it to my keyring? (no silly lanyard clips please)

    Both far more important to me in daily use than a 20% speed difference between one drive and another.
    It's not like I'm running terabyte database sorts on these little guys.......

  19. Re:Size matters by TemporalBeing · · Score: 2, Interesting

    FAT32 doesn't support single files over 4GB.

    True, but it will happily install (at least using the Linux Kernel's driver for it) on any size drive. I did that a few years ago for a backup drive that had to be accessible from Linux as well as Windows. Windows would only allow the FS to format to 32GB; while the Linux driver let it take up the whole drive (120GB? can't quite remember). The real funny thing was that Windows was happy to work with the drive afterwards and didn't complain whatsoever about the larger than 32GB FAT32 FS on it - and I filled more than the 32GB.

    However, FAT32 does come at a high overhead price. I know I lost a few GB just to the formatting alone.

    P.S. I no longer have access to that drive, otherwise, I'd pull up the real size/usage for it.

    --
    Truth is like the sun. You can shut it out for a time, but it ain't goin' away. - Elvis Presley (source: imdb.com)
  20. Re:Choose NTFS for the life of your drive by _Splat · · Score: 3, Informative

    Flash drives have a flash translation layer that makes the flash look like a regular disk despite having special properties. This layer handles the wear-leveling, garbage collection, and bad block detection so the standard filesystem (that was designed for magnetic disks, probably) doesn't have to consider them. Regardless of the filesystem used, the wear of the device should be related to the total amount of data written, not the location of the data.

    --
    -Splat