![]() ![]() Thus far, it mastered every flash drive I tried. I think Microsoft should no longer sell Windows on DVDs and instead offer USB setup sticks and bare metal cloud installations.Īnyway, I played with the free Rufus alternative to the Windows 7 USB tool, and it appears to be more reliable. People expect that they can just use a product when they paid for it without the need to fiddle around with diskpart. □ I believe forcing end users to download an unreliable tool to create install media is an anachronism. So you see what a Microsoft fan boy I am. ![]() I suppose the majority of customers would just have returned the Windows 8 DVD and bought an iPa(i)d or Android tablet instead. They didn’t know how to do that and I ended up doing it myself in the shop. Since the Windows 8 package only came with a DVD and I didn’t bring a DVD drive, I had to go back to the shop and ask them to create a USB boot stick for me. It appears that, depending on the country, the license key and the Windows 8 setup have to fit together. When I tried to install the OS with my USB stick, the setup complained that the license key doesn’t work. I recently bought Windows 8 in the Philippines. I’d like to take this opportunity to add one more annoyance that might be a bit off topic because I am supposed to review Rufus here. If you run into problems even before you can create the installation media, then then you are likely somewhat prejudiced against a new operating system that was made for tablet PCs and Ultrabooks for which a setup DVD is relatively useless. I happily went back to Ntfs, there will be no Refs for me for the next years until this product is really reliable.Considering that more and more PCs no longer feature DVD drives, this could be a major reason why Windows 8 user satisfaction is not always as high as Microsoft hopes. At the end it has worked and I got my data back but this was not exactly the experience that I had expected from a freshly built state of the art new file system that was advertised as resilient and especially suitable for large amounts of data. Not only did it cost me a new 8 TB drive as I had no spare of such a size, the fullscan also took like a week. So I had to follow Microsofts idea: The only solution was to buy a new drive, minimum the size of the one I needed to recover and perform a fullscan and copy all data found over to the new one. Microsoft only offered a tiny CLI tool, 3rd party tools like Testdisk did not exist. ![]() Where there are ways to recover a raw disk with Ntfs with ReFS there was no easy solution. Then one day BANG HDD went into RAW mode shortly after I had consolidated Terabytes onto it and retired the old drives. It happened to me too: It was running like a charm at the beginning and I could not believe the warnings I had read on the internet. They started it with lots of enthusiasm but didn’t think it to the end and finally built a useless product. But if you are facing huge latency spike on a > 10TB volume on Windows Server it might be the solution for you. PS: It is just my experience I am not saying that ReFS is better than NTFS for every Windows node. Listing the files on the volume is quite fast now.Node startup have the data volume at 60% for 3-4 minutes compare to 100% for more than 30 min before.I migrated my 11TB volume to a new ReFS 4KB partition (took some time for the copy but the node downtime was only 20 min) and it is the night and day: ReFS have his pro and cons but it there is something that I does much better than NTFS is dealing with huge numbers of files, NTFS usually keep getting slower and slower the more file you add (talking about millions of files here) Try to migrate the volume to ReFS 4KB.However, I would lose a little bit of space, as the average file size is not very huge. Try to migrate the volume to a NTFS 64KB cluster to try to reduce the MFT file and limit fragmentation.I tried defragmenting the volume but it was taking ages and did not seem to solve anything. Listing the files on the volume was very slow and I started suspecting defragmentation or files count problems. The average latency was way above 300ms even when the activity was very low.The drive activity was constantly around 80-100%.The file system used for the data drive was NTFS with 4KB clusters.Moving the database files to SSD reduced the problems but did not solve it completely. I noticed huge latency on the volume hosting the data’s since the volume reached around 4-5TB and it keep getting worse as the volume increased. It has been growing since the past year and it is now around 11TB with 7.8 million files with an average size of 1.4MB. A little bit of background first, my node is running under Windows Server 2019 with the native windows service version. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |