From: NeilBrown <neilb@suse.de>
To: "Dorau, Lukasz" <lukasz.dorau@intel.com>
Cc: "linux-raid@vger.kernel.org" <linux-raid@vger.kernel.org>,
"Baldysiak, Pawel" <pawel.baldysiak@intel.com>
Subject: Re: What can be used instead of /dev/disk/by-path/* symlinks?
Date: Tue, 17 Dec 2013 20:40:55 +1100 [thread overview]
Message-ID: <20131217204055.353e5970@notabene.brown> (raw)
In-Reply-To: <D9FFE20C522965449E182ACE73889AEB1A69A1E3@IRSMSX105.ger.corp.intel.com>
[-- Attachment #1: Type: text/plain, Size: 959 bytes --]
On Tue, 17 Dec 2013 09:10:44 +0000 "Dorau, Lukasz" <lukasz.dorau@intel.com>
wrote:
> Hi Neil,
I'd really rather people addressed thing to the list, not just to me. There
are many competent and interested people here other than me, and you
should expect them to have an opinion and ask for it.
Personally, I really don't care. Does anyone know what udev changed? Maybe
we should ask udev developers to change it back.
NeilBrown
>
> The /dev/disk/by-path/* symlinks are not created for ATA devices in systems using systemd v182+, so mdadm cannot use them in case of policies and udev rules (mdadm -If --path=...)
>
> What do you think - what should be used instead? The symlinks from /sys/block/* ?
>
> Regards,
> Lukasz
> --
> To unsubscribe from this list: send the line "unsubscribe linux-raid" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
next prev parent reply other threads:[~2013-12-17 9:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-17 9:10 What can be used instead of /dev/disk/by-path/* symlinks? Dorau, Lukasz
2013-12-17 9:40 ` NeilBrown [this message]
2013-12-17 10:02 ` Dorau, Lukasz
2013-12-17 12:43 ` Stan Hoeppner
2014-01-07 22:39 ` Dan Williams
2013-12-17 9:53 ` Dimitri John Ledkov
2013-12-17 10:08 ` Dorau, Lukasz
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=20131217204055.353e5970@notabene.brown \
--to=neilb@suse.de \
--cc=linux-raid@vger.kernel.org \
--cc=lukasz.dorau@intel.com \
--cc=pawel.baldysiak@intel.com \
/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).