I've seen this happen as well. mount(8) shows that the device it is
trying to unmount is not mounted at the time.
Apr 18 01:05:01 perseus hald[2821]: forcibly attempting to lazy unmount
/dev/sdb as enclosing drive was disconnected
Apr 18 01:05:32 perseus last message repeated 863 times
Apr 18 01:06:33 perseus last message repeated 1743 times
Apr 18 01:07:34 perseus last message repeated 1676 times
perseus:[~/iso] mount
/dev/sda1 on / type ext3 (rw,relatime,errors=remount-ro)
tmpfs on /lib/init/rw type tmpfs (rw,nosuid,mode=0755)
proc on /proc type proc (rw,noexec,nosuid,nodev)
sysfs on /sys type sysfs (rw,noexec,nosuid,nodev)
varrun on /var/run type tmpfs (rw,nosuid,mode=0755)
varlock on /var/lock type tmpfs (rw,noexec,nosuid,nodev,mode=1777)
udev on /dev type tmpfs (rw,mode=0755)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
devpts on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=620)
fusectl on /sys/fs/fuse/connections type fusectl (rw)
lrm on /lib/modules/2.6.28-11-generic/volatile type tmpfs (rw,mode=755)
tmpfs on /tmp type tmpfs (rw,nosuid,nodev)
securityfs on /sys/kernel/security type securityfs (rw)
gvfs-fuse-daemon on /home/mdz/.gvfs type fuse.gvfs-fuse-daemon
(rw,nosuid,nodev,user=mdz)
** Changed in: hal (Ubuntu)
Importance: Undecided => High
** Changed in: hal (Ubuntu)
Status: New => Triaged
--
hald loads a core 100% attempting lazy unmount
https://bugs.launchpad.net/bugs/366660
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
