Mike Christie <michaelc@xxxxxxxxxxx> wrote: > When IO is sent to a path that cannot execute IO optimally, the scsi hw > handler hook for sense processing (see rdac_check_sense in "[PATCH 8/9] > scsi_dh: add lsi rdac device handler" and the scsi_error.c hook in in > "scsi_dh: add skeleton for SCSI Device Handlers") will detect this and set > the state to passive so future IO is not execute on the path > (SG_IO/passthrough is allowed). > > I am not sure about alternatives. If we just exported the port access state > in sysfs, but did not fail IO from scsi_prep_state_check, then the users > could still check the state before sending IO. Would it be horrible to > convert apps to do this? The majority of the boot up delays is caused by the kernel partition scanning and other kernel init code (Chandra please correct if that is not true). Sysfs attributes would not help here. One option maybe to add handling of the newer BLKERR_ codes in the generators of IO or some similar solution with a rollout possibly focused at the top generators of IO. A number of user apps like lvm scanning that execute media access commands already have filter capability to filter devices that one does not want to scan. Another class of device scanners just use inquiries which are not effected by the passive state (though some could probably use udevinfo and reduce the amount of repeated SCSI inquiries execute on the system. -andmike -- Michael Anderson andmike@xxxxxxxxxxxxxxxxxx - 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
