From: Stan Hoeppner <stan@hardwarefreak.com>
To: "Dorau, Lukasz" <lukasz.dorau@intel.com>,
"linux-raid@vger.kernel.org" <linux-raid@vger.kernel.org>
Cc: "Baldysiak, Pawel" <pawel.baldysiak@intel.com>
Subject: Re: What can be used instead of /dev/disk/by-path/* symlinks?
Date: Tue, 17 Dec 2013 06:43:35 -0600 [thread overview]
Message-ID: <52B046F7.3070800@hardwarefreak.com> (raw)
In-Reply-To: <D9FFE20C522965449E182ACE73889AEB1A69A280@IRSMSX105.ger.corp.intel.com>
On 12/17/2013 4:02 AM, Dorau, Lukasz wrote:
> On Tuesday, December 17, 2013 10:41 AM Neil Brown (neilb@suse.de) wrote:
>> On Tue, 17 Dec 2013 09:10:44 +0000 "Dorau, Lukasz" <lukasz.dorau@intel.com>
>> wrote:
>>
> [...]
>> Personally, I really don't care. Does anyone know what udev changed? Maybe
>> we should ask udev developers to change it back.
>>
>> NeilBrown
>>
>
> udev developers wrote:
> http://cgit.freedesktop.org/systemd/systemd/tree/src/udev/udev-builtin-path_id.c#n378
>
> /*
> * We do not support the ATA transport class, it uses global counters
> * to name the ata devices which numbers spread across multiple
> * controllers.
> *
> * The real link numbers are not exported. Also, possible chains of ports
> * behind port multipliers cannot be composed that way.
> *
> * Until all that is solved at the kernel level, there are no by-path/
> * links for ATA devices.
> */
I think you should be using libata instead of the old IDE drivers.
Doing so should avoid this problem, if I'm understanding it correctly.
--
Stan
next prev parent reply other threads:[~2013-12-17 12:43 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
2013-12-17 10:02 ` Dorau, Lukasz
2013-12-17 12:43 ` Stan Hoeppner [this message]
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=52B046F7.3070800@hardwarefreak.com \
--to=stan@hardwarefreak.com \
--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).