[Bug 1103416] Re: 12.04 isn't cleanly unmounted

[Stefan Tauner]

i have been digging further.
REG_MTPTS contains the following values in my setup: /tftpboot/loops/sysrescuecd /tftpboot /data/backup/home-recover /var/cache /home /boot /data 
i have redirected the output of the umount call (initiated via fstab-decode) to a log file:
	fstab-decode umount -f -v -r -d $REG_MTPTS  >> /umountfs.log 2>&1
the output is:
can't delete device /dev/loop0: No such device or address
umount2: Device or resource busy
umount: /data/home busy - remounted read-only
/dev/loop0 has been unmounted
/data/tftpboot has been unmounted
/data/backup/home/hourly.0 has been unmounted
/data/cache has been unmounted
/dev/sda1 has been unmounted
/dev/mapper/ssd-data has been unmounted

the first line is apparently a problem with umount trying to delete the loop device (umount's -d option) but i dont think that is related.
i am not sure about umount2. it is either related to the loop device or to /data/home... which is clearly not cleanly umounted, but remounted as read-only (due to umount's -r option).

so... why is it busy? i have no idea.
lsof and ps auxf output (called before "Unmount local filesystems") attached


** Attachment added: "umountfs-lsof.log"
   https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/1103416/+attachment/3509715/+files/umountfs-lsof.log

-- 
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/1103416

Title:
  12.04 isn't cleanly unmounted

Status in “upstart” package in Ubuntu:
  Confirmed

Bug description:
  Noticed this when the boot-time took too long. Every reboot the
  journal must recover the root file system (i have the /home-filesystem
  on a second partition). I saw this in dmesg (not always the same but
  about, and this is always there at every boot):

  [ 9.252087] EXT3-fs (sda1): recovery required on readonly filesystem
  [ 9.252091] EXT3-fs (sda1): write access will be enabled during recovery
  [ 10.928126] kjournald starting. Commit interval 5 seconds
  [ 10.928181] EXT3-fs (sda1): orphan cleanup on readonly fs
  [ 10.928188] ext3_orphan_cleanup: deleting unreferenced inode 338285
  [ 10.928222] ext3_orphan_cleanup: deleting unreferenced inode 337758
  [ 10.928229] ext3_orphan_cleanup: deleting unreferenced inode 338428
  [ 10.928238] ext3_orphan_cleanup: deleting unreferenced inode 1622019
  [ 10.936544] ext3_orphan_cleanup: deleting unreferenced inode 1622017
  [ 10.936559] EXT3-fs (sda1): 5 orphan inodes deleted
  [ 10.936562] EXT3-fs (sda1): recovery complete
  [ 11.017444] EXT3-fs (sda1): mounted filesystem with ordered data mode
  [ 31.210636] Adding 3903788k swap on /dev/sda2. Priority:-1 extents:1 across:3903788k
  [ 32.044232] EXT3-fs (sda1): using internal journal

  I have tried much of the workarounds covering dbus bugs or network-
  manager bugs for example
  https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/740390 to no
  success. My system is a stock ubuntu 12.04 with some PPA-packages but
  not system ones. I've no slight idea what happens.

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