From: Andrey Borzenkov <arvidjaar@mail.ru>
To: linux-hotplug@vger.kernel.org
Subject: Re: More consistent /dev/ mapping for ISCSI volumes in udev.
Date: Tue, 06 Apr 2010 02:41:24 +0000 [thread overview]
Message-ID: <201004060641.31887.arvidjaar@mail.ru> (raw)
In-Reply-To: <C7DF7361.26928%mikeely@amyskitchen.net>
[-- Attachment #1: Type: Text/Plain, Size: 1364 bytes --]
On Monday 05 of April 2010 22:28:14 Mike Ely wrote:
> On 4/5/10 11:15 AM, "Andrey Borzenkov" <arvidjaar@mail.ru> wrote:
> > On Monday 05 of April 2010 22:00:49 Mike Ely wrote:
> >> (resending because our clunky old MTA doesn¹t know how to handle
> >> greylisting)
> >>
> >> I'm wondering how to get open-iscsi and udev folks to work
> >> together on a good solution for getting ISCSI volumes to map
> >> consistently to a /dev/ entry. What would be a good starting
> >> point for getting the discussion going? Currently the only
> >> solutions I can find are some scripting tricks, but it¹d be nice
> >> to see something a bit more integrated. Not all use cases
> >> support filesystem labels.
> >
> > udev already includes path_id that generates persistent name for
> > iSCSI device. Could you be more specific what exactly it misses?
>
> I'm not sure how to get path_id to work then. Here's an example of
> it not working through several remounts on RHEL 5 - look at the
> number of partitions in each volume to see how it's randomly
> remapping:
>
path_id is used to generate persistent link under /dev/disk/by-path. sdX
are not guaranteed to be persistent.
> iqn.2001-05.com.equallogic:0-8a0906-4f489fb03-3c60003e5c34bb68-delete
> me, portal: 10.1.xx.xx,3260]
I always find obfuscating of private addresses amusing :)
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
prev parent reply other threads:[~2010-04-06 2:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-05 18:00 More consistent /dev/ mapping for ISCSI volumes in udev Mike Ely
2010-04-05 18:15 ` Andrey Borzenkov
2010-04-05 18:28 ` Mike Ely
2010-04-06 2:41 ` Andrey Borzenkov [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=201004060641.31887.arvidjaar@mail.ru \
--to=arvidjaar@mail.ru \
--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).