From: Chris Webb <chris@arachsys.com>
To: James Bottomley <James.Bottomley@suse.de>
Cc: Arkadiusz Miskiewicz <a.miskiewicz@gmail.com>,
linux-scsi@vger.kernel.org,
Arjan van de Ven <arjan@infradead.org>
Subject: Re: scsi_wait_scan not working (2.6.30.5)
Date: Wed, 26 Aug 2009 17:23:01 +0100 [thread overview]
Message-ID: <20090826162301.GA2877@arachsys.com> (raw)
In-Reply-To: <1251301226.4205.10.camel@mulgrave.site>
James Bottomley <James.Bottomley@suse.de> writes:
> The way it's supposed to work is that you listen for the uevent that
> signals the sd binding is complete, so you actually get notice
> asynchronously. The event carries device information with it. udev
> uses the node information to send VPD inquiries, which is how it does
> the by-id and by-uuid mappings.
Quite hard to sit down and actually write a shell script to do this, though!
It feels like the operation of logging into an iscsi target, waiting for the
device node and then returning it is something you'd reasonably expect to be
able to do, but it's become quite tricky in this async world. Netlink isn't
at all accessible to scripts, and udevadm doesn't provide a good front-end
to do it either.
When something like a USB device being plugged in, the operation is
fundamentally asynchronous, but with an iscsi login, the device is appearing
because you've run a login command, so it's not completely mad to hope to be
get back the ultimate result of that command, even if you have to wait for
it.
Cheers,
Chris.
prev parent reply other threads:[~2009-08-26 16:23 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-25 19:24 scsi_wait_scan not working (2.6.30.5) Arkadiusz Miskiewicz
2009-08-25 19:28 ` James Bottomley
2009-08-25 19:44 ` Arkadiusz Miskiewicz
2009-08-25 19:47 ` James Bottomley
2009-08-25 20:01 ` Arkadiusz Miskiewicz
2009-08-25 21:22 ` Arkadiusz Miskiewicz
2009-08-25 23:15 ` Alan Stern
2009-08-29 23:27 ` Arkadiusz Miskiewicz
2009-08-30 3:07 ` Alan Stern
2009-08-30 8:12 ` Arkadiusz Miskiewicz
2009-08-30 17:21 ` Alan Stern
2009-08-26 14:34 ` Chris Webb
2009-08-26 15:40 ` James Bottomley
2009-08-26 16:23 ` Chris Webb [this message]
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=20090826162301.GA2877@arachsys.com \
--to=chris@arachsys.com \
--cc=James.Bottomley@suse.de \
--cc=a.miskiewicz@gmail.com \
--cc=arjan@infradead.org \
--cc=linux-scsi@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.