[Bug 779434] New: On shutdown/reboot "Could not unmount /var: Device or resource busy"
https://bugzilla.novell.com/show_bug.cgi?id=779434 https://bugzilla.novell.com/show_bug.cgi?id=779434#c0 Summary: On shutdown/reboot "Could not unmount /var: Device or resource busy" Classification: openSUSE Product: openSUSE 12.2 Version: Final Platform: x86-64 OS/Version: openSUSE 12.2 Status: NEW Severity: Critical Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: alessandro.sturniolo@gmail.com QAContact: qa-bugs@suse.de Found By: --- Blocker: --- Created an attachment (id=504959) --> (http://bugzilla.novell.com/attachment.cgi?id=504959) Shutdown on workstation User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:15.0) Gecko/20100101 Firefox/15.0 If the system have a separate /var on another partition/disk, on shutdown it was unable to clean umount /var (because, I suppose, /var/run take it busy). I've this behaviour in my workstation and I've replicated it on a VirtualBox virtual machine. On my workstation, as side effects of the more complex partition layout (2 RAID 1 SSD disk as /, 3 RAID 5 HDD with LVM with /home /root /var /tmp dirs binded in /), this cause filesystem corruption at every reboot/shutdown. Actually, as a workaround to not corrupt more over my filesystem, I logout from desktop environment, init 1, stop manually as more service as I can, remount all filesystems read-only and then poweroff. My workstation fstab: UUID=3d1d8188-7413-4f89-8dce-47b9c38ab328 swap swap defaults 0 0 UUID=46bf26d8-ffe7-44c8-ad3b-90269d194bd3 / ext4 acl,user_xattr,relatime,discard 1 1 UUID=9a0cc638-83d7-43da-9b38-8d0f4e5af01a /mnt/VolGroup00-LogVol01 ext4 acl,user_xattr,relatime 1 2 /mnt/VolGroup00-LogVol01/var /var bind defaults,bind 0 0 /mnt/VolGroup00-LogVol01/tmp /tmp bind defaults,bind 0 0 /mnt/VolGroup00-LogVol01/root /root bind defaults,bind 0 0 /mnt/VolGroup00-LogVol01/home /home bind defaults,bind 0 0 proc /proc proc defaults 0 0 sysfs /sys sysfs noauto 0 0 debugfs /sys/kernel/debug debugfs noauto 0 0 usbfs /proc/bus/usb usbfs noauto 0 0 devpts /dev/pts devpts mode=0620,gid=5 0 0 The fstab of the fresh installed virtual machine: UUID=76f63653-7371-4b84-b7f6-ce88097da2a5 swap swap defaults 0 0 UUID=784906ae-2c06-4fc6-86fa-0b4702181c0a / ext4 acl,user_xattr 1 1 UUID=0187604f-2470-41be-be9b-2de2763ca984 /boot ext4 acl,user_xattr 1 2 UUID=6de41ea6-489e-48cd-9b3c-a007ac33d860 /home ext4 acl,user_xattr 1 2 UUID=9871a843-2fea-4909-b4d3-be61ccc8a785 /var ext4 acl,user_xattr 1 2 proc /proc proc defaults 0 0 sysfs /sys sysfs noauto 0 0 debugfs /sys/kernel/debug debugfs noauto 0 0 usbfs /proc/bus/usb usbfs noauto 0 0 devpts /dev/pts devpts mode=0620,gid=5 0 0 Reproducible: Always Steps to Reproduce: 1. Install a fresh machine/virtual machine. 2. Restart/Shutdown and watch the system messages. Actual Results: On shutdown/reboot: On Workstation (/var /tmp /home /root binded to /): Could not unmount /var: Device or resource busy Not all file systems unmounted, 1 left. Detaching DM devices. Could not delete dm /dv/dm-0: Device or resource busy Not all DM devices detached, 1 left. Too many iterations, giving up. On Virtual Machine (slightly different file systems layout): Could not unmount /var: Device or resource busy Expected Results: Clean unmounting and clean shutdown/reboot. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=779434 https://bugzilla.novell.com/show_bug.cgi?id=779434#c1 --- Comment #1 from Alessandro Sturniolo <alessandro.sturniolo@gmail.com> 2012-09-09 12:51:27 UTC --- Created an attachment (id=504960) --> (http://bugzilla.novell.com/attachment.cgi?id=504960) Shutdown on virtual machine -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=779434 https://bugzilla.novell.com/show_bug.cgi?id=779434#c kk zhang <kkzhang@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |kkzhang@suse.com AssignedTo|bnc-team-screening@forge.pr |werner@suse.com |ovo.novell.com | -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=779434 https://bugzilla.novell.com/show_bug.cgi?id=779434#c2 --- Comment #2 from Alessandro Sturniolo <alessandro.sturniolo@gmail.com> 2012-09-10 17:26:20 UTC --- I've found, that both in the workstation and in the virtual machine, the blocking process is systemd. Is the only process that take busy /var/run lsof +D /var and lsof +D /var/run return output only for /var/run with systemd that take open same sockets (/var/run/avahi-daemon/socket, /var/run/cups/cups.sock, /var/run/dbus/system_bus_socket) and a named pipe (/var/run/systemd/sessions/5.ref) but this named pipe is the login process and I suppose that it disappear after I logout from terminal. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=779434 https://bugzilla.novell.com/show_bug.cgi?id=779434#c3 Dr. Werner Fink <werner@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |werner@suse.com AssignedTo|werner@suse.com |fcrozat@suse.com --- Comment #3 from Dr. Werner Fink <werner@suse.com> 2012-09-11 08:18:55 UTC --- Cool ... systemd is locking parts of the virtual file system -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=779434 https://bugzilla.novell.com/show_bug.cgi?id=779434#c4 Frederic Crozat <fcrozat@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |alessandro.sturniolo@gmail. | |com --- Comment #4 from Frederic Crozat <fcrozat@suse.com> 2012-09-20 09:11:47 UTC --- I think it is coming from plymouthd which is still using some files in /var/cache. Could you test the following: * boot with the debug options: systemd.log_level=debug systemd.log_target=kmsg log_buf_len=1M enforcing=0 * save the following script as /lib/systemd/system-shutdown/debug.sh and make it executable: #!/bin/sh mount -o remount,rw / dmesg > /shutdown-log.txt lsof /var >> /shutdown-log.txt mount -o remount,ro / * reboot and attach the log to this bug report -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=779434 https://bugzilla.novell.com/show_bug.cgi?id=779434#c5 --- Comment #5 from Alessandro Sturniolo <alessandro.sturniolo@gmail.com> 2012-09-20 16:34:35 UTC --- Created an attachment (id=506444) --> (http://bugzilla.novell.com/attachment.cgi?id=506444) Shutdown log on virtual machine -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=779434 https://bugzilla.novell.com/show_bug.cgi?id=779434#c6 --- Comment #6 from Alessandro Sturniolo <alessandro.sturniolo@gmail.com> 2012-09-20 16:35:41 UTC --- Created an attachment (id=506445) --> (http://bugzilla.novell.com/attachment.cgi?id=506445) Shutdown log on workstation -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=779434 https://bugzilla.novell.com/show_bug.cgi?id=779434#c7 Frederic Crozat <fcrozat@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|alessandro.sturniolo@gmail. | |com | --- Comment #7 from Frederic Crozat <fcrozat@suse.com> 2012-09-20 16:40:28 UTC --- ok, as expected (I'm getting the same issue on my test VM). please test by removing splash=silent on your kernel command line and see if it fixes /var umounting.. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=779434 https://bugzilla.novell.com/show_bug.cgi?id=779434#c8 --- Comment #8 from Alessandro Sturniolo <alessandro.sturniolo@gmail.com> 2012-09-20 17:20:03 UTC --- Ok, I can confirm that removing splash=silent from kernel command line, fixed the /var umounting both in the virtual machine and in the workstation. I'll take this as a better workaround than mine ;) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=779434 https://bugzilla.novell.com/show_bug.cgi?id=779434#c Frederic Crozat <fcrozat@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|fcrozat@suse.com |systemd-maintainers@suse.de -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=779434 https://bugzilla.novell.com/show_bug.cgi?id=779434#c9 Thomas Blume <thomas.blume@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO CC| |thomas.blume@suse.com InfoProvider| |alessandro.sturniolo@gmail. | |com --- Comment #9 from Thomas Blume <thomas.blume@suse.com> 2014-06-05 15:03:57 UTC --- This might have been a problem of plymouth. In OpenSUSE 13.1 the following fix has been introduced: * Fri Feb 22 2013 tittiatcoke@gmail.com - Added patch plymouth-correct-runtime-dir.patch to make the plymouthruntimedir equal to /run/plymouth and not /var/run/plymouth Can you please check wheter you still see the issue on 13.1? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=779434 https://bugzilla.novell.com/show_bug.cgi?id=779434#c10 --- Comment #10 from Thomas Blume <thomas.blume@suse.com> 2014-06-05 15:15:48 UTC --- Sorry, I need to correct myself. The patch was introduced in OpenSUSE 12.3, but please retest with the latest version. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=779434 https://bugzilla.novell.com/show_bug.cgi?id=779434#c11 Alessandro Sturniolo <alessandro.sturniolo@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |RESOLVED InfoProvider|alessandro.sturniolo@gmail. | |com | Resolution| |FIXED --- Comment #11 from Alessandro Sturniolo <alessandro.sturniolo@gmail.com> 2014-06-06 15:23:19 UTC --- Ok, I can confirm it was fixed. I tested on openSuSE 13.1 Thanks -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com