From: Gionatan Danti <g.danti@assyoma.it>
To: linux-hotplug@vger.kernel.org
Subject: udev events for iscsi
Date: Mon, 20 Apr 2020 16:55:52 +0000 [thread overview]
Message-ID: <4a648986b130f48c9125013630473d17@assyoma.it> (raw)
Hi all,
I have a question regarding udev events when using iscsi disks.
By using "udevadm monitor" I can see that events are generated when I
login and logout from an iscsi portal/resource, creating/destroying the
relative links under /dev/
However, I can not see anything when the remote machine simple
dies/reboots/disconnects: while "dmesg" shows the iscsi timeout
expiring, I don't see anything about a removed disk (and the links under
/dev/ remains unaltered, indeed). At the same time, when the remote
machine and disk become available again, no reconnection events happen.
Is this the expected behavior? Can be changed? Should I ping the
linux-scsi list instead?
Thanks.
--
Danti Gionatan
Supporto Tecnico
Assyoma S.r.l. - www.assyoma.it [1]
email: g.danti@assyoma.it - info@assyoma.it
GPG public key ID: FF5F32A8
next reply other threads:[~2020-04-20 16:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-20 16:55 Gionatan Danti [this message]
2020-04-21 15:41 ` udev events for iscsi 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=4a648986b130f48c9125013630473d17@assyoma.it \
--to=g.danti@assyoma.it \
--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 read-only IMAP folder(s) and NNTP newsgroup(s).