LTSPFS: Some USB sticks are not auto-mounted

Bug #274122 reported by René Fleschenberg
2
Affects Status Importance Assigned to Milestone
ltspfs (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Binary package hint: ltspfs

Ubuntu 8.04.1
ltspfs 0.5.0~bzr20080109-3ubuntu3 (client)
ltspfsd 0.5.0~bzr20080109-3ubuntu3 (server)
udev 117-8 (both client and server)
linux-image-generic-2.6.24.19.21 (client)
linux-image-server-2.6.24.19.21 (server)

When I plug in USB sticks of certain models, they are not auto-mounted. The client does notice that the stick is plugged in, and I can manually mount it, but /var/run/drives stays empty.

An example ID of a non-working device (according to lsusb): 090c:1000

The same stick is auto-mounted fine when plugged into the server locally.

Other models work perfectly fine from LTSP clients (for example, a device with ID 04e8:5050).

Revision history for this message
Stéphane Graber (stgraber) wrote :

The udev rules file has been updated in Intrepid and should now match most USB devices, can you please try it and tell us if you still have that buggy behavior ?

Thanks

Stéphane

Changed in ltspfs:
status: New → Incomplete
Revision history for this message
René Fleschenberg (rene.f) wrote :

With the udev rules file from Intrepid, the USB stick is still not auto-mounted.

Revision history for this message
René Fleschenberg (rene.f) wrote :

Hi,

I now discovered that for the non-working usb stick, /sys/block/sda/removable contains 0. This explains why the udev rule does not trigger. If I adjust the udev rule accordingly, the device works as expected.

As a somewhat dirty workaround, I am currently using this rule:

    ACTION=="add", SUBSYSTEM=="block", KERNEL=="sda1" RUN+="add_fstab_entry %k"

This works for my environment, but of course not as a general solution.

Maybe, even this bold rule would work? Or will that have unintended side effects?

    ACTION=="add", SUBSYSTEM=="block", RUN+="add_fstab_entry %k"

Since the device is auto-mounted fine when used on the server locally, there must be a udev rule in a normal Hardy installation that matches correctly.

Changed in ltspfs:
status: Incomplete → New
Revision history for this message
GideonRomm (gideon) wrote :

Latest upstream should address this, as we no longer block removable devices in a udev rule at all. Instead, we block only ide and ata devices that are not removable by default - what we call "Internal disks". USB disks, wether removable or not, should no longer be blocked by default.

This will no doubt make it into Jaunty. Not sure if/when a backport to Intrepid is planned.

Revision history for this message
Scott Balneaves (sbalneav) wrote :

Fixed since jaunty. Give karmic a try and let us know.

Changed in ltspfs (Ubuntu):
status: New → Fix Released
Revision history for this message
René Fleschenberg (rene.f) wrote :

I havn't see it anymore after updating to jaunty. Thanks!

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.