Dropbox is lying.
Windows may be lying too, but the only thing certain is that dropbox is lying.
Dropbox is lying.
Windows may be lying too, but the only thing certain is that dropbox is lying.
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 -f will 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 using umount -f ever since.
Which is exactly what I do if sufficiently annoyed! Problem is, Windows is usually hella vague about which particular devices have Quick Removal™®© enabled.
This is Microsoft we're talking about here. 🤮
I don't even use that dumb shit. Unless it's still actively writing something, just take it out.
I just unplug it, consequences be dammned.
I haven't come across a single program that tells you what is blocking the ejection even in Linux. Sure, if you use the right tools you can find the culprit, but the program that does the ejection task seems to love being vague.
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.