Windows 10: NTFS - time for Ms to create new file system ?

Hi there

I posted recently about how slow NTFS was when you were copying large amounts of data - especially if the data consisted essentially of zillions of small files.

Here's a reliable test which amply demonstrates that it really is time for Ms to at least consider re-writing the NTFS file system - especially as more and more of even HOME users have increasing amounts of data. The problem isn't per se in the maximum capacity of the file system but the way the I/O is performed.

Here's a brief image





For those interested the article is here

Linux 4.0 Hard Drive Comparison With EXT4 / Btrfs / XFS / NTFS / NILFS2 / ReiserFS - Phoronix

Cheers
jimbo

:)

 

How to install ovi suite to D drive?

Does your operating system support NTFS junction points or NTFS symbolic links?

NTFS junction point - Wikipedia



If it does, then you can create D:\programs\nokia

Then move all files under C:\program files\nokia to D:\programs\nokia

Then under C:\program files create NTFS junction point (or symbolic link).

This NTFS junction point should be called Nokia and point to new folder D:\programs\nokia

Remember to follow the advice in the wiki link regarding protecting junction points using NTFS ACLs.



Once the new folder and NTFS junction point is created, when you install software to C:\program files\nokia the files get written to D:\programs\nokia

 

Stopcode Loop NTFS FILE SYSTEM to FAT FILE SYSTEM

My laptop is stuck in a loop on startup, I get the stopcode NTFS SILE SYSTEM it then starts an automactic repair and restarts but then gets stopcode FAT FILE SYSTEM again it starts an auto repair and restsarts but gets the NTFS stopcode again. I have
used themedia creation tool to create a USB drive and adjusted the BIOS to use the USB but it is till running into the same loop.

 

I wonder, if it has something to do with linux itself, according to other test, 10 performs better than previous Windows.

Flexense - Data Management Software - Windows 10 Disk Performance Review

 

Hi there
that could be true - however most people seem to think that NTFS isn't a particularly efficient file system anyway. Ms were working on a newer system --they use some type of new file system when you use Pooled volumes (use a group of volumes as a Single storage space). That could be an avenue for Ms to persue.

Cheers
jimbo

 

You never let me down Jimbo... Always first to demand that Microsoft do something they have already done.

ReFS - Wikipedia, the free encyclopedia

 

Hi,

ReFS is still not implemented in consumer systems as far as I know.

NTFS is slow because it emphasizes security and data integrity.
Any way you turn it, it all comes down on what you want to compromise really.

Add a myriad of small files to be copied (meaning opening and closing every single one of them) and Windows wanting to check every file viruses and god knows what plus the fact that actions such as copying, moving and other file actions aren't high on the priority list, you inevitably end up with a long waiting time.
A time depending on your CPU, chipset, whatever.

All in all I find copying/moving file I W10 slow. I.e. way below what the hardware is capable of. it would be nice if we or W10 could set the priority of the file handling task to high when nothing else is running or demanding priority.

Cheers, *Wink

 

There was talk of Windows getting ReFS years ago but nothings happened.

 

ReFS is built into Windows 8.x and up. It's used by StorageSpaces for instance, but can also be enabled for normal drive usage, though it cannot be a boot volume.

How You Can Try the New Resilient File System for Windows

Having said that, ReFS will probably take 10 years before it's ready to replace NTFS, just like NTFS took a number of years before it replaced FAT(32).

ReFS does not perform well (yet) on every condition, and in at least one case (sequential writes) it can be very slow. But I imagine that will change over time.

SQL Server and ReFS: Part 2 FIO Benchmarking NTFS vs. ReFS | Exchange Spill

I was really just commenting that Microsoft was already doing what Jimbo was suggesting. It doesn't mean it's ready to be used as a primary filesystem yet, but it's being done.

 

Hi there

I'm willing to have a go with this on a test system -- note using this on a VM isn't actually a good test since VM itself will use its own I/O (from the HOST system) to perform Disk transfers. (Assuming that they use something like VBOX or VMWARE VM software).

I'll see if I can test this out on a REAL machine with a whole slew of small files (the most difficult for efficient and fast data transfer).

As to File / Data Integrity --I haven't ever lost data with Linux EXT3/EXT4 or XFS - journalling system usually keeps file system pretty safe -- of course if Hardware goes defective that's another issue). I haven't lost data either with NTFS or even FAT32 so I don't think data integrity of the basic file system is a problem.

A good thing with Linux file systems though is you don't need things like GPT or MBR -- the GPT system always creates a small "Microsoft reserved partition " - when you mount a GPT disk in Linux it always shows for example as /dev/sdd and /dev/sdd1 where /dev/sdd1 is the data partition and /dev/sdd shows up as something like a 500 MB "Microsoft reserved basic partition". With things like EXT4 / XFS you can create a single partition file system (mkfs.xfs /dev/sdd -f) which creates a file system on the entire HDD no matter what the size is.

Of course Ms need to support legacy file systems but it's time now to get really efficient file I/O as HDD's become HUGE - and faster. !! SSD's while great aren't going to replace spinners for large data capacities just yet --especially when for example you can get fast 5TB 7200 RPM HDD's with 128 MB Cache for around 110 EUR / 120 USD a pop. !!!

Cheers
jimbo

 

I've been using ReFS on my Windows 10 box for over 6 months now and have had no problems. I set it up using Storage Spaces, and it uses two 5TB WD Blacks as a mirror. My decision to use this was I want to run Windows software, but wanted ultimate redundancy. I've heard of files going bad silently due to bad blocks and such. ZFS is supposed to prevent this, but it is next to impossible to find Skylake motherboards that support ECC memory (a ZFS requirement). I can run a HD Tune on it if anyone wants the stats.