On 10/31/2012 10:32 PM, Michael Christie wrote: > > On Oct 30, 2012, at 7:31 PM, amit.ut...@gmail.com wrote: > >> >> I apologize if this has been asked in the list before, I did some >> research but did not find a clear answer/recommendation. >> >> Currently, I use udev to monitor new devices added by the open-iscsi >> initiator. This works great. However, when the target is disconnected I >> get timeout messages in the kernel log but the device nodes in /dev/ >> still exists. Thus, no udev events. >> >> As noted in a few of the messages in the archives, doing a rescan does >> not automatically delete the LUNs. So the following script was >> suggested: >> >> scsi_sz=`sg_readcap /dev/sdko | grep address | sed s'/.*blocks=//'` >> kernel_sz=`cat /sys/block/sdko/device/block\:sdko/size` >> >> if (($scsi_sz==$kernel_sz)); then >> echo "Good." >> else >> echo "Do the deletion of the block device." >> echo 1 > /sys/block/sdko/device/delete >> fi >> >> This looks like it will do the trick. But I am wondering if this is still >> the recommended approach as the above suggestion was made in 2008. > > I do not know about recommended, but it will work, and we have not > implemented something like dev_loss_tmo FC behavior so it is one of > the only options. >
Mike hi Did we ever consider integrating iscsi with the hotplug infrastructure? It could be nice if an admin could specify at configuration time if he wants the device permanently attached but offline on error like today, or if he wants an hot-unplug notification like a usb device. Thanks Boaz -- You received this message because you are subscribed to the Google Groups "open-iscsi" group. To post to this group, send email to open-iscsi@googlegroups.com. To unsubscribe from this group, send email to open-iscsi+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/open-iscsi?hl=en.
