Date: Sat, 13 Sep 2003 16:33:04 +1200 From: Andrew Thompson <andy@fud.org.nz> To: Nate Lawson <nate@root.org> Cc: current@freebsd.org Subject: Re: USB da(4) quirks deprecated Message-ID: <3F629E00.7010708@fud.org.nz> In-Reply-To: <20030822094621.T4440@root.org> References: <20030806213504.S74720@root.org> <03Aug8.140932nzst.119071@homer.fire.org.nz> <20030807200629.G77081@root.org> <1060346467.33258.3.camel@localhost> <20030808084040.C78146@root.org> <1060413953.33258.18.camel@localhost> <20030822094621.T4440@root.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Nate Lawson wrote:
>>dmesg:
>>umass0: SigmaTel, Inc. USBMSC Audio Player, rev 1.10/0.01, addr 3
>>umass0: Get Max Lun not supported (IOERROR)
>>Enabling quirks for device
>>da0 at umass-sim0 bus 0 target 0 lun 0
>>da0: <SigmaTel MSCN 0001> Removable Direct Access SCSI-4 device
>>da0: 1.000MB/s transfers
>>da0: 125MB (256001 512 byte sectors: 64H 32S/T 125C)
>>
>>
>The NO_PREVENT support has been added. Does this work for you?
> {
> {T_DIRECT, SIP_MEDIA_REMOVABLE, "SigmaTel", "MSCN", "*"},
> /*quirks*/ DA_Q_NO_SYNC_CACHE|DA_Q_NO_PREVENT
> },
>
>
>
Yes, it does work :)
I have just got around to trying this pen-drive again and have been
trying tracking down data corruptions. If I mount the drive, write a
file, umount/mount again the file is different.
Using cmp I have found that there are consistent blocks of nulls in the
written file where data should be. The block is always 0xfff bytes long
and starts at 0x3000. I have tried many files and the offsets are
always the same. All the other data in the file is correct and at the
right location.
0x3000 -> 0x3fff
0x7000 -> 0x7fff
0xb000 -> 0xbfff
0xf000 -> 0xffff
0x13000 -> 0x13fff
... and so on until the end of the file ...
Any suggestions?
Andy
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3F629E00.7010708>