FS#28110 - [initscripts] shutdown hangs on Unmounting Swap-backed filesystems
Attached to Project:
Arch Linux
Opened by Heinrich Siebmanns (Harvey) - Thursday, 26 January 2012, 10:18 GMT
Last edited by Eric Belanger (Snowman) - Friday, 16 November 2012, 17:57 GMT
Opened by Heinrich Siebmanns (Harvey) - Thursday, 26 January 2012, 10:18 GMT
Last edited by Eric Belanger (Snowman) - Friday, 16 November 2012, 17:57 GMT
|
Details
Description:
I use a central storage for my pacman packages on my home server. It is distibuted via NFS4. When doing 'pacman -Syu' I mount this share to /var/cache/pacman/pkg by executing 'mount server:/srv/pacman/cache/x86_64 /var/cache/pacman/pkg/' I use the same scenario for i686-boxes (of course with another share for this architecture) and it's all the same there. If I forget to unmount this share manually and the system shuts down the process hangs forever saying 'Unmounting Swap-backed filesystems'. If I unmount this manually by 'umount /var/cache/pacman/pkg' before the shutdown process all is well. I use multilib and all testing repos and upgrade on a daily basis. Actual version of initscripts: 2012.01.3-1 |
This task depends upon
My only guess so far is that this is some sort of kernel bug (as umount should never hang, even if it fails).
We at least need your rc.conf and fstab to be able to make sense of this.
Please also attach some relevant logs/output so we can see what is going on (one way to do this would be to add a call to 'bash' just before the umount call in rc.shutdown, that should give you a terminal so you can call umount manually with verbose output to see what happens).
First, /etc/exportfs of the fileserver
____________
/srv/pacman/cache/x86_64 192.168.1.0/24(rw,sync,no_subtree_check,no_root_squash)
/srv/pacman/cache/i686 192.168.1.0/24(rw,sync,no_subtree_check,no_root_squash)
____________
fairly trivial in my eyes.
Then, my /etc/fstab on the client
_____________
#
# /etc/fstab: static file system information
#
# <file system> <dir> <type> <options> <dump> <pass>
devpts /dev/pts devpts defaults 0 0
shm /dev/shm tmpfs nodev,nosuid 0 0
tmpfs /tmp tmpfs nodev,nosuid,noatime,size=1000M,mode=1777 0 0
#/dev/fd0 /media/fl auto user,noauto 0 0
/dev/sda2 /boot ext2 defaults 0 1
/dev/mapper/root / ext4 defaults 0 1
/dev/mapper/home /home ext4 defaults 0 1
/dev/mapper/swapDevice swap swap defaults 0 0
# NFS4-shares auf Server
teefax:/srv/pacman/cache/x86_64 /var/cache/pacman/pkg nfs4 defaults 0 1
___________________________
This seems to be complicated, but it also happens on systems that only have the last line additional to the default fstab.
The rc.conf on my system:
_______________________
#
# /etc/rc.conf - Main Configuration for Arch Linux
#
# See 'man 5 rc.conf' for more details
#
# LOCALIZATION
# ------------
#
HARDWARECLOCK="UTC"
TIMEZONE="Europe/Berlin"
KEYMAP="de-latin1"
CONSOLEFONT=
CONSOLEMAP=
LOCALE="de_DE.UTF-8"
DAEMON_LOCALE="yes"
USECOLOR="yes"
# HARDWARE
# --------
#
MODULES=(floppy vboxdrv vboxnetflt vboxnetadp)
USEDMRAID="no"
USEBTRFS="no"
USELVM="no"
# NETWORKING
# ----------
#
HOSTNAME="obelix"
interface=eth0
address=
netmask=
broadcast=
gateway=
NETWORK_PERSIST="no"
# DAEMONS
# -------
#
DAEMONS=(dbus acpid syslog-ng network rpcbind nfs-common netfs crond cupsd pcscd openntpd bluetooth sensors)
______________________
Again, this also happens on systems with rather uncomplicated rc.conf. acpid, pcscd, bluetooth and sensors are only running on my system but not on other affected boxes. virtualbox-modules and floppy are also only loaded on my system .
BTW, the shutdown process doens't hang any longer when this is mounted through fstab. I can only confirm this when the nfs share is mounted manually. After that shutdown will hang at the line 'Unmounting Swap-backed filesystems'. When the share is unmounted manually before shutdown all is well.
Hope this helps a bit more. I will provide some logs later this day when I have some spare time.
1) comment out the nfs entry from fstab
2) restart
3) mount your nfs entry manually
4) # rc.d stop netfs
5) check "findmnt" to see if your netfs is still mounted or not
Lokking forward to more info if it reoccurs.
What do you suggest to investigate further please?
So if you experienced this bug in the past, please try again to shutdown your box with manually mounted nfs-share(s) and write down your result here.