One doesn't need to kill every hald-addon-storage in the system, just that is stalled:
$ ps afx|grep hal 6633 ? Sl 0:00 /usr/lib/gvfs/gvfs-hal-volume-monitor 20806 pts/3 D+ 0:00 | \_ grep --color=yes hal 20693 ? Ss 0:00 /usr/sbin/hald 20694 ? S 0:00 \_ hald-runner 20718 ? S 0:00 \_ hald-addon-input: Listening on /dev/input/event6 /dev/input/event5 /dev/input/event1 20721 ? S 0:00 \_ hald-addon-hid-ups: listening on /dev/usb/hiddev0 20723 ? S 0:00 \_ /usr/lib/hal/hald-addon-cpufreq 20724 ? S 0:00 \_ hald-addon-acpi: listening on acpid socket /var/run/acpid.socket 20727 ? S 0:00 \_ hald-addon-storage: polling /dev/sdb (every 2 sec) 20731 ? S 0:00 \_ hald-addon-storage: polling /dev/sdc (every 2 sec) 20740 ? S 0:00 \_ hald-addon-storage: polling /dev/scd0 (every 2 sec)
In my case killing 20727 "fixed" the log spam.
One doesn't need to kill every hald-addon-storage in the system, just that is stalled:
$ ps afx|grep hal gvfs/gvfs- hal-volume- monitor hal/hald- addon-cpufreq acpid.socket
6633 ? Sl 0:00 /usr/lib/
20806 pts/3 D+ 0:00 | \_ grep --color=yes hal
20693 ? Ss 0:00 /usr/sbin/hald
20694 ? S 0:00 \_ hald-runner
20718 ? S 0:00 \_ hald-addon-input: Listening on /dev/input/event6 /dev/input/event5 /dev/input/event1
20721 ? S 0:00 \_ hald-addon-hid-ups: listening on /dev/usb/hiddev0
20723 ? S 0:00 \_ /usr/lib/
20724 ? S 0:00 \_ hald-addon-acpi: listening on acpid socket /var/run/
20727 ? S 0:00 \_ hald-addon-storage: polling /dev/sdb (every 2 sec)
20731 ? S 0:00 \_ hald-addon-storage: polling /dev/sdc (every 2 sec)
20740 ? S 0:00 \_ hald-addon-storage: polling /dev/scd0 (every 2 sec)
In my case killing 20727 "fixed" the log spam.