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.
How is linux handle such situations, i’m new using it and haven’t looked that up yet, well i didn’t got in such a situation yet, but i only used a handful of time a external hard drive
Basically, if you, as a regular user, cannot unmount a device, you can usually just go to root shell (
sudo -i), see where the thing is mounted (just usemount) and then unmount it (umount /media/blah/floop). If it says the device is still busy, as root you can remount it as read-only and then unmount it (seeking documentation left as an exericise to the reader, as I’m sitting at a Windows system now).There’s also
lsof(“list open files”) tool, which can be used to see which exact programs are using files on that device, which you can then use to kill those sneaky processes (ps,kill).So a complicated set of terminal commands and alternatives you need to have memorized ahead of time. That’s definitely the linux solution. You can do it, but no average user would ever be able to when they need it.
Windows probably has some equally complicated way of finding what is locking a file/folder… or you can just install File Locksmith which is a Microsoft PowerToys tool, and just have it in the context menu everywhere.
No average user would be able to look up what commands to run? Because newsflash: unlike Windows, searching for a common problem on Linux normally turns up a solution written by a human who knows what they’re talking about.
“Windows doesn’t even have basic package management like every Unix-like OS does so you don’t have to individually update applications and go find them on the Internet, but this one edge case on Linux requires like two terminal commands (the
sudo -iis totally superfluous if you just putsudoin front of commands) instead of installing an entire separate tool you’ll ever use one time like on Windows and which an average user wouldn’t even know exists. Therefore Linux is more complicated.”Incidentally, here’s what Microsoft officially recommends for the “average user” regarding PowerToys:
It’s insane how nose-blind Windows users are to how user-unfriendly their OS is.
Oh the irony. You clearly don’t work with any sort of end user.
For 99% of computer users, if the GUI doesn’t have an option, it doesn’t exist. They aren’t searching past a basic Google of the issue showing them step by step instructions of how to use the GUI to fix the problem. If there is no way to do so in the GUI, it’s not getting fixed by them, they’ll take it to the Geek Squad if they even decide to fix it at all. They’re must more likely to just ignore an issue. In this case, just removing the USB drive and complaining about something being corrupt later on. The idea of the terminal scares the average person.
Literally 99% of Windows tech support is
That’s the difference with Linux. Your average user never uses terminal, and when they do, they find the tools suck.
Your users are searching for their problems???
Most wouldn’t even do that.
If the button isn’t right there to fix everything automatically, the problem just stays that way until they (maybe) restart
Alright, so others went over the “easy” way to see which program is being the offender. But I feel like the average Lemmy user just skips GUI at this point.
Say hello to KDE:
KDE also does automatic fsck before mounting, which is why it may take some 2 seconds to mount a drive.
HDDs it properly spins down and unpowers as well.
The best part is that Geek Squad probably won’t even fix it.
With the amount of time allocated to tasks and the lack of autonomy retail workers are given, the solution to anything not explicitly written in an employee runbook is going to be “we need to reinstall windows” or “it can’t be fixed, but we have a new computer you can buy”
Just sudo umount /mnt -l that mf
Well, the commands that I presented (
sudo,mount,umount,ps,kill, evenlsof) are actually just normal commands that you use to do ordinary things on your system to manage account elevation, mounted disk volumes, processes, and running processes. You need to “memorise” them just as much as you need to memorise their counterparts in a Windows system (Run As/Explorer/Explorer Eject/taskmgr) (…what kind of nerd memorises Ctrl+Alt+Esc anyway?).…except you don’t have
lsof, you literally need to install SysInternals Process Explorer.Hi, I am that nerd, it’s Ctrl+Shift+Esc to open taskmgr, actually.
…I hope to be able to develop a similar level of nerd when I switch to Linux soon
I found learning Linux much more fun, because I didn’t have to fight with the computer on every damned thing.
You can also just pull the USB drive out, if you have waited a reasonable time after last writing to it, no harm will be done.
Also, terminal commands have the advantage that they are the same over the course of 20something years and across all desktop environments, while the tinyfloppy windows moves critical functions around with every second patch so you have to relocate stuff you had just memorized.
As a point of contrast. In Linux Mint you press the eject button. That’s it.
The other guy was getting into more detail for people who want it.
And the same works 99% of the time in Windows. We’re talking about the small fraction where pressing eject doesn’t work for whatever reason.
I don’t think an average user is going to know how to interpret the output of
mountorfindmtsound a lot better than on windows, at least for power user.
Linux Mint has an eject button that allows any cached writes* to finish, prevents new ones from starting, and un-mounts it. It’s actually important to use the eject button as flash drives are slow, and the write cache can obscure the fact that a file isn’t done writing yet.
*Copying a file will add it into the write cache while it writes out to the disk. As soon as it is in the cache, you can use the file as if it was already done copying, including making changes.
Idk how Linux handles it but today on Mac I accidentally sent a folder to trash that was in use by four programs at once.
Mac OS did not give a shit. It nuked it.
Macintosh Killed My Inner Child
Real answer: it depends.
lsofcan tell you which process has which files open. There’s nuance with lazy unmounts and whatnot but that should not be used in most cases.Now in practice you should be wary of one very important thing that changes compared to Windows: Writes are asynchronous on Linux. First the kernel writes to RAM, then it flushes to disk at a later time for performance reasons (this is one of the reasons why writing a bunch of small files is many times faster on Linux than Windows). The upshot is that just because your file copy is “done” doesn’t mean you can just yank the USB cable. Always safely unmount before unplugging a storage device on Linux.
Unless I mount it with
sync, which I wish would be default for non-system drives (which are going to be in fstab anyway). I didn’t notice any difference, aside from the lack of guessing when the magic is over. 2GiB goes into black hole, now what?You can also use the
synccommand to flush cached writes and wait for completion, but I agree that it is a bit cumbersome.Strongly disagreed. A lot of removable storage benefits very strongly from async writes. The performance benefits are night-and-day and worth the hassle of explicitly unmounting.
I think a better compromise would be to mount non-journaled + removable storage (e.g. vfat USB keys) as sync.
Many files copied to an external disk are cached, and not written immediately unless you run the “sync” command.
So when you press the “eject” icon, on most frontends a notification will tell you not to unplug it right away, once the write is complete it will send a “it is safe to remove the drive” message. This can take a couple minutes if you are writing a big file to a slow drive.
By default Windows disables file caching on external USB drives. It should be writing those files directly. That doesn’t prevent a program from locking a file or folder that it is using though.
I basically never have this problem on Linux.
I think programs can’t hold removable media busy by default on Debian. If you remove, you lose whatever changes aren’t there. Either way, Linux programs just read files and close them, they mostly don’t keep files open.