Comment 6 for bug 105563

On Hardy (2.6.24), there are still problems. CONFIG_USB_PERSIST=y, in /boot/config-2.6.24-16-generic.

 I don't have time right now to test a lot of stuff, for one thing because my Toshiba A70 is really slow to boot. (kernel seems to stick for a while before before detecting hard drives...)

 I hibernated with a Patriot brand USB stick mounted (by gnome/nautilus), and when I came back there seemed to be two mount points. /media/Patriot on /dev/sda1, and /media/Patriot_ on /dev/sdb1. I didn't notice until I'd unmounted one of them, but I think the kernel detected the USB stick again, instead of realizing that it was the same one present when it hibernated. I did remove and reinsert the USB stick, after a while, so that's in the kernel log, too.

 My kern.log shows this. Note the sda insertion on May 7, 23:50, then the hibernate. After the resume on May 8, 14:15, the USB stick is detected as sdb. There are some FAT directory read errors, which makes it look like the kernel really did get something crossed up. This might have been the original mount which became stale after resume from hibernation? I don't know if there ever was a /dev/sda1 block dev after the resume.

 Eventually just umount and pumount, and clicking on unmount in nautilus, got rid of /media/Patriot*, and the mount entries, so I didn't have to hack mtab or anything.