Author Topic: Anything wrong with formatting a USB stick in NTFS? (Read 30020 times)

superboyac · « **on:** November 19, 2012, 12:36 PM »

All USB sticks come formatted as FAT. But FAT can't store large multi-gigabyte files. Does anyone see any problems with formatting a disk in NTFS? I can't come up with a reason not to...

tomos · « **Reply #1 on:** November 19, 2012, 12:50 PM »

I have no idea/opinion myself

but there's this:
http://serverfault.c...ld-be-formatted-ntfs

wraith808 · « **Reply #2 on:** November 19, 2012, 12:52 PM »

Nothing wrong with it- however there are some things that should be considered:
1. You have to make sure that you eject safely. The OS holds on to NTFS resources longer, and if you just remove it, the chances are high that you will corrupt data (write-caching).
2. There's also a lot more writing to the drive, which will reduce the life of the drive, and minimally reduce performance.
3. NTFS allows encryption- but be aware that if you do, you will not be able to open the files anywhere else.
4. There's also a space overhead for NTFS. How much varies by where you look for the information, but it seems to be about 4%.

No breaking changes- but they are some things to be aware of.

MerleOne · « **Reply #3 on:** November 19, 2012, 02:09 PM »

All USB sticks come formatted as FAT. But FAT can't store large multi-gigabyte files. Does anyone see any problems with formatting a disk in NTFS? I can't come up with a reason not to...
-superboyac (November 19, 2012, 12:36 PM)

you can always use an archiver like winrar that can split big files into chunks of 4GB max. And keep the FAT32 format.

f0dder · « **Reply #4 on:** November 19, 2012, 02:16 PM »

All USB sticks come formatted as FAT. But FAT can't store large multi-gigabyte files. Does anyone see any problems with formatting a disk in NTFS? I can't come up with a reason not to...
-superboyac (November 19, 2012, 12:36 PM)
you can always use an archiver like winrar that can split big files into chunks of 4GB max. And keep the FAT32 format.
-MerleOne (November 19, 2012, 02:09 PM)

(Obviously) not if you want to use the files directly, though - like large .WIM files for Windows installs, or HD .MKVs for playback on a media thingamajig

I've used NTFS-formatted pendrives for a while, and they work fine (as fine as those unrealiable POSs go, anyway). Only trouble I've run into is that NTFS is read-only on OSX, so you can't use it to get data from loose-wristed coworkers :-)

MerleOne · « **Reply #5 on:** November 19, 2012, 02:31 PM »

All USB sticks come formatted as FAT. But FAT can't store large multi-gigabyte files. Does anyone see any problems with formatting a disk in NTFS? I can't come up with a reason not to...
-superboyac (November 19, 2012, 12:36 PM)
you can always use an archiver like winrar that can split big files into chunks of 4GB max. And keep the FAT32 format.
-MerleOne (November 19, 2012, 02:09 PM)
(Obviously) not if you want to use the files directly, though - like large .WIM files for Windows installs, or HD .MKVs for playback on a media thingamajig

I've used NTFS-formatted pendrives for a while, and they work fine (as fine as those unrealiable POSs go, anyway). Only trouble I've run into is that NTFS is read-only on OSX, so you can't use it to get data from loose-wristed coworkers :-)
-f0dder (November 19, 2012, 02:16 PM)

Sure, but when clicking on the .rar file it will uncompress it to a temp folder and run it from there. Less efficient but it would still work - you still need winrar installed I think.

eleman · « **Reply #6 on:** November 19, 2012, 02:31 PM »

1. You have to make sure that you eject safely. The OS holds on to NTFS resources longer, and if you just remove it, the chances are high that you will corrupt data (write-caching).
-wraith808 (November 19, 2012, 12:52 PM)

Once you formatted the drive to use NTFS as file-system, you can revert to usual settings for flash drives and turn off write caching. That will minimize data corruption risks.

MilesAhead · « **Reply #7 on:** November 19, 2012, 02:33 PM »

If the device comes formatted as FAT32 my advice is to do a slow format when formatting to NTFS. I don't remember seeing it stipulated anywhere that it's required. But I've had USB that I changed from FAT32 and once it got past the point where I had written the drive in the past, in terms of disk space used, I started getting flaky behavior. They performed as expected after a slow format as NTFS.

Also to cut down on disk accesses with NTFS you can disable last access. I do that on all my systems. I don't use databases or backup robots that need that setting.

Just google "fsutil disable last access" for the command line.

f0dder · « **Reply #8 on:** November 19, 2012, 02:37 PM »

If the device comes formatted as FAT32 my advice is to do a slow format when formatting to NTFS. I don't remember seeing it stipulated anywhere that it's required. But I've had USB that I changed from FAT32 and once it got past the point where I had used the drive in the past, I started getting flaky behavior. They performed as expected after a slow format.
-MilesAhead (November 19, 2012, 02:33 PM)

Quick and normal formats do exactly the same amount of formatting - which is simply to initialize a relatively modest amount of sectors with a blank filesystem. The "slow" additionally does a read across the entire partition to check if it's readable, but it doesn't do any kind of write, repair or sector-reallocation triggering (at least for harddrives, sector reallocation only happens on write)... so it sounds weird that a "slow" format helped you. I'd attribute it to general pendrive flakyness

MilesAhead · « **Reply #9 on:** November 19, 2012, 02:47 PM »

I had a feeling you'd comment. All I can tell you is I've had problems with quick format both for bare drives and USB keys. Long format fixed it up. I don't really care why.

f0dder · « **Reply #10 on:** November 19, 2012, 02:53 PM »

Please don't subscribe to Cargo Cults

Doing a full format on new pendrives is a good idea anyway, as there's been more than one example of cheap Chinese brands that were labelled (and controller-configured) with a higher capacity than they actually have - which ends up giving you data corruption if you fill the drive beyond it's real capacity. (If controller simply does offset%realsize, a full format will not be enough to detect this malpractice, though - so it'd be even better to do a quickformat, fill the drive with data, and verify the data was written correctly).

MilesAhead · « **Reply #11 on:** November 19, 2012, 02:57 PM »

It's probably the ghost in the machine. This isn't just cheapie pen drives but WD Caviar Black Sata III bare drives in USB 3.0 docks. None of 'em like the quick format. Maybe it's just a conspiracy by Windows Seven to waste 2 of my hours. Or perhaps the drives weren't aware of your theoretical objections. In any case, just my experience. I realize the BMW convertible crowd may be able to do things the easy way. That's how it goes.

superboyac · « **Reply #12 on:** November 19, 2012, 03:11 PM »

lol

thanks guys, very helpful. I'll just leave it be for now.

f0dder · « **Reply #13 on:** November 19, 2012, 03:12 PM »

Did a little investigation, seems things have changed since does-format-write-zeroes was last brought up. So it actually does make sense that a non-quick format has helped you

XP and below, "full format" actually only does quick-format + sector verification... Vista and onwards, you get zero-overwrite (and reallocation triggering). Yay research ^_^

MilesAhead · « **Reply #14 on:** November 19, 2012, 04:38 PM »

Did a little investigation, seems things have changed since does-format-write-zeroes was last brought up. So it actually does make sense that a non-quick format has helped you

XP and below, "full format" actually only does quick-format + sector verification... Vista and onwards, you get zero-overwrite (and reallocation triggering). Yay research ^_^
-f0dder (November 19, 2012, 03:12 PM)

Glad you found that out. I had the "feeling" it was writing something all that time. But I wasn't certain. Probably with format to the same file type the quickie is fine. But changing to another file type it may be worth it to spend the time for the full shootin' match.

Daleus · « **Reply #15 on:** November 20, 2012, 06:40 AM »

I work in an environment that supports Macs as well as PCs. The Macs can read NTFS, but can't write to it (natively - you can install drivers or whatnot), but they *can* read and write Fat32.

So, all of my work USB sticks are formatted Fat32.

SeraphimLabs · « **Reply #16 on:** November 20, 2012, 04:54 PM »

All of my USB memory devices are formatted NTFS except where other devices like cameras do not support NTFS formatted memory.

The thing to do is go into the options for the device under device manager and disable caching. Although doing this causes a performance penalty, disabling caching makes it so that removing the device without first doing so in software is less likely to corrupt data.

MilesAhead · « **Reply #17 on:** November 20, 2012, 05:24 PM »

Sometimes Eject or Safely Remove does not want to function. Even though the stick will be shown as a removable drive, if you explicitly list the letter, Sync from SystemInternals should flush the data to disk.

I have USB 3.0 docks with caching enabled. I have sync.exe hooked to F10 function key. Before I'm going to shut off a dock, I hit F10 a few times to make sure the data is written. Sync works by simply locking the volume. This triggers Windows to write all data in file buffers to the drive. Couldn't be much safer. I've been using Sync.exe through many flavors of Windows.

By default just running sync.exe at a command prompt flushes all fixed disks. To use with a USB key that has write caching disabled, just specify the drive letter, like
sync F

without the ':'

The drives in my docks show as fixed disks. The fastest way to see if you have to specify the drive letter is just run sync.exe. It will report the letters of the drives flushed. If it shows your thumb, then no need to specify it.

It couldn't hurt.

wraith808 · « **Reply #18 on:** November 20, 2012, 06:07 PM »

^ I use Zentimo (used to be usb safely remove) for that.

MilesAhead · « **Reply #19 on:** November 20, 2012, 06:40 PM »

^ I use Zentimo (used to be usb safely remove) for that.
-wraith808 (November 20, 2012, 06:07 PM)

I got a free copy of Safely Remove. It was totally inconsistent on my machines. Basically a waste of time hitting the button.

Plus you don't want to "safely remove" hardware that is seen as a fixed drive, like the bare drives in my docks. Flush buffer kill power does it. Sync.exe works on everything, even Win9x. I've been using it since 9x days.

superboyac · « **Reply #20 on:** November 20, 2012, 07:12 PM »

^ I use Zentimo (used to be usb safely remove) for that.
-wraith808 (November 20, 2012, 06:07 PM)

I got a free copy of Safely Remove. It was totally inconsistent on my machines. Basically a waste of time hitting the button.

Plus you don't want to "safely remove" hardware that is seen as a fixed drive, like the bare drives in my docks. Flush buffer kill power does it. Sync.exe works on everything, even Win9x. I've been using it since 9x days.

-MilesAhead (November 20, 2012, 06:40 PM)

Really? What was inconsistent? I've been using it for a couple of years and have had no problems, but maybe I'm doing something dangerous? I've used it to eject usb drives and esata drives in docks.

MilesAhead · « **Reply #21 on:** November 20, 2012, 07:28 PM »

Inconsistent meaning I invoked it again and again and it almost never told me the drive could now be removed. I liked the eye candy. I wouldn't have stopped using it if it worked for me.

Like many things if it works for you it's great. If not it's a lemon.

SKA · « **Reply #22 on:** November 21, 2012, 04:28 AM »

I found USB Safely Remove to be much better (stable) than Zentimo on Vista Business 32-bit, Zentimo hangs with errors , but USBSR worked smoothly since last 2 years, on same flash drives/external drives(USB 2.0/3.0) .

Hard drives (2.5 or 3.5") in USB enclosures are far more reliable than flash/pen drives/"sticks", esp. if the former (external hard drives) have their own power supply(ac adapter etc)

My guess: All pendrives (even 16/32/64/128/256GB versions) are not so reliable as they rely on USB socket(2.0/3.0) for power,so a (heat) glitch in motherboard (whether desktop or laptop) could affect your data. So one is forced to have multiple devices for backup, of which I recommend at least one external powered drive.

exFAT file system(Microsoft): http://support.microsoft.com/kb/955704
-Supports volumes larger than 32 GB, Theoretical max volume size 64 ZB,
recommended max volume size is 512 TB.
-Supports files larger than 4 GB, Theoretical max file size 64 ZB, recommended max file size 512 TB.

some more links on exFAT:
http://www.lifehacke...xternal-drive-again/

http://www.mactalk.c...n-windows-7-mac.html

http://www.ehow.com/...tting-windows-7.html

http://en.wikipedia.org/wiki/ExFAT

http://www.sevenforu...27-exfat-format.html

http://www.sevenforu...usb-flash-drive.html

rgds
Ska

f0dder · « **Reply #23 on:** November 21, 2012, 08:06 AM »

The drives in my docks show as fixed disks.
-MilesAhead (November 20, 2012, 05:24 PM)

For an USB dock? What?!

I've seen that happen with eSata, but only if the BIOS hasn't configured the particular port used for hotswap... while you can do some hotswapping in that scenario, it's kinda flaky and dangerous. But if you're stuck with an old BIOS, you might not be able to toggle the port to hotswap mode

As for exFAT, I wouldn't use it unless for a specific device... devices that only support FAT don't support exFAT, so in that case you might as well use the (much) more robust NTFS.

MilesAhead · « **Reply #24 on:** November 21, 2012, 10:07 AM »

But if you're stuck with an old BIOS, you might not be able to toggle the port to hotswap mode

Write caching may be disabled. But since I'm running Sata III bare drives why would I want to take a performance hit? I have battery backup on the docks.