I’m on the way of transfering to hard drive my cd/dvd/BD collection of divx and video.
I use 12.2 and Have two readers/writers, one SATA (in the box) and one BD (usb).
I can work with the two of them most of the time without problem.
However, sometime - that is once in a while for cd/dvd but half of the time for BD (Blu-Ray disks) the disk do not mount. dmesg gives some error message (VFS: busy inodes on changed media or resized disk sr0).
However I can use k3b to copy the disk to a hard drive image and then open this image, for example with fileroller and them extract the files from there. Sometime there is a corrupted file, but not always.
I beg why k3b is able to read, but dolphin is not? I use kde and the 12.2 is uptodate.
I can live with this, but this double the reading time.
ful error message is:
VFS: busy inodes on changed media or resized disk sr0
5451.727568] ISO 9660 Extensions: Microsoft Joliet Level 3
5451.728549] ISOFS: changing to secondary root
5959.640288] VFS: busy inodes on changed media or resized disk sr0
I know disks can sometime be read after water and soap cleaning and I use this. The problem I flag is not this kind.
I beg why k3b is able to read, but dolphin is not? I use kde and the 12.2 is uptodate.
IMHO because Dolphin does not work on devices, but on the directory tree (like most decent applications), that is on mounted file systems. k3b can work on devices (like /dev/sr0) and thus ignores if an eventual file system on the device is mounted or not (it is even not a must that there is a usable file system, e.g. as k3b burns on a fresh CD/DVD).
When I insert the disk, the kde applett pops up and the device name appears in dolphin tree, but the device is not yet mounted. It’s enough to clic on the device name on dolphin to mount it and read it in the default window. I know that something is wrong when the disk do not apprear in dolphin.
In k3b, there is a device list (left column, tree). A right clic on the device in this window shows options. Mount never works is lmy cases, but “load” somatime fix the problem, unloading the disk (opening the slot) and closing it again. The option “copy” works always (for now), and I simply copy it to an image file.
so all the mounting/umounting is managed by the system.
Partly this is a case of semantics. You do mount the file system by telling dolphin you want to use it.
But I am not talking about mounting, but about unmounting. Contrary to the actions at mounting, where you indicate you want to use it (in this case via Dolphin) and thus the system can take action, when you do not “tell” the system by any means that you want to stop using it, the system, being unable to read your brains, does not act and not unmount. You have to tell the sytem, by using the button in the applet. “Save removal” or something like that (even Windows has it). Simply removing the device, maybe even during a write action to it, can create all sorts of havoc, inclusing what you experience. It is like sawing the legs from under your table without taking any precautions to save what is on the table.
I understand what you say. I do not umount more than I mount. I open the reader. The applet (or the daemon underlying) acknoledge the order, umount the device and eject it (or at least do as if it did).
I have problem doing it through dolphin. I will experiment a bit more.
In Dolphin you right click on the device in the left column and there is also a “remove savely”. Use it and it will be unmounted properly (this can take some seconds because cache must be emptied).
Use a terminal and check every step with
mount]
or with some filtering to make easy reading
mount | grep media
ad you will see if the device is mounted at that moment in time.