What gets me is when I’m not allowed to remove an external drive. Deleting a file can be delayed until later but here I am with a physical object that I need to detach from my computer and first I need to play hide and seek with the OS.
If this happens often, you can disable write caching for that drive. It’ll feel slightly slower (since it’s actually operating at the speed of the hardware instead of caching operations in RAM and gradually writing them to disk in the background), but you’ll be able to remove the drive almost instantly.
I was having terrible performance problems in Windows a while back, and it turned out it had marked every drive as removable, and the write cache was filling up due to an extremely slow external HDD, causing even the internal SSDs to grind to a halt until the buffer was flushed whenever a large amounts of writes were made to the HDD (which was often, since it was used for backups and large Steam games).
I used to find it had something to do with the explorer thumbnailer finishing up but sort of not letting go. It would happen if I had pictures or videos on the USB drive, and if I got the error I could go to another folder like my documents, drag a picture into another folder, go look at the pretty new thumbnail, then I could remove the USB drive because the thumbnailer was ‘parked’ back on the C drive. Sounds like I’m making it up but I swear it worked.
And that removable object’s filesystem is probably the most shit, unjournalled filesystem in the world so you’re actually fucked if it becomes corrupted by removing it early.
And if you move the drive between operating systems you’re very limited in what filesystems you can use because Windows is very limited in what filesystems it can use. So you can’t just pick a more robust filesystem.
What gets me is when I’m not allowed to remove an external drive. Deleting a file can be delayed until later but here I am with a physical object that I need to detach from my computer and first I need to play hide and seek with the OS.
If this happens often, you can disable write caching for that drive. It’ll feel slightly slower (since it’s actually operating at the speed of the hardware instead of caching operations in RAM and gradually writing them to disk in the background), but you’ll be able to remove the drive almost instantly.
Shouldn’t that happen automatically if the drive is identified as removable? And the real solution should be to tell the OS that it’s removable?
I was having terrible performance problems in Windows a while back, and it turned out it had marked every drive as removable, and the write cache was filling up due to an extremely slow external HDD, causing even the internal SSDs to grind to a halt until the buffer was flushed whenever a large amounts of writes were made to the HDD (which was often, since it was used for backups and large Steam games).
I used to find it had something to do with the explorer thumbnailer finishing up but sort of not letting go. It would happen if I had pictures or videos on the USB drive, and if I got the error I could go to another folder like my documents, drag a picture into another folder, go look at the pretty new thumbnail, then I could remove the USB drive because the thumbnailer was ‘parked’ back on the C drive. Sounds like I’m making it up but I swear it worked.
And that removable object’s filesystem is probably the most shit, unjournalled filesystem in the world so you’re actually fucked if it becomes corrupted by removing it early.
And if you move the drive between operating systems you’re very limited in what filesystems you can use because Windows is very limited in what filesystems it can use. So you can’t just pick a more robust filesystem.
Yeah that was kind of my point.
You can use this performance view thing that comes with windows to search for file handles and the processes that own them