From: "Surekha.PC" <surekhap@cisco.com>
To: linux-hotplug@vger.kernel.org
Subject: RE: udev does not create scsi disk entries during bootup
Date: Mon, 24 Nov 2003 12:50:22 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-106967822222721@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-106870290127081@msgid-missing>
>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 <h> <c> <t> <l>" > /proc/scsi/scsi
echo "scsi remove-single-device <h> <c> <t> <l>" > /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
next prev parent reply other threads:[~2003-11-24 12:50 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-13 5:28 udev does not create scsi disk entries during bootup Surekha.PC
2003-11-13 6:25 ` Greg KH
2003-11-13 8:13 ` Surekha.PC
2003-11-14 1:07 ` Greg KH
2003-11-14 3:55 ` Surekha.PC
2003-11-17 4:54 ` Surekha.PC
2003-11-17 13:02 ` Martin Hicks
2003-11-18 8:23 ` Surekha.PC
2003-11-19 13:48 ` Surekha.PC
2003-11-19 23:57 ` Greg KH
2003-11-20 15:11 ` Surekha.PC
2003-11-20 16:46 ` Greg KH
2003-11-20 16:53 ` Greg KH
2003-11-20 18:38 ` Clay Haapala
2003-11-20 18:41 ` Greg KH
2003-11-20 19:11 ` Clay Haapala
2003-11-21 5:49 ` Surekha.PC
2003-11-21 6:12 ` Greg KH
2003-11-21 6:52 ` Surekha.PC
2003-11-22 18:12 ` Greg KH
2003-11-24 12:50 ` Surekha.PC [this message]
2003-11-24 22:14 ` Greg KH
2003-11-25 12:56 ` Surekha.PC
2003-11-25 13:12 ` Martin Hicks
2003-11-25 13:40 ` Surekha.PC
2003-11-25 16:36 ` Greg KH
2003-11-27 11:36 ` Surekha.PC
2003-12-01 23:59 ` Greg KH
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=marc-linux-hotplug-106967822222721@msgid-missing \
--to=surekhap@cisco.com \
--cc=linux-hotplug@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).