[issue979] Failure-prone USB mass storage (SB600? msdosfs? CAM?)

["Joe \"Floid\" Kanowitz" <sinknull@xxxxxxxxxxxxxxxxxxxxxxx>]

Joe "Floid" Kanowitz <jkanowitz@snet.net> added the comment:

Short update:

The USB stick (PNY Attache 2GB) seems to be working fine with 1.12.  Perhaps I
wasn't stressing it much because the files were immediately copied from the HD
and back and a large portion may've been retained in cache.

Using a second card reader ("Zio Corporation," detected with a generic string
per below):

Controller /dev/usb2:
addr 1: full speed, self powered, config 1, OHCI root hub(0x0000), ATI(0x0000),
rev 1.00
 port 1 addr 2: low speed, power 100 mA, config 1, PS2/USB Browser Combo
Mouse(0x0011), Cypress Sem(0x05fe), rev 0.00
 port 2 addr 3: full speed, power 500 mA, config 1, USB2.0 Card Reader(0x0001),
Storage Device(0x0dda), rev 1.6f

. .. the 2GB CF card (which may or may not have a corrupt FS at this point)
presented with a severely truncated directory listing.  I believe it was trying
fsck_msdos that produced the following in dmesg:

contigmalloc_map: failed in index < 0 case!
umass1: BBB reset failed, STALLED
umass1: BBB bulk-in clear stall failed, STALLED
umass1: BBB bulk-out clear stall failed, STALLED
contigmalloc_map: failed in index < 0 case!
umass1: BBB reset failed, STALLED
umass1: BBB bulk-in clear stall failed, STALLED
umass1: BBB bulk-out clear stall failed, STALLED
contigmalloc_map: failed in index < 0 case!
umass1: BBB reset failed, STALLED
umass1: BBB bulk-in clear stall failed, STALLED
umass1: BBB bulk-out clear stall failed, STALLED
contigmalloc_map: failed in index < 0 case!
umass1: BBB reset failed, STALLED
umass1: BBB bulk-in clear stall failed, STALLED
umass1: BBB bulk-out clear stall failed, STALLED
contigmalloc_map: failed in index < 0 case!
umass1: BBB reset failed, STALLED
umass1: BBB bulk-in clear stall failed, STALLED
umass1: BBB bulk-out clear stall failed, STALLED
umass1: BBB reset failed, STALLED
umass1: BBB bulk-in clear stall failed, STALLED
umass1: BBB bulk-out clear stall failed, STALLED
(da2:umass-sim1:1:0:0): Synchronize cache failed, status == 0x4, scsi status == 0x0
umass1: BBB reset failed, STALLED
umass1: BBB bulk-in clear stall failed, IOERROR
umass1: BBB bulk-out clear stall failed, TIMEOUT

With the Zio reader, ls of a known-good 1GB CF was fine, while fsck_msdos failed
with that exact same output in dmesg.

Attempting to copy the roughly 1GB of large JPEGs from that card has proceeded
for perhaps a minute, hung for approximately 1 minute, and now to my surprise is
proceeding again.  That pattern now seems to be repeating, so I'm logging iostat
with timestamps to try to get some sense of it.

_____________________________________________________
DragonFly issue tracker <bugs@lists.dragonflybsd.org>
<https://bugs.dragonflybsd.org/issue979>
_____________________________________________________