Created attachment 1458905 [details] 'fuser' outputs (stdout and manual) Description of problem: With no extra services added to the system, the mounted point /home does not allow to be unmounted. Version-Release number of component (May not be related to component against it is reported): util-linux.x86_64 2.32-2.fc28 Actual results: # umount /home umount: /home: target is busy. Expected results: not to have by default some blocking processes. Additional info: Since 'sudo -' is a non-adequate command in releases from version 28 and above of Fedora, commands 'sudo -i' or 'sudo su' may be used in order to act as root. # w 18:38:59 up 1 min, 1 user, load average: 3,43, 1,50, 0,56 USER TTY LOGIN@ IDLE JCPU PCPU WHAT yk tty1 18:37 1:36 28.06s 8.27s /usr/bin/gnome-software --gappl # LANG=C who -a system boot Jul 14 11:11 yk ? :0 Jul 14 11:12 ? 1006 (:0) run-level 5 Jul 14 11:13 $ lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:0 0 232,9G 0 disk ├─sda1 8:1 0 1G 0 part /boot └─sda2 8:2 0 231,9G 0 part ├─fedora-root 253:0 0 150G 0 lvm / ├─fedora-swap 253:1 0 3,9G 0 lvm [SWAP] └─fedora-home 253:2 0 78G 0 lvm /home $ LANG=C df -hTt ext4 Filesystem Type Size Used Avail Use% Mounted on /dev/mapper/fedora-root ext4 147G 23G 117G 17% / /dev/sda1 ext4 976M 222M 687M 25% /boot /dev/mapper/fedora-home ext4 77G 5.8G 67G 8% /home Since output resulting from command 'fuser -mv /dev/mapper/fedora-home | wc -l' was incorrect, here is the output as attachment according to: $ LANG=C fuser -mv /dev/mapper/fedora-home >fuser_output The collected output for an unknown reason, figured only the PIDs, so I added to ir the whole output (Copied Pasted).
Sorry, I've lost in your report. It seems you have log-in non-root user, this user has executed many services (according to fuser). Why do you expect that /home is unused?
Case 1 – Outputs in which are involved users logged as 'sudo su' and''su root' are identical: $ sudo su # pwd /home/yk # whoami root # w 16:26:50 up 6:41, 1 user, load average: 0,20, 0,17, 0,17 USER TTY LOGIN@ IDLE JCPU PCPU WHAT yk :0 09:45 ?xdm? 1:29 0.03s /usr/libexec/gdm-x-session --ru Case 2 – Outputs in which are involved users logged as 'sudo -i' and''su -' are identical_ $ sudo -i # pwd /root # whoami root # w 15:50:31 up 6:05, 1 user, load average: 0,13, 0,18, 0,30 USER TTY LOGIN@ IDLE JCPU PCPU WHAT yk :0 09:45 ?xdm? 1:21 0.03s /usr/libexec/gdm-x-session --ru In both cases 1 and 2, outputs regarding the user, resulting respectively from commands 'whoami' and 'w' are not identical; Shouldn't then the output from 'w' to be the one from 'whoami'? I may have interpreted incorrectly my readings: an LVM /home partition aimed to be resized to smaller, does not require to be handled at system boot by relying on a –presumed– Fedora rescue mode.
but "sudo" as well as "su" means that the original user's session is still active. If you want to umount /home you have to completely logout the user and login as root (for example on standard console), then the /home will be unused.
It could not be an issue; At last when I interpreted 'standard' as 'virtual' I was able to apply a solution. I did not expect that even from a user's session manager – here for instance, GDM – switching to virtual consoles was possible.