[Bug 606989] Re: /var/run /var/lock mounts prevent umount of /var at shutdown

Steve Langasek steve.langasek at canonical.com
Fri May 17 22:00:00 UTC 2013


In later releases, neither /var/run nor /var/lock should be a
mountpoint, so there should be no failure to unmount them.  Therefore
closing this report.

** Changed in: sysvinit (Ubuntu)
       Status: Confirmed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to sysvinit in Ubuntu.
https://bugs.launchpad.net/bugs/606989

Title:
  /var/run /var/lock mounts prevent umount of /var at shutdown

Status in “sysvinit” package in Ubuntu:
  Fix Released

Bug description:
  Title says it all really.  Leads to error messages like

  umount2: Device or resource busy.
  umount: /dev/sda8 busy - remounted read-only

  in the shutdown console messages.

  Since /var is remounted read-only the technical consequences of this
  bug are nil, I think.  However, the user consequences are non-nil:
  the error messages serve as a red-herring for anyone troubleshooting
  their system.  I wasted time on it because I thought unsuccessful
  umounting of /var might be the cause of fscks on boot, this all
  following a power failure.  I now know better, but I wasted a couple
  of days on it (fuser & lsof come up blank).

  
  Ubuntu 10.04 LTS 64-bit.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/606989/+subscriptions




More information about the foundations-bugs mailing list