On Mon, Jun 14, 2010 at 12:17:53PM +0100, Alan Cox wrote: > > > sd 11:0:0:0: [sdd] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE > > > sd 11:0:0:0: [sdd] Sense Key : Medium Error [current] [descriptor] > > That is the drive complaining about a bad block. > > > > Descriptor sense data with sense descriptors (in hex): > > > 72 03 13 00 00 00 00 0c 00 0a 80 00 00 00 00 00 > > > 00 5b 23 bb > > > sd 11:0:0:0: [sdd] Add. Sense: Address mark not found for data field > > > sd 11:0:0:0: [sdd] CDB: Read(10): 28 00 00 5b 23 4f 00 00 80 00 > > Which in my experience usually comes from > > - The disc being unable to find the data block > > - A corrupt indirect block in the file system leading to a requst for an > out of range data block > > In theory it could be an on the wire bitflip but thats a bit too > consistent to believe. Thank, Alan. I really don't care about the drive (nothing valuable on it). It was an old IDE disk and I am not surprised it has some bad sectors. In fact I was clearing it for junking it (although I may keep it now just in case I need to test IDE error handling again :) But I cared about the system becoming unusable due to error handling running amok. That was the point of this bug report. -Andi -- ak@xxxxxxxxxxxxxxx -- Speaking for myself only. -- To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
