The kernel probably does it right (one space). But the kernel has to communicate with udev which communicates with hal (transmission across several spaces).
device_connect . udev_called . hald_reads_connect_from_socket . hald_mounts_device ... What if the device disconnects between hald receiving the connect message and mounting the filesystem? Or, what if the device is mounted, then disconnects and data is written to the device before hald receives the disconnect message? But, if you see this without hal, then my argument does become very weak. It's just that everytime I ran into "lost page write" or "buffer i/o errors" it apparently had something to do with a mismatch between what was perceived to be mounted and what was actually (not) mounted or vice versa. David -- ehci_hcd module causes I/O errors in USB 2.0 devices https://bugs.launchpad.net/bugs/88746 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
