Hi Marcy, Thanks. Good to know I'm not the only one. :-)
Met vriendelijke groet/With kind regards/Mit freundlichen Grüßen, Berry van Sleeuwen -----Original Message----- From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Marcy Cortes Sent: Wednesday, December 14, 2016 8:54 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: systemd Failed unmounting /usr I'm seeing this stuff too on SP2. I don't see it on an SP1 server Sounds like we need to report it. May have something to do with LVM on those file systems. -----Original Message----- From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of van Sleeuwen, Berry Sent: Wednesday, December 14, 2016 7:32 AM To: LINUX-390@VM.MARIST.EDU Subject: [LINUX-390] systemd Failed unmounting /usr Hi All, I have installed a new SLES12 SP2 guest. The root partition is on one partition (/dev/dasda1). The remaining system directories are stored within an lvm, rootvg. This lvm contains logical volumes for /usr, /opt, /home, /tmp and /var. During boot, when systemd is started it tries to umount /usr. After a couple of tries umount ends. But I did have one occasion where the umount apparently succeeded as the guest came up in emergency mode, without /usr mounted. 2016-12-14T15:54:41.052380+01:00 SLES12 systemd[1]: systemd 228 running in system mode. (+PAM -AUDIT +SELINUX -IMA +APPARMOR -SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT -GNUTLS +ACL +XZ -LZ4 +SECCOMP +BLKID -ELFUTILS +KMOD -IDN) 2016-12-14T15:54:41.052387+01:00 SLES12 systemd[1]: Detected virtualization zvm. 2016-12-14T15:54:41.052389+01:00 SLES12 systemd[1]: Detected architecture s390x. 2016-12-14T15:54:41.052391+01:00 SLES12 systemd[1]: Set hostname to <SLES12>. 2016-12-14T15:54:41.052394+01:00 SLES12 systemd[1]: nss-lookup.target: Dependency Before=nss-lookup.target dropped 2016-12-14T15:54:41.052396+01:00 SLES12 systemd-modules-load[784]: Inserted module 'ecryptfs' 2016-12-14T15:54:41.052398+01:00 SLES12 umount[774]: umount: /usr: target is busy 2016-12-14T15:54:41.052401+01:00 SLES12 umount[774]: (In some cases useful info about processes that 2016-12-14T15:54:41.052403+01:00 SLES12 umount[774]: use the device is found by lsof(8) or fuser(1).) … <snip> … 2016-12-14T15:54:41.052446+01:00 SLES12 umount[836]: umount: /usr: target is busy 2016-12-14T15:54:41.052448+01:00 SLES12 umount[836]: (In some cases useful info about processes that 2016-12-14T15:54:41.052450+01:00 SLES12 umount[836]: use the device is found by lsof(8) or fuser(1).) 2016-12-14T15:54:41.052453+01:00 SLES12 systemd[1]: usr.mount: Mount process exited, code=exited status=32 2016-12-14T15:54:41.052462+01:00 SLES12 systemd[1]: Failed unmounting /usr. 2016-12-14T15:54:41.052464+01:00 SLES12 systemd[1]: usr.mount: Unit is bound to inactive unit dev-mapper-rootvg\x2dusrlv.device. Stopping, too. 2016-12-14T15:54:41.052466+01:00 SLES12 systemd[1]: Unmounting /usr... … <snip> … 2016-12-14T15:54:41.052625+01:00 SLES12 systemd-udevd[855]: Network interface NamePolicy= disabled by default. 2016-12-14T15:54:41.052628+01:00 SLES12 umount[864]: umount: /usr: target is busy 2016-12-14T15:54:41.052630+01:00 SLES12 umount[864]: (In some cases useful info about processes that 2016-12-14T15:54:41.052632+01:00 SLES12 umount[864]: use the device is found by lsof(8) or fuser(1).) 2016-12-14T15:54:41.052634+01:00 SLES12 systemd[1]: usr.mount: Mount process exited, code=exited status=32 2016-12-14T15:54:41.052636+01:00 SLES12 systemd[1]: Failed unmounting /usr. 2016-12-14T15:54:41.052638+01:00 SLES12 systemd[1]: usr.mount: Unit is bound to inactive unit dev-mapper-rootvg\x2dusrlv.device, but not stopping since we tried this too often recently. 2016-12-14T15:54:41.052640+01:00 SLES12 systemd[1]: Stopped File System Check on /dev/rootvg/usrlv. 2016-12-14T15:54:41.052643+01:00 SLES12 systemd[1]: Reached target Local File Systems (Pre). … Boot continues with starting services etc. Why does the startup produce these errors? And how can it be resolved? Met vriendelijke groet/With kind regards/Mit freundlichen Grüßen, Berry van Sleeuwen Flight Forum 3000 5657 EW Eindhoven • +31 (0)6 22564276 [cid:image001.jpg@01CE3508.E10AE080] [cid:image002.jpg@01CE3508.E10AE080] This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, Atos’ liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted. On all offers and agreements under which Atos Nederland B.V. supplies goods and/or services of whatever nature, the Terms of Delivery from Atos Nederland B.V. exclusively apply. The Terms of Delivery shall be promptly submitted to you on your request. This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, Atos’ liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted. On all offers and agreements under which Atos Nederland B.V. supplies goods and/or services of whatever nature, the Terms of Delivery from Atos Nederland B.V. exclusively apply. The Terms of Delivery shall be promptly submitted to you on your request.
