[opensuse] why is my LVM-disk busy when shutting down?
Hi, hope all of you have started a great year! When I shut down my computer (using the kde button or entering "shutdown -h now", doesn't matter) at the end of all the shutdown messages appears the following: Command failed device-mapper: remove ioctl on diska-disk1sys failed: Device or resource busy Command failed device-mapper: remove ioctl on ata-WDC_WD20EARS-00MVWB0_WD-WMAZA2401793-part3 failed: Device or resource busy These messages repeat numerous times and run quickly over the screen (I took a photo to read it...), finally after a quite short while the computer shuts down normally. This is my disk-layout:
daniel@venus:~> lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:0 0 1.8T 0 disk ├─sda1 8:1 0 297M 0 part /boot/efi ├─sda2 8:2 0 1G 0 part /boot └─sda3 8:3 0 1.8T 0 part └─cr_ata-WDC_WD20EARS-00MVWB0_WD-WMAZA2401793-part3 254:0 0 1.8T 0 crypt ├─diska-disk1sys 254:1 0 200G 0 lvm / ├─diska-system 254:2 0 4G 0 lvm [SWAP] └─diska-disk1hme 254:5 0 1.6T 0 lvm /home sdb 8:16 0 1.8T 0 disk └─sdb1 8:17 0 1.8T 0 part └─cr_ata-WDC_WD2002FAEX-007BA0_WD-WCAY01001843-part1 254:3 0 1.8T 0 crypt └─diskb-disk2 254:4 0 1.8T 0 lvm /home/daniel/disk2 sr0 11:0 1 1024M 0 rom
the cr_ata_... are both encrypted LVM's all logical volumes except swap are formatted with ext4 So something in the root files is "busy", but why? And how can I find out what is busy? (I only shut down my computer after a new kernel update, so it's not often that I see this, but now I thought it's the moment to ask :-) ) Thanks for hints! Daniel -- Daniel Bauer photographer Basel Barcelona https://www.patreon.com/danielbauer http://www.daniel-bauer.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Uuu, I see my copy from console had no line breaks, so for better reading I inserted them, hope it's better readable...
daniel@venus:~> lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 1.8T 0 disk
├─sda1 8:1 0 297M 0 part /boot/efi
├─sda2 8:2 0 1G 0 part /boot
└─sda3 8:3 0 1.8T 0 part
└─cr_ata-WDC_WD20EARS-00MVWB0_WD-WMAZA2401793-part3 254:0 0 1.8T 0 crypt
├─diska-disk1sys 254:1 0 200G 0 lvm /
├─diska-system 254:2 0 4G 0 lvm [SWAP]
└─diska-disk1hme 254:5 0 1.6T 0 lvm /home
sdb 8:16 0 1.8T 0 disk
└─sdb1 8:17 0 1.8T 0 part
└─cr_ata-WDC_WD2002FAEX-007BA0_WD-WCAY01001843-part1 254:3 0 1.8T 0 crypt
└─diskb-disk2 254:4 0 1.8T 0 lvm /home/daniel/disk2
sr0 11:0 1 1024M 0 rom
-- Daniel Bauer photographer Basel Barcelona https://www.patreon.com/danielbauer http://www.daniel-bauer.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
04.01.2018 14:53, Daniel Bauer пишет:
So something in the root files is "busy", but why?
That must be a joke. Root is always busy by virtue of being root. You cannot remove mounted device and root is always mounted nor can you unmount root because there is always at least /sbin/init which holds it busy. The only way to cleanly tear down storage stack used for root mount is to jump back into RAM disk (opposite of what usually happens on boot) and unmount "real" root filesystem that now becomes free. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Am 04.01.2018 um 13:17 schrieb Andrei Borzenkov:
04.01.2018 14:53, Daniel Bauer пишет:
So something in the root files is "busy", but why?
That must be a joke. Root is always busy by virtue of being root. You cannot remove mounted device and root is always mounted nor can you unmount root because there is always at least /sbin/init which holds it busy. The only way to cleanly tear down storage stack used for root mount is to jump back into RAM disk (opposite of what usually happens on boot) and unmount "real" root filesystem that now becomes free.
So you think my system is joking on me? Then at least I'd expect it to put some smileys in the messages :-) I don't know the technical details how a shutdown works, but somewhere to the end for sure all disks, also root, must be unmounted, I think. So what is not working here? How can I find out? -- Daniel Bauer photographer Basel Barcelona https://www.patreon.com/danielbauer http://www.daniel-bauer.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
04.01.2018 16:23, Daniel Bauer пишет:
Am 04.01.2018 um 13:17 schrieb Andrei Borzenkov:
04.01.2018 14:53, Daniel Bauer пишет:
So something in the root files is "busy", but why?
That must be a joke. Root is always busy by virtue of being root. You cannot remove mounted device and root is always mounted nor can you unmount root because there is always at least /sbin/init which holds it busy. The only way to cleanly tear down storage stack used for root mount is to jump back into RAM disk (opposite of what usually happens on boot) and unmount "real" root filesystem that now becomes free.
So you think my system is joking on me? Then at least I'd expect it to put some smileys in the messages :-)
No, I thought you were joking.
I don't know the technical details how a shutdown works, but somewhere to the end for sure all disks, also root, must be unmounted, I think.
No. At most root is remounted read-only. As I mentioned, there are technical prerequisites to actually unmount root but I am not aware of any actual implementation at lest in widely used Linux distributions.
So what is not working here? How can I find out?
Everything is working as it should. You can ignore this message as long as it only refers to root LV. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (2)
-
Andrei Borzenkov -
Daniel Bauer