On Wed, 27 Jul 2005, Keith Hellman wrote: > Thanks for getting back to me so quickly. Here is the snippit of the > /var/log/debug immediately after the rsync error. > > Jul 26 13:24:52 localhost kernel: usb-storage: -- transfer complete > Jul 26 13:24:52 localhost kernel: usb-storage: Bulk status result = 0 > Jul 26 13:24:52 localhost kernel: usb-storage: Bulk Status S 0x53425355 T > 0x6e85 R 0 Stat 0x0 > Jul 26 13:24:52 localhost kernel: usb-storage: scsi cmd done, result=0x0 > Jul 26 13:24:52 localhost kernel: usb-storage: *** thread sleeping. > Jul 26 13:24:53 localhost khellman: FIRST SYNC ERROR DISPLAYED ON CONSOLE > Jul 26 13:42:05 localhost kernel: usb-storage: queuecommand called > Jul 26 13:42:05 localhost kernel: usb-storage: *** thread awakened. > Jul 26 13:42:05 localhost kernel: usb-storage: Command READ_10 (10 bytes) > Jul 26 13:42:05 localhost kernel: usb-storage: 28 00 00 00 4a 57 00 00 01 00 > Jul 26 13:42:05 localhost kernel: usb-storage: Bulk Command S 0x43425355 T > 0x6e86 L 512 F 128 Trg 0 LUN 0 CL 10 > > As you can see, there aren't anymore debug messages for almost 15 > minutes. I inserted the 'FIRST SYNC ERROR...' message by just hovering > over the enter key of a logger invokation while my sync process ran in > another window, so there is definetly a delay between the filesystem > switching to read-only and my logger message showing up. Apparently, > that delay is enough for all of the usb i/o to complete.
Interestingly, in your original log the last write operation occurred 33 seconds before your sync error message, with lots of reads in between. I guess that's typical for rsync operations, though. > More disheartening is that the usb logs don't show any abnormal > conditions. Yes. Whatever went wrong, it doesn't seem to be connected with the USB stack. > It seems there are only two routes from here: > - add more debug code to usb-storage That won't show anything useful. > - turn on debug in other kernel modules to determine why the fileystem > is being switched to read-only. I assume this would be the vfat > driver, but I honestly don't know. You're probably right. I believe the vfat driver has undergone some changes recently. > Any insights from your side of the fence? You can try mounting the H300's filesystem without the "-o sync" option. Alan Stern ------------------------------------------------------- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf _______________________________________________ [email protected] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-users
