Bug 128369 - updfstab does nothing on usb jumpdrive because scsi device string is improperly set?
updfstab does nothing on usb jumpdrive because scsi device string is improper...
Status: CLOSED NOTABUG
Product: Fedora
Classification: Fedora
Component: kudzu (Show other bugs)
2
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Bill Nottingham
David Lawrence
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2004-07-22 05:13 EDT by Spiros Papadimitriou
Modified: 2014-03-16 22:46 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2004-07-22 14:36:55 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Spiros Papadimitriou 2004-07-22 05:13:27 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7)
Gecko/20040706 Firefox/0.9.1

Description of problem:
I am running FC with the latest available kernel (2.6.6-1.435.2.3) and
I'm trying to get updfstab to see a Lexar JumpDrive (I've already run
kudzu with the device plugged in and hotplug seems to work just fine).
 The updfstab.conf.default does contain the device string.  However,
the "Model" string on the SCSI bus is simply "STORAGE DEVICE".

If I add that string to updfstab.conf, then everything works just fine
every time I plug in the drive.  Otherwise, nothing happens.  I also
tried "JUMPDRIVE2" but that does not seem to work.  Is there any
better solution than this??  Incidentally, this problem does not occur
only on the SMP kernel.  Some information that may be useful follows.

# uname -a
Linux mordor.angband.net 2.6.6-1.435.2.3smp #1 SMP Thu Jul 1 08:36:21
EDT 2004 i686 i686 i386 GNU/Linux
# rpm -q kernel kudzu hwdata
kernel-2.6.6-1.435.2.3
kudzu-1.1.62-1
hwdata-0.120-1
# cat /proc/scsi/scsi
Attached devices:
Host: scsi0 Channel: 00 Id: 00 Lun: 00
  Vendor: Generic  Model: STORAGE DEVICE   Rev: 1.25
  Type:   Direct-Access                    ANSI SCSI revision: 02
# cat /proc/scsi/usb-storage/1
   Host scsi1: usb-storage
       Vendor: LEXAR MEDIA
      Product: JUMPDRIVE2
Serial Number: 0000000309
     Protocol: Transparent SCSI
    Transport: Bulk
       Quirks:
# lsusb
Bus 004 Device 001: ID 0000:0000
Bus 003 Device 003: ID 050d:0084 Belkin Components
Bus 003 Device 002: ID 0451:2046 Texas Instruments, Inc. TUSB2046 Hub
Bus 003 Device 001: ID 0000:0000
Bus 002 Device 001: ID 0000:0000
Bus 001 Device 003: ID 05dc:a300 Lexar Media, Inc.
Bus 001 Device 001: ID 0000:0000
# cat /etc/sysconfig/hwconf
[...]
-
class: HD
bus: USB
detached: 0
driver: usb-storage
desc: "LEXAR MEDIA JUMPDRIVE2"
usbclass: 8
usbsubclass: 6
usbprotocol: 50
usbbus: 1
usblevel: 1
usbport: 4
usbdev: 2
vendorId: 05dc
deviceId: a300
usbmfr: LEXAR MEDIA
usbprod: JUMPDRIVE2
-

Regards,
Spiros

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1. Plug in flash drive    

Additional info:
Comment 1 Bill Nottingham 2004-07-22 14:36:55 EDT
The scsi device string is what's used; changing that would require a
kernel change.
Comment 2 Spiros Papadimitriou 2004-07-22 16:35:34 EDT
What does kudzu use and set the info in the /etc/sysconfig/hwconf? 
Why does it see it there and why doesn't updfstab use the same
information? 

AFAIK, there is nothing special with this JumpDrive device (generic
USB storage, recognized by the non-product-specific hotplug info), so
this should have nothing to do with the kernel driver (but I may be
wrong).  I also have the exact same problem with a JumpDrive Trio
(vendorID:productID=05dc:b013), on both FC2 machines I have.  In any
case, hotplug and kudzu work just fine and manually mounting the
device also works fine, I'd just like to get updfstab to see it.

Has anyone managed to get anyone JumpDrive recognized by updfstab? 
Any suggestions would be appreciated!  Thanks!
Comment 3 Bill Nottingham 2004-07-22 16:50:55 EDT
It uses the SCSI device field.

The USB information doesn't have the actual device name attached to
it; it isn't used.
Comment 4 Spiros Papadimitriou 2004-07-22 18:27:26 EDT
Hm, yes, there is also this bit in /etc/sysconfig/hwconf (which refers
to the sda device):
-
class: HD
bus: SCSI
detached: 0
device: sda
driver: ignore
desc: "Generic STORAGE DEVICE"
host: 0
id: 0
channel: 0
lun: 0
generic: sg0
-

Any suggestions on figuring out why the kernel does not set the SCSI
vendor/model strings according to the USB vendor/product strings for
either of these two JumpDrives?  I've been looking at the usb_storage
code for ~15mins and I'm kind of lost (apparently all this happens
indirectly, somewhere in the SCSI probing code or sth?).  Thanks again!

Note You need to log in before you can comment on or make changes to this bug.