Hi again and thank you for clearing up that matter and pointing me in
the right direction.
The suspected app causing the problems /sbin/vol_id is part of the udev
package, and, as it seems, causes this problem to others as well as a
simple +udev +vol_id google illustrates.
Allow me one last question though, do you think the second set of error
messages, i posted here, the

#######################################################################
printk: 6 messages suppressed.
Buffer I/O error on device sdb1, logical block 978871
lost page write due to I/O error on sdb1
#######################################################################

kind of thing, is also related to the udev vol_id application (which as
it seems should do nothing more than probe for a device name)?
After several tests filling the mp3 player and deleting and so on this
error message seems to show up when the real damage is done to the
filesystem.

Gian Ghodrat

Am Samstag, den 20.08.2005, 21:49 -0400 schrieb Alan Stern: 
> On Sun, 21 Aug 2005, Gian Ghodrat wrote:
> 
> > ok, got it, switched to 2.6.12.5 too while enabling verbose output
> > (which didn't change anything, still the same errors).
> > 
> > i connected the mp3player and cut anything happening while doing so out
> > of my /var/syslog
> > output is pretty huge, but here you go:
> 
> I've cut out all of the unimportant parts from your log; basically they
> show everything happening normally.  Even the part shown here looks
> normal as far as usb-storage is concerned.
> 
> > Aug 21 00:22:16 localhost kernel: usb-storage: Command TEST_UNIT_READY
> > (6 bytes)
> > Aug 21 00:22:16 localhost kernel: usb-storage:  00 00 00 00 00 00
> > Aug 21 00:22:16 localhost kernel: usb-storage: Bulk Command S 0x43425355
> > T 0x19 L 0 F 0 Trg 0 LUN 0 CL 6
> > Aug 21 00:22:16 localhost kernel: usb-storage:
> > usb_stor_bulk_transfer_buf: xfer 31 bytes
> > Aug 21 00:22:16 localhost kernel: usb-storage: Status code 0;
> > transferred 31/31
> > Aug 21 00:22:16 localhost kernel: usb-storage: -- transfer complete
> > Aug 21 00:22:16 localhost kernel: usb-storage: Bulk command transfer
> > result=0
> > Aug 21 00:22:16 localhost kernel: usb-storage: Attempting to get CSW...
> > Aug 21 00:22:16 localhost kernel: usb-storage:
> > usb_stor_bulk_transfer_buf: xfer 13 bytes
> > Aug 21 00:22:16 localhost kernel: usb-storage: Status code 0;
> > transferred 13/13
> > Aug 21 00:22:16 localhost kernel: usb-storage: -- transfer complete
> > Aug 21 00:22:16 localhost kernel: usb-storage: Bulk status result = 0
> > Aug 21 00:22:16 localhost kernel: usb-storage: Bulk Status S 0x53425355
> > T 0x19 R 0 Stat 0x0
> > Aug 21 00:22:16 localhost kernel: usb-storage: scsi cmd done, result=0x0
> > Aug 21 00:22:16 localhost kernel: usb-storage: *** thread sleeping.
> 
> That was just like you'd expect, no errors.
> 
> > Aug 21 00:22:16 localhost kernel: printk: 62 messages suppressed.
> 
> I wonder what those 62 messages were...  Maybe they're related to what 
> comes next.
> 
> > Aug 21 00:22:16 localhost kernel: Buffer I/O error on device sdb1,
> > logical block 992000
> > Aug 21 00:22:16 localhost kernel: Buffer I/O error on device sdb1,
> > logical block 992001
> > Aug 21 00:22:16 localhost kernel: Buffer I/O error on device sdb1,
> > logical block 992002
> > Aug 21 00:22:16 localhost kernel: Buffer I/O error on device sdb1,
> > logical block 992003
> > Aug 21 00:22:16 localhost kernel: Buffer I/O error on device sdb1,
> > logical block 992004
> > Aug 21 00:22:16 localhost kernel: Buffer I/O error on device sdb1,
> > logical block 992005
> > Aug 21 00:22:16 localhost kernel: Buffer I/O error on device sdb1,
> > logical block 992006
> > Aug 21 00:22:16 localhost kernel: Buffer I/O error on device sdb1,
> > logical block 992007
> > Aug 21 00:22:16 localhost kernel: Buffer I/O error on device sdb1,
> > logical block 992000
> > Aug 21 00:22:16 localhost kernel: Buffer I/O error on device sdb1,
> > logical block 992001
> 
> Note that these messages appear with no intervening messages from 
> usb-storage.  Also notice this line from earlier in the log:
> 
> > Aug 21 00:22:15 localhost kernel: SCSI device sdb: 978944 512-byte hdwr
> > sectors (501 MB)
> 
> Apparently some program is trying to read beyond the end of the device.  
> (That is, 992000 > 978944, so of course the I/O will fail without even 
> trying to call usb-storage).  This isn't a kernel problem, it's a bug in 
> an application program.
> 
> > Aug 21 00:22:16 localhost udev[4777]: run_program: '/sbin/vol_id'
> > abnormal exit
> 
> My guess is that vol_id (whatever it is) is the guilty party.  Everything
> else in the log is perfectly normal.
> 
> 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
> 



-------------------------------------------------------
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

Reply via email to