That's certainly where the IO errors are triggered at bootup. Can you send the code snippet ?You mean from the init script? Here it is: hsg80_init() { dummy_capa=2097152 for i in $(grep -rl 2097152 /sys/block/sd*/size|awk -F/ '{print $4}') do echo echo "##################################" echo "FIXING HSG80 device: $i" echo sg_start -start /dev/$i sleep 1 echo 1>/sys/block/$i/device/rescan done } I put the echo's in so that I could see if and for which devices it was being called. And yes, it's called for the two "ghost" devices (sdc and sdd). But if you look at boot output, the errors begin well beforethe multipath-tools init script runs.
Right, this script can't be the culprit.
Here is a trimmed excerpt: (218411 MB) [42949395.380000] SCSI device sdb: drive cache: write through [42949395.450000] sdb: unknown partition table [42949395.510000] sd 0:0:1:1: Attached scsi disk sdb [42949395.580000] sdc : READ CAPACITY failed. [42949395.580000] sdc : status=1, message=00, host=0, driver=08 [42949395.710000] sd: Current: sense key: Not Ready [42949395.770000] Additional sense: Logical unit not ready, initializing cmd. required [42949395.870000] sdc: asking for cache data failed [42949395.930000] sdc: assuming drive cache: write through [42949396.000000] sdc : READ CAPACITY failed. [42949396.000000] sdc : status=1, message=00, host=0, driver=08 [42949396.130000] sd: Current: sense key: Not Ready [42949396.190000] Additional sense: Logical unit not ready, initializing cmd. required [42949396.300000] sdc: asking for cache data failed [42949396.360000] sdc: assuming drive cache: write through [42949396.430000] sdc:<6>sd 0:0:2:1: Device not ready. [42949396.490000] end_request: I/O error, dev sdc, sector 0
The scsi driver probing seems to fail with io errors on ghost paths. If so, you can consider it harmless. Regards, cvaroqui -- dm-devel@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/dm-devel
