Alan, I recompiled to kernel to get usb-stor debuf msgs. When I try to
read a file previously recorded by windows system, this is what is
shows(/dev/sdb mounted on /mnt/usb):
>cp /mnt/usb/file.txt .
usb-storage: Command READ_10 (10 bytes)
usb-storage: 28 00 00 00 0c 5f 00 00 01 00
usb-storage: Bulk Command S 0x43425355 T 0xac L 4096 F 128 Trg 0 LUN 0 CL 10
usb-storage: usb_stor_bulk_transfer_buf: xfer 31 bytes
FAT: Filesystem panic (dev sdb)
fat_get_cluster: invalid cluster chain (i_pos 669)
File system has been set read-only
FAT: Filesystem panic (dev sdb)
fat_get_cluster: invalid cluster chain (i_pos 669)
usb-storage: Status code 0; transferred 31/31
usb-storage: -- transfer complete
usb-storage: Bulk command transfer result=0
usb-storage: usb_stor_bulk_transfer_sglist: xfer 4096 bytes, 1 entries
usb-storage: Status code 0; transferred 4096/4096
usb-storage: -- transfer complete
usb-storage: Bulk data transfer result 0x0
usb-storage: Attempting to get CSW...
usb-storage: usb_stor_bulk_transfer_buf: xfer 13 bytes
usb-storage: Status code 0; transferred 13/13
usb-storage: -- transfer complete
usb-storage: Bulk status result = 0
usb-storage: Bulk Status S 0x53425355 T 0xac R 0 Stat 0x0
usb-storage: scsi cmd done, result=0x0
usb-storage: *** thread sleeping.
The rest of the log seems ok(before the copy command). To me this
looks like a imcompatibility in the way both Linux and Windows deal
with FAT when the pen drive uses 4K block size. I say that because i
tested the pen drive with 512-byte block size, and it works from one
system to the other. Is that possible?
thanks!
Sara
On Wed, 19 Jan 2005 10:53:13 -0500 (EST), Alan Stern
<[EMAIL PROTECTED]> wrote:
> On Tue, 18 Jan 2005, Sara Fonseca wrote:
>
> > Hi,
> >
> > when I connect my pen drive in linux(kernel 6.9) the filesystem
> > automounts, but as read-only.
>
> Most likely the pen drive is telling your computer that it is
> write-protected.
>
> > Another issue is that i cant read the
> > files(I/O errors). The pen drive was previously formatted with fat in
> > windows.
> > Is it a firmware error? If so, is there a good linux sniffer?
>
> There's no way to tell whether this is a firmware error without more
> information. You can get more information by turning on the usb-storage
> verbose debugging option in the kernel configuration and rebuilding the
> driver. This will cause a lot of additional messages to be sent to the
> system log. You may have to update /etc/syslog.conf to tell the syslog
> daemon that it should store debug-level messages from the kernel rather
> than ignoring them. Doing this will probably tell you what you need to
> know without any need for a sniffer.
>
> Alan Stern
>
>
-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
linux-usb-devel@lists.sourceforge.net
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
