debian etch lxc shutdown tries to umount host filesystems

[RobFantini]

Hello

using this to start the lxc:

 lxc-start -n  3508  -F --logfile=3508.log --logpriority=debug

when the system is shutdown there are a lot of lines like this:

umount: /sys/fs/cgroup/cpuset: block devices not permitted on fs
umount2: Permission denied
umount: lxcfs: not found
umount: /sys/fs/cgroup/memory: block devices not permitted on fs
umount2: Permission denied
umount: lxcfs: not found
umount: /sys/fs/cgroup/memory: block devices not permitted on fs
umount2: Permission denied
umount: lxcfs: not found
umount: /sys/fs/cgroup/blkio: block devices not permitted on fs
umount2: Permission denied
umount: lxcfs: not found
umount: /sys/fs/cgroup/blkio: block devices not permitted on fs
umount2: Permission denied
umount: /dev/sdb1: not found
umount: /bkup: block devices not permitted on fs
umount2: Permission denied
umount: /dev/sdb1: not found
umount: /bkup: block devices not permitted on fs
failed.
mount: cannot mount block device /dev/loop2 read-only
Will now halt.

those all look like errors trying to unmount the pve hosts' filesystems.

here is the config file:

arch: i386
cpulimit: 2
cpuunits: 1024
hostname: sys3-pro4
memory: 1024
net0: name=eth0,hwaddr=66:11:0A:BE:AE:95,bridge=vmbr1,ip=10.1.7.198/24,gw=10.1.7.1,tag=7
onboot: 1
ostype: debian
rootfs: pve:3508/vm-3508-disk-1.raw,size=12G
swap: 1536
lxc.mount.entry: /pve/bkup  bkup  none bind 0 0

any clues on what setting I need to change in the container or config file?

 

[RobFantini]

Using the following mount method

mp0: /pve/bkup,mp=/bkup

had the same issue.

next I'll try without any lxc bind mount

and still got this:

Unmounting temporary filesystems...umount: /sys/fs/cgroup: device is busy
umount: /sys/fs/cgroup: device is busy
failed.
Deactivating swap...failed.
Unmounting local filesystems...umount2: Permission denied
umount: lxcfs: not found
umount: /sys/fs/cgroup/net_cls,net_prio: block devices not permitted on fs
umount2: Permission denied
umount: lxcfs: not found

sys3  /etc/pve/lxc # pveversion -v
proxmox-ve: 4.0-16 (running kernel: 4.2.2-1-pve)
pve-manager: 4.0-48 (running version: 4.0-48/0d8559d0)
pve-kernel-4.2.0-1-pve: 4.2.0-13
pve-kernel-4.2.1-1-pve: 4.2.1-14
pve-kernel-4.2.2-1-pve: 4.2.2-16
lvm2: 2.02.116-pve1
corosync-pve: 2.3.5-1
libqb0: 0.17.2-1
pve-cluster: 4.0-22
qemu-server: 4.0-30
pve-firmware: 1.1-7
libpve-common-perl: 4.0-30
libpve-access-control: 4.0-9
libpve-storage-perl: 4.0-26
pve-libspice-server1: 0.12.5-1
vncterm: 1.2-1
pve-qemu-kvm: 2.4-9
pve-container: 1.0-7
pve-firewall: 2.0-12
pve-ha-manager: 1.0-9
ksm-control-daemon: 1.2-1
glusterfs-client: 3.5.2-2+deb8u1
lxc-pve: 1.1.3-1
lxcfs: 0.9-pve2
cgmanager: 0.37-pve2
criu: 1.6.0-1
zfsutils: 0.6.5-pve4~jessie

 

[RobFantini]

solution :

from inside lxc:

rm -f /etc/rc0.d/*umount*  /etc/rc6.d/*umount*

need to check that the solution does not cause filesystem issues.