http://bugzilla.kernel.org/show_bug.cgi?id=12896 Jan Kara <jack@xxxxxxx> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jack@xxxxxxx --- Comment #3 from Jan Kara <jack@xxxxxxx> 2009-03-25 14:51:20 --- This seems like a problem with your USB drive (or motherboard having too weak USB controller to power the drive or something like that). Because the drive disconnects after being mounted and later also gives IO errors. See: Mar 20 16:45:57 usb 1-6: configuration #1 chosen from 1 choice Mar 20 16:45:57 localhost kernel: scsi9 : SCSI emulation for USB Mass Storage devices Mar 20 16:46:02 localhost kernel: scsi 9:0:0:0: Direct-Access WD 1600BEAExternal 1.02 PQ: 0 ANSI: 0 Mar 20 16:46:02 localhost kernel: sd 9:0:0:0: [sde] 312581808 512-byte hardware sectors: (160 GB/149 GiB) ... Mar 20 16:46:04 localhost kernel: EXT3 FS on sde1, internal journal ... Mar 20 16:46:47 localhost kernel: usb 1-6: USB disconnect, address 4 ... Mar 20 16:47:00 localhost kernel: EXT3-fs error (device sde1): ext3_get_inode_loc: unable to read inode block - inode=2, block=1027 Mar 20 16:47:00 localhost kernel: EXT3-fs error (device sde1) in ext3_reserve_inode_write: IO failure ... And there are more IO errors because the drive then reconnects, gets sdf assigned but disconnects again. Anyway, this is either USB stack or HW problem. If you see it only with some kernel and not with other, it might be worth pursuing further. Otherwise I'd try to play with HW... -- Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching the assignee of the bug. -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
