> On Wed, 2003-05-28 at 10:04, Marco Fioretti wrote:
> > Hello,
> >
> > Yesterday I purchased an USB pen drive, connected it to a shrike PC
> Don't know exactly what kind of USB pen you have, but on mine is a very
> small switch which acts like a "write protect" tab...
> I've had no problems using it on RH8+9.
>
Mine has no such switch. For the record, I have tried again on the same RH
and got this dmesg (more info below):
hub.c: USB new device connect on bus1/1, assigned device number 2
usb.c: USB device 2 (vend/prod 0xc76/0x7) is not claimed by any active driver.
SCSI subsystem driver Revision: 1.00
Initializing USB Mass Storage driver...
usb.c: registered new driver usb-storage
scsi0 : SCSI emulation for USB Mass Storage devices
Vendor: Eutron Model: Picodisk Easy Rev: 1.00
Type: Direct-Access ANSI SCSI revision: 02
WARNING: USB Mass Storage data integrity not assured
USB Mass Storage device found at 2
USB Mass Storage support registered.
Attached scsi removable disk sda at scsi0, channel 0, id 0, lun 0
SCSI device sda: 256000 512-byte hdwr sectors (131 MB)
sda: Write Protect is off
sda: sda1
Filesystem panic (dev 08:01).
fat_free: deleting beyond EOF
File system has been set read-only
Filesystem panic (dev 08:01).
fat_free: deleting beyond EOF
File system has been set read-only
usb.c: USB disconnect on device 2
hub.c: USB new device connect on bus1/1, assigned device number 3
WARNING: USB Mass Storage data integrity not assured
USB Mass Storage device found at 3
usb-uhci.c: interrupt, status 2, frame# 302
I/O error: dev 08:01, sector 2
SCSI device sda: 256000 512-byte hdwr sectors (131 MB)
sda: Write Protect is off
sda: sda1
usb.c: USB disconnect on device 3
hub.c: USB new device connect on bus1/1, assigned device number 4
WARNING: USB Mass Storage data integrity not assured
USB Mass Storage device found at 4
##################################################################
then I mounted it to get:
mount -
rirme115/teifima/pendrive/
/dev/sda1: Input/output error
after that, however, I was indeed able to write files to it, umount, mount it
again, and
find the files safe and sound. I can also report that, on a friend PC with
win2K, it showed
no problem at all.
How should we call this problem, considering the output above? instability of USB
drivers in the kernel? hardware/connector problems? something else?
Keep in mind that I have seen the very same behavior
on shrike, even if the dmesg above comes from rh7.2
TIA,
Marco Fioretti
