I don't fucking know why I can't eject USB hard drives. I installed the SysInternals apps, and best they can tell me is that Dropbox is fucking with the drives. I explicitly told Dropbox to not fuck with USB drives. I don't know who's lying, I just want whoever is fucking with the drives to stop fucking with the drives, OK??? OK.

(page 2) 50 comments

sorted by: hot top controversial new old

[–] Brkdncr@lemmy.world 6 points 1 month ago (2 children)

So unplug it? You would accomplish the same thing.

[–] balsoft@lemmy.ml 3 points 1 month ago (2 children)

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.

load more comments (2 replies)

load more comments (1 replies)

[–] marcos@lemmy.world 5 points 1 month ago

Dropbox is lying.

Windows may be lying too, but the only thing certain is that dropbox is lying.

[–] Object@sh.itjust.works 3 points 1 month ago* (last edited 1 month ago)

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.

[–] the_riviera_kid@lemmy.world 3 points 1 month ago

I just unplug it, consequences be dammned.

[–] rockettaco37@feddit.nu 3 points 1 month ago

This is Microsoft we're talking about here. 🤮

[–] Kolanaki@pawb.social 3 points 1 month ago* (last edited 1 month ago)

I don't even use that dumb shit. Unless it's still actively writing something, just take it out.

load more comments