814
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 31 Oct 2025
814 points (98.3% liked)
Programmer Humor
28360 readers
846 users here now
Welcome to Programmer Humor!
This is a place where you can post jokes, memes, humor, etc. related to programming!
For sharing awful code theres also Programming Horror.
Rules
- Keep content in english
- No advertisements
- Posts must be related to programming or programmer topics
founded 2 years ago
MODERATORS
So unplug it? You would accomplish the same thing.
I'm not too versed in the intricacies of Windows, but I don't think that's the case on Linux at least.
There's a difference between telling the processes to "fuck off" (by using
umount -f) and actually yanking the drive.umount -fwill at least flush the caches to drive, including all filesystem metadata and journaling, while just yanking the drive off will definitely not, and if you're unlucky you can ruin the FS (especially if it's not a journaling one). I've lost data like that before, been usingumount -fever since.OP has done the same. A file is in use/locked by an app even after the have issued an unmount/eject command. The file that’s in use may not survive.
Yes, but at least the rest of the filesystem will
Which is exactly what I do if sufficiently annoyed! Problem is, Windows is usually hella vague about which particular devices have Quick Removal™®© enabled.