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."

198 comments

  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 longhairedgnome · · Score: 1, Funny

      Wow, who would have thought that the manufacturers would have chosen the best option?

      --
      GENERATION O98346: The first time you see this, copy it into your sig and remove a random number from the generation. T
    2. Re:Great by Anonymous Coward · · Score: 2, Funny

      I'm too lazy to even care.

    3. 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.
    4. Re:Great by Anonymous Coward · · Score: 2, Funny

      I'm too lazy to even care.

      Morla, is that you?

    5. Re:Great by Hal_Porter · · Score: 0, Offtopic

      That's not true generally though. For example if you buy a cheap laptop with the default choice of Windows Vista Home Basic you will die of aids AND cancer.

      That's why it's important to read the tech sites EVERY DAY.

      --
      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;
    6. 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
    7. Re:Great by Anonymous Coward · · Score: 0

      I'm too lazy to read your post...

    8. Re:Great by dimension6 · · Score: 1

      ...and I'm too lazy to write a reply to your post.

    9. Re:Great by geminidomino · · Score: 3, Funny

      Wow... Neverending Story reference on Slashdot?

      Way to make me feel old, asshole. ;)

    10. Re:Great by AmiMoJo · · Score: 1

      Unfortunately FAT32 is the only universally supported file system. You can be sure pretty much any machine you put your USB flash drive in will read and write it. Most embedded systems only support FAT/FAT32 as well (e.g. TVs, cameras, car head units etc.)

      The reason it's unfortunate is that FAT32 is not journalled, so not exactly ideal for a removal storage device.

      NTFS probably comes second, since obviously Windows 2000/XP/Vista fully support it and you can at least read, if not write it on Linux/Mac.

      --
      const int one = 65536; (Silvermoon, Texture.cs)
      SJW, n: "Someone I don't like, and by the way I'm a fuckwit" - AC
    11. Re:Great by digitrev · · Score: 1

      Whereas I'm too lazy to reply to anyone who replies to me.

      --
      Cynical Idealist
    12. 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.
    13. Re:Great by AmiMoJo · · Score: 1

      Is there a simple way to format a USB drive as UDF in Windows? Normally you only get FAT, FAT32, NTFS and if on Vista exFAT.

      --
      const int one = 65536; (Silvermoon, Texture.cs)
      SJW, n: "Someone I don't like, and by the way I'm a fuckwit" - AC
    14. Re:Great by afidel · · Score: 1

      FORMAT X: /FS:UDF from Vista.

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

      I remember it an I'm 19, don't feel bad.

      --
      Obligatory blog plug: http://www.caseybanner.ca/
    16. Re:Great by A+nonymous+Coward · · Score: 1

      Hell, I'm too lazy to even read your posts.

    17. Re:Great by AmiMoJo · · Score: 1

      Ah, okay, it does not seem to be supported under XP or XP x64 (2003 kernel).

      --
      const int one = 65536; (Silvermoon, Texture.cs)
      SJW, n: "Someone I don't like, and by the way I'm a fuckwit" - AC
    18. Re:Great by Trogre · · Score: 1

      No data points here, but when I formatted my 8GB flash disk as EXT3 (was FAT32), I saw an almost ten-fold increase in transfer speed.

      --
      "Nine times out of ten, starting a fire is not the best way to solve the problem." - my wife
    19. Re:Great by hairyfeet · · Score: 1

      I always thought you would die of blunt force trauma from beating your head against the wall in frustration as you waited on the damned thing to boot. I guess you're right, it IS important to read tech sites every day!

      P.S. I still think the bleed in the brain from the blunt force trauma would actually get you before the aids and cancer would. Especially if you got the "frustration special" they offered on Black Friday with a Celeron desktop processor in a laptop with a lousy 1GB of RAM and Vista Basic. After all, just as you finally got to the desktop the Celeron would have sucked your battery dry and your screen would go black! Now THAT brings torture to a whole new level!

      --
      ACs don't waste your time replying, your posts are never seen by me.
    20. 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...
    21. Re:Great by modestgeek · · Score: 1

      I was too lazy to interpret this. Say what now?

    22. Re:Great by Anonymous Coward · · Score: 0

      NTFS probably comes second, since obviously Windows 2000/XP/Vista fully support it and you can at least read, if not write it on Linux/Mac.

      NTFS Write support on Linux has been production quality (if not necessarily full speed) on Linux for some time now with NTFS-3G.

    23. Re:Great by arekusu_ou · · Score: 0

      19, that's almost 20. You should feel old. The average non-poor family 10 - 20 year old is likely to be as technologically sophisticated as any non-professional in the country. Kids have been doing drugs and having sex half your life already. And pregancies have started in the last quarter of your life. You need to catch up because it's all downhill from here man.

    24. Re:Great by post.scriptum · · Score: 1

      I'd mod you up if I could.

  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?

    1. Re:No JFFS2? by tabrisnet · · Score: 1

      OSS is part of a healthy diet and all, but JFFS{,2} is for raw flash, not for flash with an IDE front-end.

    2. Re:No JFFS2? by rvw · · Score: 1

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

      And I want to know how RAID 9 performs when I plugin my 27 USB sticks. How about that? Why doesn't anybody think about these useful situations?!

    3. Re:No JFFS2? by Anonymous Coward · · Score: 0

      I've had little trouble with NTFS formatted USB drives and interoperability, Ubuntu reads/writes to them without any effort (but it is a (valid) pain that Ubuntu detects improperly unmonted drives), OS X reads them well but requires third-party (but slow open-source) drivers to write. OK, forget embedded devices to support them though (such as PMPs, etc.)

  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!
    1. Re:Same applies to SSDs? by Tisha_AH · · Score: 1

      The differences between filesystems is not that surprising and you can see a common trend across all of the USB flash drives. This is a good heads-up comparison of the filesystems.

      I have a great interest in the differences between manufacturers and models of the flash-drives. You can clearly see who is using faster chips and who is using the dregs out of a bucket full of memory chips. The filesystem comparisons are dwarfed by the hardware speed.

      Once a USB flash-drive is put in a convenient plastic case no-one ever looks at access speed. While we all debate the advantages of filesystems and USB 1.0, 1.1 or 2.0 we sometimes forget that it's the chip that becomes the factor limiting performance.

      When have you ever seen a USB flash drive that lists the access times in uSec? We all look with great interest at RAM, hard-drive access speeds, video performance yet we treat a USB flash drive like a mouse.

      --
      Tisha Hayes
  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 neokushan · · Score: 1

      You mean like exFAT? Which, as far as I'm aware, is basically just FAT64. I.e. it's got all the "benefits" of FAT32 without the filesize limit, probably at the cost of a bit of performance.

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

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

    3. Re:not so fast by neokushan · · Score: 1

      I'd wager that it's more compatible than NTFS, though.
      Still, it's not ideal and I agree with what you're saying.

      --
      +1 IDisagreeSoHeMustBeATrollOrAnAstroturferOrAShill
    4. 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. Re:not so fast by evilbessie · · Score: 1

      Ah but I have 4 million 1K files do I still use FAT? FAT32 is quite crap really but in the situation of USB flash drive it may not encounter some of it's issues.

    6. Re:not so fast by Salgat · · Score: 1

      I'm surprised that there is no universal standard to concatenate the two files into a single file in FAT32.

    7. Re:not so fast by Kirth · · Score: 1

      Well, FAT is mostly "not so fast". That thing _crawls_ if it has to cope with directories with lots of files.

      Besides, the only use for that fucked-up filesystem is data exchange with operating systems which don't support decent filesystems. Unless I need that functionality, I'd use ext2.

      --
      "The more prohibitions there are, The poorer the people will be" -- Lao Tse
    8. Re:not so fast by jridley · · Score: 1

      Probably much less so, in fact. Heck, almost every OS has NTFS compatibility these days. exFAT doesn't. Not Macs, not Linux (not licensed anyway, maybe someone has a module for it). Even XP doesn't unless the hotfix has been applied, which had probably happened on all of 300 PCs worldwide.

      So it's essentially useless for carrying files around to any randomly selected PC.

      NTFS thumb drives are readable widely, by contrast.

    9. Re:not so fast by Sturdy · · Score: 1

      That's a tough wager when 90% of PC's natively support NTFS and FAT[32] but not much else. Perhaps you mean exFAT is more "open" than NTFS?

    10. Re:not so fast by petermgreen · · Score: 1

      I'd wager that it's more compatible than NTFS, though.
      Afaict exFAT is compatible with vista SP1+, XP SP2+ with a hotfix (that few are likely to have installed) and CE 6.0 .

      Afaict NTFS is compatibile with the whole NT line of windows (though apparently vista doesn't like to boot from partitions that have been touched by NT4 for some reason which caused some fun for resize tools) and with linux through NTFS-3g.

      I'd wager that systems that support NTFS but not exFAT (XP without the hotfix, vista pre-sp1, previous versions of the NT line and linux with NTFS-3G) are more common than systems that support exFAT but not NTFS (just CE 6.0 afaict).

      --
      note: i'm known as plugwash most places but i screwd up registering that here somehow in the past and now can't register
    11. Re:not so fast by neokushan · · Score: 1

      Ahh yes, you've hit the nail on the head there. My bad!

      --
      +1 IDisagreeSoHeMustBeATrollOrAnAstroturferOrAShill
    12. Re:not so fast by Sturdy · · Score: 1

      Tangent: I do wonder when MS will announce their next update to NTFS. Or, for that matter if/when they'll natively support mounting more file systems. I'm certainly not expecting WinFS to arrive anytime soon!

    13. Re:not so fast by neokushan · · Score: 1

      WinFS is not a file system, it was never anything to replace NTFS. It was a database technology, a layer that sat on top of the filesystem and used to keep information about the files within said system.

      As for NTFS, I think it actually has changed over the years, just not enough to break compatibility yet. Who knows what they have planned next, call me cynical but I wouldn't be surprised if we had a new filesystem that was just basically NTFS with a few tweaks, enough to break it on Linux.

      --
      +1 IDisagreeSoHeMustBeATrollOrAnAstroturferOrAShill
    14. Re:not so fast by Sj0 · · Score: 1

      WinFS Is Not a FileSystem?

      Curse you, oh insidious recursive acronyms!

      --
      It's been a long time.
    15. Re:not so fast by neokushan · · Score: 1

      WinFS = Windows Future Storage.

      --
      +1 IDisagreeSoHeMustBeATrollOrAnAstroturferOrAShill
    16. Re:not so fast by Sj0 · · Score: 1

      I bet you kick kittens too.

      --
      It's been a long time.
    17. Re:not so fast by Bert64 · · Score: 1

      And why did they create exFAT, a completely new and not compatible with anything else filesystem at all?
      There are hundreds of filesystems out there, it is absolutely insane and quite insulting that they would create a new proprietary one. Why not just use one of the ones that already exists?

      --
      http://spamdecoy.net - free throwaway anonymous email - avoid spam!
    18. Re:not so fast by TemporalBeing · · Score: 1

      Not sure why exactly...probably because FAT is used a lot, and can be supported by devices without a lot of overhead. Not sure how exFAT fits in there, but I would guess that it probably has a similar low-overhead design.

      In comparison, ext2 and NTFS have a lot higher overhead as you have to map a lot more stuff to be able to read/write.

      Of course, the low-overhead is also one of the reasons why FAT has a lot more corruption in it too.

      --
      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 Chabo · · Score: 1

      Do you mean "patent"?

      --
      Convert FLACs to a portable format with FlacSquisher
    2. 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!
    3. Re:NTFS patten? by Joe+Snipe · · Score: 4, Funny

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

      --
      Sometimes, life itself is sarcasm...
    4. Re:NTFS patten? by Anonymous Coward · · Score: 0

      Would it not be a trademar instead of a patten?

    5. Re:NTFS patten? by Anonymous Coward · · Score: 0

      No, it's a traddemak.

    6. Re:NTFS patten? by Chabo · · Score: 1

      It only has a patent on it if you say it like the British do: "pay-tent". If you say it like a true American -- "pah-tent", then there's no law broken.

      --
      Convert FLACs to a portable format with FlacSquisher
    7. Re:NTFS patten? by jgtg32a · · Score: 1

      dammit.

      Actually I did write Patton the first time, and then I changed it to patten.

      Which is apparently a type of shoe.

    8. 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.

    9. Re:NTFS patten? by Anonymous Coward · · Score: 0

      Thanks for entertaining me. I will give you a simple answer for that:
      http://www.ntfs-3g.org/support.html#patent

      What about the NTFS patents?
      No NTFS patent is known in any country.

    10. Re:NTFS patten? by Idiomatick · · Score: 1

      thats patently ridiculous. patent(law) and patent(obvious) are totally different words. The law is said pah-tent the obvious is said pay-tent

    11. Re:NTFS patten? by Chabo · · Score: 1

      I'm American, but I've never heard Brits use "pah-tent" in any context. In Jeremy Clarkson's "Inventions that Changed the World" series, for example, when he was talking about the race to the patent office between Alexander Graham Bell and Elisha Gray, pronounced it "pay-tent".

      The OED says that both pronunciations are valid for the legal document:
      http://www.askoxford.com/concise_oed/patent?view=uk

      --
      Convert FLACs to a portable format with FlacSquisher
    12. Re:NTFS patten? by Sj0 · · Score: 1

      Not THE Patton, A Patton.

      I'm sure the general has a cute granddaughter (She'd be about 20 now, right?), I wouldn't mind having THAT patton on top of me(Assuming she's cool).

      --
      It's been a long time.
  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 Anonymous Coward · · Score: 0

      You might have trouble finding your files on ReiserFS.

    3. Re:Question by Hal_Porter · · Score: 1

      If you chop it into bits they won't be able to find it.

      --
      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;
    4. 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.
    5. 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?

    6. Re:Question by elrous0 · · Score: 1

      I lost my ReiserFS-formatted drive. It must be somewhere in Russia.

      --
      SJW: Someone who has run out of real oppression, and has to fake it.
    7. Re:Question by LonghornXtreme · · Score: 1

      Only if your name is Hans...

  7. Size matters by Thanshin · · Score: 1

    Did he run tests with 16GB files?

    1. 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.

    2. 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.

    3. Re:Size matters by sexconker · · Score: 1

      And because "4 GB" drives don't support files much larger than 3.72529 GB.

    4. Re:Size matters by Fred_A · · Score: 1

      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.

      Which is a real shame since I was really looking forward to seeing his technique for fitting those 16GB files on 8 or 4GB drives. Curse you Microsoft !

      --

      May contain traces of nut.
      Made from the freshest electrons.
    5. Re:Size matters by Anonymous Coward · · Score: 0

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

      Yeah, just another stupid Windows limitation

    6. 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)
    7. Re:Size matters by morgan_greywolf · · Score: 1

      $ bzip2 -f9 foo

    8. Re:Size matters by Anonymous Coward · · Score: 0

      I had 120 GB FAT32 drive as well. I think Windows 98 didn't have the 32GB restriction.
      It was very nice while I still dual-booted win98/Linux, but video recording was limited to 10 minute pieces because of the file size limit.

      Occasionally I use rar (without compression) to split and recombine files if I need to move it using an flash drive.

    9. Re:Size matters by Rich0 · · Score: 1

      Actually, with an appropriate filesystem they might - sort-of. I believe that newer filesystems can record the presence of zero-filled blocks without allocating the blocks. So, you could have a 1TB file full of zeros that takes just one inode or something along those lines.

    10. Re:Size matters by Anonymous Coward · · Score: 1, Informative

      Yes, Windows has a built in artificial limitation for formatting FAT32 because they want you to use NTFS. Format with Linux instead for 32GB+.

    11. Re:Size matters by Anonymous Coward · · Score: 0

      The 32GB limit in Windows when formatting FAT drives is by design. I guess they tried to get people to migrate towards NTFS.

    12. Re:Size matters by Anonymous Coward · · Score: 0

      I know I lost a few GB just to the formatting alone.

      Was that due to formatting or due to misleading advertising by the drive manufacturer seeing as manufacturer gigabytes tend to be about 24 megabytes smaller than actual gigabytes?

    13. Re:Size matters by jabuzz · · Score: 1

      Sparse files have existing since forever.

    14. Re:Size matters by Anonymous Coward · · Score: 0

      4GB drives with NTFS support sparse files.

    15. Re:Size matters by coolsnowmen · · Score: 1

      I understand, but then you are using the fs to do transparent compression. That argument fails in this case because filesize=size_on_disc. Otherwise you could argue that a 3mb mp3 is really a 30MB .wav file...but it's not, it is a compressed file.

    16. Re:Size matters by m50d · · Score: 1
      True, but it will happily install (at least using the Linux Kernel's driver for it) on any size drive.

      Not so; the limit is quite low, IIRC 274GB (and even that requires a non-standard cluster size). Yes, the 32GB limit in windows XP is fake (and you can bypass it by using an earlier version of windows), but the hard limit isn't so much higher.

      --
      I am trolling
    17. Re:Size matters by TemporalBeing · · Score: 1

      No it wasn't. I'm talking about going from like 120GB to 100 GB. I'm well aware of the misleading manufacture info and this was well above and beyond that change, which was most evident because the drive _came_ formatted at a larger size than what I had in the end.

      Manufacturer's base their numbers on base 10, as opposed to computer systems which use base 2. So for every kilobyte, the manufacturer will by shy by 24 bytes. The easiest way to compute the actual size of the drive is take the base 10 number in bits, convert to bytes (div by 8), and then computer up to the size using 1024 instead of 1000. For example:

      1 TB = 1,000 GB = 1,000,000 MB = 1,000,000,000 KB = 1,000,000,000,000 Bits = 125,000,000,000 bytes = 122,070,312.5 KB = 119,209.28955078125 MB = 116.415321826934814453125 GB

      --
      Truth is like the sun. You can shut it out for a time, but it ain't goin' away. - Elvis Presley (source: imdb.com)
    18. Re:Size matters by Anonymous Coward · · Score: 0

      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).

      Ya, I ran into that issue as well. If you're just unwilling to boot a linux distro to do the format, you can always partition the drive out.

      But that isn't much of an issue for the USB thumb drives since most are 8gigs or less still, but if you are using a USB-attached HD/SSD you might see it pop up.

    19. Re:Size matters by Bert64 · · Score: 1

      I hate artificial restrictions like this...
      Software should perform to the best of it's ability.
      The fact they spent time and effort to REDUCE functionality is just absolutely farcical. Wouldn't that development effort have been better spent trying to improve functionality instead?

      --
      http://spamdecoy.net - free throwaway anonymous email - avoid spam!
  8. 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.
    1. Re:incomplete tests by corsec67 · · Score: 1

      I have seen a couple of problems with FAT based flash drives.
      What happened in both cases was that the files got "locked", and couldn't be deleted on OSX and Linux, but a fsck fixed the issue.

      --
      If I have nothing to hide, don't search me
    2. Re:incomplete tests by Nimey · · Score: 1

      I've been around a while. Let me tell you, there are many ways to screw up a FAT-formatted volume, most especially the computer powering off in the middle of a write. I've had far fewer problems in that regard with NTFS, probably because NTFS is journaled.

      --
      Hail Eris, full of mischief...

      E pluribus sanguinem
    3. Re:incomplete tests by WuphonsReach · · Score: 1

      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 ...

      Ugh... FAT32 is so much more likely to lose data compared to NTFS (which is journaled). (My only data loss due to a screwed up FS is due to FAT32 going crazy.)

      (Either way, I always setup my flash drives to auto-backup when they are hooked up to my PC.)

      --
      Wolde you bothe eate your cake, and have your cake?
    4. Re:incomplete tests by PatentMagus · · Score: 1

      I don't trust NTFS journaling yet. It wasn't all that when they slapped it into NTFS v3.0. Perhaps they don't (didn't) journal the master file table? That's where my drive got corrupted. Decent journaling would have dealt with that. It has been many years since I lost that NTFS partition and my FAT32 formated flash drives have been robust. I haven't experimented with NTFS formatting since the mishap.

      Over all, I'm a little embarrassed to be talking about which is better: NTFS or FAT32. ext3 is better than either. I haven't played with reiserFS since I met hans and I worried it might be an extension of his personality.

      --
      I am a lawyer, but not yours. Anything I tell you might be a total lie intended to benefit my clients at your expense.
    5. Re:incomplete tests by Anonymous Coward · · Score: 0

      How do you know ext3 is better than NTFS? You said you've not touched NTFS for years now...

    6. Re:incomplete tests by Anonymous Coward · · Score: 0

      I haven't played with reiserFS since I met hans and I worried it might be an extension of his personality.

      Worried your flash drive might go M-5 on you? ;)

    7. Re:incomplete tests by jridley · · Score: 1

      This is actually one of the best reasons to use FAT32. Windows automatically configures FAT32 filesystems "optimized for quick removal" - that means that they don't do write caching. With other filesystems, the OS may have data intended to be written to the flash device, but not write it until you tell it you want to dismount the device.

      With write caching disabled, if the drive access light has stopped flashing, you're good to just yank the drive. With NTFS or some other filesystem, no, you really need to properly eject the device.

      I toyed with NTFS for a while due to wanting one big 8GB TrueCrypt volume, but in the end it was too much of a pain to manually unmount things every time I wanted to take a file over to a friend's machine.

    8. Re:incomplete tests by PatentMagus · · Score: 1

      That's exactly it. Even those of us that know about flushing the cache will eventually make a mistake. I dismount the drive at least 15 times a week. Repeat for years and eventually you mind fart and screw something up. Across that amount of time it isn't rare to get a windows freeze up requiring a hard reboot or power cycle.

      --
      I am a lawyer, but not yours. Anything I tell you might be a total lie intended to benefit my clients at your expense.
    9. Re:incomplete tests by PatentMagus · · Score: 1

      That's like asking how do I know that that midget will punch me in the sack again if I haven't patted him on the head in years.

      --
      I am a lawyer, but not yours. Anything I tell you might be a total lie intended to benefit my clients at your expense.
  9. What about UFS? by tchuladdiass · · Score: 1

    Would one of the UFS variations be suitable for flash drives? And also better portability (almost all OS's support UFS by now). Would performance be better?

    1. Re:What about UFS? by Anonymous Coward · · Score: 0

      What are these "almost all" OSs that syupport a specific UFS format?

    2. Re:What about UFS? by tchuladdiass · · Score: 1

      Actually I meant UDF.

  10. 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 khellendros1984 · · Score: 1

      Writing files in NTFS is apparently somewhat complex. I don't know *that* much about it, except the it uses B+ trees to store some of it's information (which are a little difficult to write), and that it took a *long* time before Linux had NTFS write capability. They were stuck on read-only for a long while.

      --
      It is pitch black. You are likely to be eaten by a grue.
    2. 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;
    3. Re:Read vs Write by Salgat · · Score: 1

      All I know is that FAT32 is incredibly simple for writing to. It just sequentially writes to memory in every free spot available, adding the address of the next cluster of the data to a table at the beginning of the partition. NTFS must just be much more complex in handling all the writing. When you add several extra operations every time you write to a 4KB or larger cluster, the delay would seem to build up rather quickly.

  11. 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 Anonymous Coward · · Score: 0

      So when you add security checks to the chain of procedures, things slow down a bit? Fancy that! ;) No wonder my parents' old Pentium/60MHz blazed through Windows 3.1 but could only just keep up with Windows 95... damn those extra layers of operating system!

      Can't we just go back to DOS, back before the ability to nest directories inside of each other? =)
      -- os

    3. Re:Don't install your OS on FAT32... by Anonymous Coward · · Score: 0

      And also don't copy important material. Flash memories are the safest one. Somewhere a have red that it can store data up to 10 years. But What is it good for if data lost it's integrity? FAT doesn't have any self correcting mechanism or journal storage or any redundancy. So if something bad happens to FAT it is big problem to put files together. On the other hand NTFS has evil mechanism of Alternate data streams that store some crap like that the origin of the file is from internet (who cares?), but most usage of this stupid mechanism is for hiding viruses & co.

    4. Re:Don't install your OS on FAT32... by Khyber · · Score: 1

      You might want to scan your computer for SecuROM, then, considering one of it's first priority tasks is to usurp your Administrative privileges.

      --
      Still waiting on Serviscope_minor to wake up to fucking reality and realize that Jessica Price isn't going to fuck him.
    5. Re:Don't install your OS on FAT32... by Anpheus · · Score: 1

      Agreed, I had two files left over from installing Bioshock that couldn't be moved if I used a sledgehammer, for all I know. Nothing I did worked and I ended up giving up trying to move or remove them.

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

      Google "unlocker". Very useful tool.

    7. Re:Don't install your OS on FAT32... by AmiMoJo · · Score: 1

      Another issue for a lot of people is that FAT32 does not support Unicode for file names. In other words, if your Windows system is English you can't save files with Japanese names on a FAT32 drive.

      NTFS and ext2 fully support Unicode. I usually use Unicode on my flash drives, and despite what the article suggests it does not seem to affect performance noticeably.

      --
      const int one = 65536; (Silvermoon, Texture.cs)
      SJW, n: "Someone I don't like, and by the way I'm a fuckwit" - AC
    8. 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...

    9. Re:Don't install your OS on FAT32... by BenoitRen · · Score: 1

      Why does this have to be ingrained into the file system? Why can't it just be as simple as not allowing non-system processes to write to system directories like C:\Windows?

    10. Re:Don't install your OS on FAT32... by morgan_greywolf · · Score: 1

      When we impeach Bush, can we do something about Memphis' "King Willie" please?

      Psssst. Might wanna change your sig. Bush is no longer a sitting president and hence, can't be impeached.

    11. Re:Don't install your OS on FAT32... by Khyber · · Score: 1

      Impeach: 1. To make an accusation against.
            2. To charge (a public official) with improper conduct in office before a proper tribunal.

      We can still Impeach Bush. Doesn't matter if he's sitting President or not.

      --
      Still waiting on Serviscope_minor to wake up to fucking reality and realize that Jessica Price isn't going to fuck him.
    12. Re:Don't install your OS on FAT32... by Animaether · · Score: 1

      unlocker (if you use Vista, make sure to set it to run as administrator by default in its properties tab) is great for -unlocking- files that are in use... e.g. some program or service has a file handle open on it.

      it does crap all for permissions issues.. so do the actually permissions tools in Windows if the permissions table itself is corrupt (had to remove two folders recently because vista wouldn't even let me change the owner.. teehee)

      a boot CD (UBCD / UBCD4WIN) can be *very* useful for these types of things - presuming you didn't encrypt your drive.

    13. Re:Don't install your OS on FAT32... by Anpheus · · Score: 1

      Boot CDs can corrupt the volume shadow copies because they don't correctly deal with them.

      This means you can lose your system restore functionality in one fell swoop.

    14. Re:Don't install your OS on FAT32... by shutdown+-p+now · · Score: 1

      sometimes I have problems moving or deleting the Windows directory because I do not have enough permissions and taking ownership does not work.

      Taking ownership alone may not be sufficient, because the ACL for a file can specify "deny write" for the owner as well (just like it can on any Unix system). So you need to take ownership, and then to give yourself full rights for the file (which is something that you can only do as an owner), and only then you will definitely be able to delete it. Some Vista system files in particular have deny write for all except for a special "TrustedInstaller" account, presumably to make it harder to mess up one's system inadvertently.

    15. Re:Don't install your OS on FAT32... by Anonymous Coward · · Score: 0
      You'll find that while the dictionary is a great first point of reference for unfamiliar words, it is not an authoritative source on language.

      Impeachment is a specific legal process laid out in the United States Constitution. It can no longer be applied to an official who has left office. While "impeach" may sound like the proper word based on the dictionary, it is a word carrying multiple definitions in different contexts. It's an inappropriate in the context you're using it. You're looking for something more along the lines of "indict".

    16. Re:Don't install your OS on FAT32... by Khyber · · Score: 1

      No, we can IMPEACH. I can accuse publicly all the fuck I want. Should the judges act on my accusations, THEN they would indict.

      Semantics won't work on me. Electronic Arts is finding this out the HARD WAY.

      --
      Still waiting on Serviscope_minor to wake up to fucking reality and realize that Jessica Price isn't going to fuck him.
    17. Re:Don't install your OS on FAT32... by Walter+Carver · · Score: 1

      JFYI: if you dont have unlocker available, then you can loggoff and login again.

    18. Re:Don't install your OS on FAT32... by Pentium100 · · Score: 1

      Taking ownership alone may not be sufficient, because the ACL for a file can specify "deny write" for the owner as well (just like it can on any Unix system).

      And I tried it. Taking ownership, giving the "administrators" group full control permissions, giving my user name full control permissions and giving "everyone" full control permissions. Yet, I was unable to delete the file. This has happened with two files in c:\windows\system32\macromedia directory.

    19. Re:Don't install your OS on FAT32... by repvik · · Score: 1

      Doesn't necessarily help. I've had windows lock up a file where I had to erase it on boot (using unlocker), since it would be relocked upon boot.

    20. Re:Don't install your OS on FAT32... by shutdown+-p+now · · Score: 1

      The only thing that it can mean (to the best of my knowledge) is that some other app has opened the file and locked them for deletion. For DLLs from a system folder of a non-running OS, I could only think of an anti-virus (seen that sort of thing before).

    21. Re:Don't install your OS on FAT32... by Anonymous Coward · · Score: 0

      Try booting to Safe Mode command line.

      If that doesn't work just use a bootable linux distro that will handle ntfs.

    22. Re:Don't install your OS on FAT32... by Pentium100 · · Score: 1

      Well, my main PC does not have antivirus software installed (I use online scanning sites to scan downloaded files :), and it was not a "file in use" problem, Unlocker, would have taken care of that. It was an "access denied" problem, I could not clear the "read only" attribute, which was in the third state (neither checked nor unchecked). Couldn't delete the file either...

    23. Re:Don't install your OS on FAT32... by Sj0 · · Score: 1

      A far more important problem is that FAT32 has terrible reliability.

      One of the greatest advances of moving from Windows 98 to Windows 2000 or XP was that FAT32 would randomly decide your boot drive shouldn't boot anymore. After the change, a major failure mode of PCs disappeared.

      --
      It's been a long time.
    24. Re:Don't install your OS on FAT32... by Sj0 · · Score: 1

      Are you nuts?!

      My directories were beautifully structured before Windows. It was a work of functional art.

      Now I don't even know where they put anything.c:\program files\vendor name\program name? c:\documents and settings\username\Application files\vendor name\random squiggles?

      I remember it used to be my games were in c:\games. My tools were in c:\tools. My applications were in c:\tools. All of them were accessed with hdm4, in c:\hdm4.

      The old days were nice.

      --
      It's been a long time.
  12. 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.

    1. Re:Important for me by jawtheshark · · Score: 1

      I have experimented with NTFS on USB sticks too and the last point you gave, brought me back to FAT.

      However, I found you can work around it by setting the ACLs to "Everyone","Full Access". After you do that, it doesn't matter anymore. I don't call that "obscure NTFS file permissions": that's bog standard stuff.

      That said, the problem you describe (with source codes) should be fixed because this is a terrible way of working around. For this kind of stuff one usually uses version control software. I do realise that they get your source code that way (or you theirs), but your collaborating for crying out loud!

      Let the lawyers make a contract allowing each other to see the code under an NDA or something like that. I'm not a lawyer, so ask one. I'd hate to be put in such a situation.

      Another alternative is writing an API an delivering a DLL, which is a much better alternative. (Or if it's Java, give them a JAR, obfuscated of course...)

      --
      Ahhh...the great dumpster continuum. Many a free computer will be found there. -- sowth (748135)
    2. Re:Important for me by bmorency · · Score: 1

      I'm currently on site at a customer's office.

      Wow, you are posting on slashdot while at a customer's office? You have to let me know how you bill the customer for that? :-)

    3. Re:Important for me by justthinkit · · Score: 1

      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.

      How do you figure? Run diskmgmt.msc, right click on drive in question, "Format..." etc. Defaults to NTFS for me.

      --
      I come here for the love
    4. Re:Important for me by Anonymous Coward · · Score: 0

      The write cache would not have affected the review because, by default, Windows disables write caching for removable drives (including other things like NTFS file-access stamping).

  13. Slashdotted by Nimey · · Score: 1

    Since the article is /.ed and I can't RTFA anyway, a question: I'm about to have a user start backing her files up to a 32GB USB stick. Probably no huge movie files. Should I format the stick as NTFS or exFAT (she's running Vista SP1)?

    --
    Hail Eris, full of mischief...

    E pluribus sanguinem
    1. Re:Slashdotted by Falstius · · Score: 1

      According to the benchmarks, exFAT. If you trust it not to die a horrible death and to be readable anywhere else.

  14. Re:exFAT by D.+Taylor · · Score: 1

    Except if you'd even bothered to read the summary, you'd notice he did consider ExFAT. Whoops.

  15. 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 emj · · Score: 1

      Don't bother with vfat, use what is best for your computer. And as an extension of what is stated bellow you can always install drivers for ext2 + a bootable Linux on the flash drive. A whopping 50MB would be needed.

    2. Re:Installing the ext2 driver? by Anonymous Coward · · Score: 0

      I noticed (on a USB hard-drive, big one) that ext3 performed miles above vfat (at least on Linux).

    3. 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!
    4. Re:Installing the ext2 driver? by Anonymous Coward · · Score: 0

      The biggest difficulty with FAT is the loss of file permissions. 95% of my use of USB drives, is for a quick backup of the day's work, and for moving things around between laptop, desktop, and work machines. I've given up playing tar games, and now just format it ext2. It works transparently on the various linuxies and life is so much simpler.

      I keep a second, FAT-formatted usb flashdrive in the desk drawer for the rare occasions I need to transfer to or from windows. Or I can use my music player's storage for that.

    5. Re:Installing the ext2 driver? by shokk · · Score: 1

      Are you finding a lot of danger in passing Windows viruses to your Linux system in your daily life that you need to avoid FAT32?

      --
      "Beware of he who would deny you access to information, for in his heart, he dreams himself your master."
    6. Re:Installing the ext2 driver? by rolfwind · · Score: 1

      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 [fs-driver.org] 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.

      I like to run my Ubuntu off a usb stick, since Ubuntu Live CD makes it so simple to install to one that someone like me can do it - and since I can have all my firefox settings, passwords, programs, and preferences as I want them without carrying my computer or leaving traces of my info on other people's computers. So yes, it'd be nice to know how fast ext2/3 runs off a flash drive. It probably has more of an impact as well, as the one-time-per-session transfering of files most USB users use their sticks for is relatively much simpler and less demanding.

    7. Re:Installing the ext2 driver? by tepples · · Score: 1

      I like to run my Ubuntu off a usb stick

      Until you end up on a PC with pre-USB 2.0 USB ports, or a PC whose BIOS doesn't know how to boot from USB, or a PC that you don't want to reboot. Often at my aunt's house, the boy using the PC wants me to use Windows Fast User Switching instead of rebooting so that he doesn't have to take ten minutes opening the windows for the dozen projects that his ADD self works on at the same time. (I got so fed up that I bought a laptop.) If you want to limit the discussion to your own PC, you could use a USB hard drive, which should have better-known performance characteristics.

    8. Re:Installing the ext2 driver? by Anonymous Coward · · Score: 0

      The same thing would hold true for formating in NTFS. No Linux, Solaris or Mac machines could readily open the drive.

    9. Re:Installing the ext2 driver? by petermgreen · · Score: 1

      Of course for the next few years the same will apply to exfat. XP is going to take quite some time to dissapear and doesn't support it by default.

      --
      note: i'm known as plugwash most places but i screwd up registering that here somehow in the past and now can't register
  16. 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.

    1. Re:You can partition flash drives by jridley · · Score: 1

      Actually, I've not been able to partition many of my flash drives. They appear to have the partitioning burned into them or something. Some I can, some I can't.

  17. Re:exFAT by Anonymous Coward · · Score: 0

    This can also be used on XP - the drivers from Vista install on it just fine.

  18. 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.

  19. NTFS Permissions/Speed by Ohio+Calvinist · · Score: 1

    I've always been under the impression that NTFS is inherently slower (though I do not know exactly "how much") because of the processing of ACLs/Audit events that do not take place under FAT32, and that other than for these "features" NTFS and FAT32 are very similar.

    --
    Forgive my spelling from time to time. I'm often posting during short breaks.
  20. 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
    1. Re:Filesystem for Slashdotters by spintriae · · Score: 1

      I use exclusively free *nixes and so does all my friends (otherwise they wouldn't be real friends, would they?).

      If *nix use is among your criteria for determining friendships, good luck finding one with a vagina.

    2. Re:Filesystem for Slashdotters by jalefkowit · · Score: 1

      They make a *nix with a vagina?

    3. Re:Filesystem for Slashdotters by spintriae · · Score: 1

      Yes, Darwin I believe.

    4. Re:Filesystem for Slashdotters by swillden · · Score: 1

      I have heard someone say that ext2 means less wear on the drive than ext3 (something with journaling?).

      I don't think that matters any more. Flash drives do automatic wear leveling internally, now, because they're optimized for FAT32 which has some severe "hot spots".

      --
      Note to ACs: I usually delete AC replies without reading them. If you want to talk to me, log in.
    5. Re:Filesystem for Slashdotters by Anonymous Coward · · Score: 0

      Yeah, Vaginix. Haven't you heard of it?

  21. Choose NTFS for the life of your drive by Xygon · · Score: 1

    There's one other reason to choose NTFS: the file system is spread across the drive, versus having a localized FAT table. Unless the wear-leveling on the drive is good (and most controllers for USB sticks are more than sufficient for what they're designed for, but I wouldn't call "good," they're designed for price), you end up with very uneven wear on a finite-life product. Add in that the USB market takes the lowest grade of memory available, and I'd trust NTFS over FAT, generally.

    That said, I still use FAT, because as long as my thumb drive works long enough to move my presentation from my laptop to my customer's, it's done its job. I don't expect it to have a long life, and I have an unlimited stream of new drives to play with.

    1. Re:Choose NTFS for the life of your drive by Anonymous Coward · · Score: 1, Insightful

      Why worry about wear leveling? When's the last time you ran out of ink in a ballpoint pen before you lost it?

    2. Re:Choose NTFS for the life of your drive by Anonymous Coward · · Score: 0

      Actually, others say just the opposite: that because of the journalling, NTFS will wear out the USB drive faster.

    3. 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
  22. What year is this from? by Anonymous Coward · · Score: 1, Insightful

    Yay, we have an answer to which of these two obsolete legacy fs works best with this modern hardware. But you left out Amiga FFS and MacOS HFS.

    Funny there's no mention of ext4 and reiser3 and xfs.

    1. Re:What year is this from? by HTH+NE1 · · Score: 1

      Given a big enough partition table, I could put 125 ProDOS partitions on that (4 GB / 32 MiB).

      --
      Oh, say does that Star-Spangled Banner entwine / The myrtle of Venus with Bacchus's vine?
    2. Re:What year is this from? by ivan256 · · Score: 1

      Given this comment, I certainly hope your username is meant to be ironic.

    3. Re:What year is this from? by HTH+NE1 · · Score: 1

      What, you think an Apple II can't use USB?

      --
      Oh, say does that Star-Spangled Banner entwine / The myrtle of Venus with Bacchus's vine?
    4. Re:What year is this from? by morgan_greywolf · · Score: 1

      The real question: Why would you want to do that?

    5. Re:What year is this from? by Nimey · · Score: 1

      BECAUSE IT'S THERE!

      Obviously.

      --
      Hail Eris, full of mischief...

      E pluribus sanguinem
    6. Re:What year is this from? by m50d · · Score: 1

      Comparing ext4 to reiser3? Biased much?

      --
      I am trolling
  23. 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.

    1. Re:FAT32 and MS Backup by Anonymous Coward · · Score: 0

      This is a very good point. I recently did an audit of a medical facility. The critical patient records were backed up to external usb hdd nightly. The external usb hdds were formatted fat32- as most usb storage devices- even 250gb disks- seem to arrive. Ntbackup was the program used to backup the medical record data store, which rolled up into a 6gb file. Ntbackup wrote the first 4gb happily, then failed silently, discarding the remaining 2gb of potentially life critical patient records.... This wasn't the only backup mechanism, but the contractors that had installed the backup didn't catch it, as the datastore was less than 4gb rolled up when they installed the backup procedure. Different contractors are used now- so watch out for this one, potential disaster- really, does it make sense to ship >250gb devices today formatted with a max file size of 4gb? (-1byte)

  24. 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.......

    1. Re:The first two things I look for in a jump drive by DMUTPeregrine · · Score: 1

      There's a third important thing: If it has a keyring attachment point and a cap, is that point on the cap? This can cause you to lose the drive instead of just the useless cap.

      --
      Not a sentence!
  25. Very strange use of colours in the graphs by drspliff · · Score: 1

    I'm sure i cant be the only person who noticed this, but in many of the graphs TWO of the bars were coloured white with the other being red/green or whatever, not just that but they colouring seemed to be switched at random.

    That's a huge usability failure!

  26. Ext4 and Btrfs anyone? by gzipped_tar · · Score: 1

    This may sound off-topic, but has anyone tested ext4's performance on USB drives? I hope ext4's delayed allocation (well, something not specific to ext4) could provide some meaningful enhancement for USB usage. I'm considering the idea of ext4 on a flash drive with no journaling and noatime for LiveUSB. That being said, I'll have to make sure it works with GRUB..

    Also the new BtrFS is said to be optimized for SSDs. I wonder whether this will benefit USB flash drives too when it comes out.

    --
    Colorless green Cthulhu waits dreaming furiously.
  27. VFAT? by LittleBigScript · · Score: 1

    Why not VFAT? Or are these only windows formated filesystem types?

    1. Re:VFAT? by Nimey · · Score: 1

      VFAT is FAT16 with long file names. FAT16 is limited to 2GB partitions and I'm sure the max filesize is much less than that.

      So unless you're sticking with really small USB sticks, that's right out.

      --
      Hail Eris, full of mischief...

      E pluribus sanguinem
    2. Re:VFAT? by petermgreen · · Score: 1

      vfat is the name of a driver in win3.x and win9x not the name of a filesystem.

      If you meant fat with long filenames then those are going to be used by any modern version of windows on any variant of FAT.

      If you meant fat16 that isn't really suitable for 4GB drives ( 64KB is a stupidly big cluster size and not all implementation can handle it properly afaict )

      --
      note: i'm known as plugwash most places but i screwd up registering that here somehow in the past and now can't register
  28. NTFS burns up drives more quickly! by johanatan · · Score: 0

    NTFS' design dictates many more accesses than FAT. Yet another advantage of FAT32 if you care about longevity at all.

    1. Re:NTFS burns up drives more quickly! by _Splat · · Score: 1

      Accesses don't wear flash significantly compared to writes. Heavily read pages of NAND flash do need to be rewritten occasionally, but I can't imagine this alone would ever cause a device to reach its wear limit in normal use. NTFS does write more than FAT32, so you're still correct that FAT is better for reducing wear. FAT's fault tolerance is notoriously bad though.... would you rather lose your data or have to replace a $20 usb stick (which will probably be $2 by the time you wear it out)

      --
      -Splat
    2. Re:NTFS burns up drives more quickly! by johanatan · · Score: 0

      I meant access to envelop both reads and writes (a usage which is standard in some circles) because I couldn't remember whether it was reads or writes or both which affected lifetime. Thanks for the clarifications and good points though! :-)

    3. Re:NTFS burns up drives more quickly! by johanatan · · Score: 0

      And, how do you think that data wouldn't be lost when the drive does kill over? Looks to me like data loss is a risk either way; with NTFS, it just happens all at once when the drive dies and with FAT, it accumulates along the way! :-)

  29. Two problems by SanityInAnarchy · · Score: 1

    First: The drives are likely optimized for FAT32. I would not be surprised if they contained very specific optimizations based on knowledge of the internal FAT datastructures.

    Second: JFFS2 requires that you actually be able to access the flash device, not some mass storage layer on top of it. And isn't there something newer anyway?

    --
    Don't thank God, thank a doctor!
  30. Sync user names? by tepples · · Score: 1

    The biggest difficulty with FAT is the loss of file permissions. 95% of my use of USB drives, is for a quick backup of the day's work, and for moving things around between laptop, desktop, and work machines. I've given up playing tar games, and now just format it ext2. It works transparently on the various linuxies and life is so much simpler.

    How do you keep user names/numbers synchronized across different Linux installations well enough for this to work?

    1. Re:Sync user names? by Anonymous Coward · · Score: 0

      How do you keep user names/numbers synchronized across different Linux installations well enough for this to work?

      Just by choosing the same UIDs/GIDs for the home machines, as is used on the work network. There's no need to sync the whole company's userlist to home, only the few that I need (myself, and the project groups), which so far is easy enough to do by hand.

    2. Re:Sync user names? by tepples · · Score: 1

      Just by choosing the same UIDs/GIDs for the home machines, as is used on the work network.

      So if you work for more than one company, either at the same time (e.g. contractors/consultants) or just by leaving one company and joining another), do you have to install and reboot into more than one copy of your Linux distro so that your UIDs/GIDs on each copy match the configuration that each employer happens to use? And in any case, what Google keywords should I be using to set the uid for an already existing user in Linux?

    3. Re:Sync user names? by Anonymous Coward · · Score: 0

      Congratulations. If your intent was to be a dick, you've succeeded.

      So if you work for more than one company

      The answer is likely that he doesn't. I fail to comprehend your attacking someone for sharing their personal practice if it isn't congruent for every contrived scenario you come up with that doesn't apply in his case.

      And in any case, what Google keywords should I be using to set the uid for an already existing user in Linux?

      man apropos

    4. Re:Sync user names? by Sj0 · · Score: 1

      This has been happening a lot lately. At some point, Slashdot stopped being filled with Engineers, because everyone started to lose the concept of "The first step of design is determining user requirements"

      --
      It's been a long time.
    5. Re:Sync user names? by tepples · · Score: 1

      I fail to comprehend your attacking someone for sharing their personal practice if it isn't congruent for every contrived scenario you come up with that doesn't apply in his case.

      It wasn't intended as an attack. Nor is the scenario contrived; I've seen sets of requirements like the one I describe.

  31. Flash comes in =CLASSES= by redelm · · Score: 1

    Different grades of flash memory are available, visible to the consumer as the "Class" rating on SDHC cards (SD above 2 GB capacity). You can buy unrated, Class 2, 4, 6 and sometimes 8 MB/s nominal serial block write speed. These rating are very important for digital camera performance.

    Did you try any of the Classed SD cards in a fast USB adapter (not all are fast) to establish some watermarks for what class flash chips the labels are hiding?

  32. And this is news? by lpq · · Score: 1

    FAT32 has always been 2-5x faster than NTFS....its just that FAT32 limited you to 4GB file sizes...

    NTFS would put premature wear on a memory disk since it would uselessly keep a transaction log for file I/O's.

  33. Comment removed by account_deleted · · Score: 1

    Comment removed based on user account deletion