Home > Failed To > Failed To Unmount /var

Failed To Unmount /var

Only affects the filesystem containing /var/log (journal location). Offline #18 2015-11-11 23:47:40 zasire Member Registered: 2011-07-20 Posts: 10 Re: systemd "failed to unmount /var" This is expected behavior of journald. Stop network.target 2. Not the answer you're looking for? Check This Out

It seems to be a systemd-bug. Are people of Nordic Nations "happier, healthier" with "a higher standard of living overall than Americans"? share|improve this answer edited Apr 3 '14 at 14:38 n611x007 3121414 answered Apr 7 '12 at 17:52 ZakW 38132 10 All 924 days uptime means is that you need to Browse other questions tagged linux arch-linux shutdown reboot or ask your own question.

Feb 02 15:42:30 systemd[1]: Failed unmounting /tmp. On a shutdown after reverting the commit, the log shows clearly that unmounting /run/user/1000 takes place in the very end of the shutdown process (line 124). The difference is that lsof with no arguments shows all open files using some sort of cache table, and grep is very fast at searching through it. Ideally, we'd just provide a bus method for this operation, that we could call during shutdown, but we cannot do that, as dbus-daemon is a client to journald, and that would

You've got a point on that. > Also, Lennart claims "This specific issue is pretty cosmetic > actually, as all you see is the EBUSY error messages during shutdown, but > Contributor eworm-de commented Oct 15, 2015 I still see Failed unmounting /var/log with systemd 227. When I stopped the nfs-kernel-server I could umount the directory. Contributor eworm-de commented Aug 10, 2015 I do see a similar problem with /var/log: Aug 10 19:33:10 thebe systemd[1]: Stopped Flush Journal to Persistent Storage.

Regards, David. Aug 17 01:11:10 anon systemd[539]: pam_unix(systemd-user:session): session closed for user hookline Aug 17 01:11:10 anon systemd[538]: Received SIGRTMIN+24 from PID 921 (kill). Journalctl shows that both /var and /home failed unmounting. https://github.com/systemd/systemd/issues/867 Do we know exactly where Kirk will be born?

Comment 10 Christian Stadelmann 2015-03-24 18:15:29 EDT Present on F22 alpha. I've done this because the micromanaging has helped me in the past deal with this problem and fat32 volumes are very easy to deal with if problems arise (They can be Perhaps Fedora shows the same behaviour and it isn't related to your problem. Notice that unmounting /run/user/1000 starts already on line 50 where user services (particularly profile-sync-daemon) haven't even exited yet.

Aug 17 00:36:57 anon umount[839]: umount: /var: target is busy Aug 17 00:36:57 anon umount[839]: (In some cases useful info about processes that Aug 17 00:36:57 anon umount[839]: use the device news Aug 17 01:06:14 anon mkinitcpio[1458]: ==> Starting build: none -- Aug 17 01:06:15 anon systemd[1]: Removed slice system-systemd\x2dbacklight.slice. Harv234 commented Oct 15, 2015 Yes, I know that. Failed unmounting /run/user/1000 Failed unmounting /home It's been happening when shutting down or rebooting.

graysky2 commented Sep 29, 2015 Reverting this commit has not solved my problem. his comment is here How To Tell When Broccoli is Bad? Comment 8 Christian Stadelmann 2014-10-01 06:29:59 EDT Present on F21 alpha. Aug 17 01:06:15 anon systemd[1]: Stopped Remount Root and Kernel File Systems.

stop remote-fs.target 13. This is a real productive system, so I want my logs to go to disk. Last edited by TheRinger (2015-08-17 12:57:38) Offline #12 2015-08-17 17:17:51 Gregosky Member From: UK Registered: 2013-07-26 Posts: 86 Re: systemd "failed to unmount /var" Did you read this thread? this contact form Couldn't umounting /var or /var/log be delayed until then?

This occurs where /var is on its own separate partition. https://bbs.archlinux.org/viewtopic.php … 4#p1204644Arch Linux dev is saying there is nothing to be worried about. Aug 17 02:04:18 anon umount[2567]: umount: /var: target is busy Aug 17 02:04:18 anon umount[2567]: (In some cases useful info about processes that Aug 17 02:04:18 anon umount[2567]: use the device

You can't unmount /tmp /usr/ or /var they are not filesystems (they are all part of the root (/) filesystem).

  • Comment 4 moon300web 2014-02-02 11:31:56 EST I have the same problem: system shutdown hangs with last line on screen: unmounting /sys/fs/fuse/connections Looking at the shutdown messages, system seems to fail to
  • I believe that due to this same bug systemd might unmount those overlays before profile-sync-daemon has the opportunity to sync the profiles back to disk, causing data loss.
  • Relevant?
  • Aug 04 19:55:31 lenovo systemd[1]: Failed unmounting /run/user/1000. -- Subject: Unit run-user-1000.mount has finished shutting down -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit run-user-1000.mount has finished shutting down. --
  • Unix & Linux Stack Exchange depends on everyone sharing their knowledge.
  • If you suspect you have something left running in a chroot, sudo ls -l /proc/*/root | grep chroot will find the culprit (replace "chroot" with the path to the chroot).
  • No errors since systemd 227.
  • Aug 17 01:11:10 anon systemd[1]: Stopped Authorization Manager.
  • Personal Open source Business Explore Sign up Sign in Pricing Blog Support Search GitHub This repository Watch 149 Star 1,555 Fork 660 systemd/systemd Code Issues 515 Pull requests 37 Projects

It seems like the readahead services need to be stopped before unmounting the root filesystem. stop basic.target 5. dhclient is a child process of NetworkManager - should NetworkManager clean it up? But on the Arch Wiki, it says the shutdown hook is obsolete so I guess there's nothing to do then.

Description: Ubuntu 12.10 Release: 12.10 upstart: Installed: 1.5-0ubuntu9 Candidate: 1.5-0ubuntu9 Version table: *** 1.5-0ubuntu9 0 500 http://jp.archive.ubuntu.com/ubuntu/ quantal/main amd64 Packages 100 /var/lib/dpkg/status Add tags Tag help Graham Waugh (gureamu) on 2012-12-13 systemd-journald is stopped a bit earlier during shutdown, thus collecting fewer log messages. Aug 17 00:44:40 anon systemd[1]: Started Store Sound Card State. navigate here I'd already checked the output of fuser -vm /lsof +D , mount and cat /proc/mounts, checked whether some old nfs-kernel-server was running, turned off quotas, attempted (but failed) a umount -f

A few rebus puzzles What is this blue thing in a photograph of a bright light? If that shows true, I believe this would be resolved by changing dbus to stop on stopping networking affects: network-manager (Ubuntu) → ifupdown (Ubuntu) Stéphane Graber (stgraber) wrote on 2012-12-13: #3 This can particularly affect user services like profile-sync-daemon which make use of $XDG_RUNTIME_DIR (mine being /run/user/1000). This has been happening with both v225 and v226.