hald loads a core 100% attempting lazy unmount

Bug #366660 reported by MikeCalder
4
Affects Status Importance Assigned to Milestone
hal (Ubuntu)
Invalid
High
Unassigned

Bug Description

Binary package hint: hal

Installed Jaunty yesterday. AMD 64 dual core. Experienced several freezes with applications attempting file dialogs.

This morning, found one cause. An application had finished an operation on a USB mass storage device, which I then removed from the system. Subsequent attempts with other applications to use file dialogs caused applications to freeze. System Monitor showed that hald was occupying virtually 100% of the CPU on one core.

Monitor shows many dozen instances of

hal-storage-unmount Sleeping .... 884.0 KiB flock_lock_file_wait

Use of the other core allowed other applications and the desktop to continue limited operation.

On inspection of logs:

------------------------------------------------------------------------------
kern log, many instances of:
Apr 25 10:30:46 mikehome kernel: [ 2982.467307] FAT: Directory bread(block 8216) failed

------------------------------------------------------------------------------
daemon.log, many instances of

Apr 25 11:07:27 mikehome last message repeated 2080 times

(with different counts) following a message:

Apr 25 10:30:41 mikehome hald[2850]: forcibly attempting to lazy unmount /dev/sdc as enclosing drive was disconnected

------------------------------------------------------------------------------
syslog: combination of the two.
------------------------------------------------------------------------------

This continued even after the application(s) which had connected to the USB device were closed.

Nautilus may be involved. (ver 2.26.2) - on restarting Nautilus, the USB device mount points were visible in the navigation bar with "Unmount" as a right-click option. Attempting to unmount these gave an error dialog "Unable to mount..." with the message: "DBus error org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken."

description: updated
Revision history for this message
Matt Zimmerman (mdz) wrote :

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
status: New → Triaged
Revision history for this message
Carl Fink (carl-finknetwork) wrote :

I've just experienced the same problem. hald is now using 100% of one of the two cores on my system, with messages like this in kern.log:

Sep 30 12:04:14 Nitpickinghp2 kernel: [ 754.548991] invalid access to FAT (entry 0x15769559)
Sep 30 12:04:14 Nitpickinghp2 kernel: [ 754.555320] FAT: Filesystem panic (dev sda6)
Sep 30 12:04:14 Nitpickinghp2 kernel: [ 754.555325] invalid access to FAT (entry 0x6a5bcce7)
Sep 30 12:04:14 Nitpickinghp2 kernel: [ 754.560175] FAT: Filesystem panic (dev sda6)
Sep 30 12:04:14 Nitpickinghp2 kernel: [ 754.560178] invalid access to FAT (entry 0xe2fa0c1a)
Sep 30 12:04:14 Nitpickinghp2 kernel: [ 754.597459] FAT: Filesystem panic (dev sda6)
Sep 30 12:04:14 Nitpickinghp2 kernel: [ 754.597464] invalid access to FAT (entry 0xe6ae82d5)
Sep 30 12:04:14 Nitpickinghp2 kernel: [ 754.631716] FAT: Filesystem panic (dev sda6)

There are literally thousands of lines like this. I can't fully unmount or remount or check sda6, looks like I'll have to reboot.

Revision history for this message
dino99 (9d9) wrote :
Changed in hal (Ubuntu):
status: Triaged → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.