From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Surekha.PC" Date: Mon, 24 Nov 2003 12:50:22 +0000 Subject: RE: udev does not create scsi disk entries during bootup Message-Id: List-Id: References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: linux-hotplug@vger.kernel.org >The 'tree' function is much nicer for seeing things like this :) Is this a utility? Appreciate if you can inform me where to get it. >> Here sda, sdb are my native scsi disks while sdc, sdd are iSCSI disks. >Why is your iscsi host controller haning off of the legacy bus? Isn't it connected to a >ethernet device in reality? You should link it to that. iSCSI is a pseudo SCSI HBA, it is registered with Scsi_Host template just like any native SCSI HBA. Since there isn't any pci bus associated with it, it appears on legacy bus. >> I am able to manually create the device nodes for iSCSI disks with >> udev. >> >> Making udev work with hotplug is the only issue now :( >Don't know why it isn't working for you. Does any other devices work >with hotplug? What distro are you using? Can you install the hotplug >rpms instead of using the tarballs? I have native scsi disk devices on my system. These are not tested for hotplugging since it requires to build udev with initrd, which I am yet to test with. I am using Redhat 9.0 with linux-kernel 2.6.0-test5. I was not able to install from rpm, rpm on 2.6 kernel has an issue, it gives following error and fails... That's another issue. ------------------------------------------------------------------------ -------------- rpmdb: unable to join the environment error: db4 error(11) from dbenv->open: Resource temporarily unavailable error: cannot open Packages index using db3 - Resource temporarily unavailable (11) error: cannot open Packages database in /var/lib/rpm ------------------------------------------------------------------------ -------------- I have one more query. I happened to read from the URL mentioned below, that hotplugging can be achieved by plugging/unplugging the scsi device and executing the following command. echo "scsi add-single-device " > /proc/scsi/scsi echo "scsi remove-single-device " > /proc/scsi/scsi h - host number c - channel t - target l - lun http://lwn.net/Articles/12723/ Hope this is not all about scsi hotplugging ? I presume that hotplugging should not take any user input and should be completely automated. Thanks, surekha ------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ _______________________________________________ Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net Linux-hotplug-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel