From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Paul Menzel <pmenzel@molgen.mpg.de>
Cc: "Martin K. Petersen" <martin.petersen@oracle.com>,
linux-scsi@vger.kernel.org, dvteam@molgen.mpg.de
Subject: Re: Ordering problems with 3ware controller
Date: Thu, 10 Nov 2016 08:59:21 -0500 [thread overview]
Message-ID: <yq11syjo2py.fsf@sermon.lab.mkp.net> (raw)
In-Reply-To: <49d06c24-24a0-e0fa-0cae-af8ea79a38e0@molgen.mpg.de> (Paul Menzel's message of "Wed, 9 Nov 2016 10:08:37 +0100")
>>>>> "Paul" == Paul Menzel <pmenzel@molgen.mpg.de> writes:
Paul,
>> Linux does not provide device discovery ordering guarantees. You need
>> to fix your scripts to use UUIDs, filesystem labels, or DM devices to
>> get stable naming.
Paul> Indeed. But it worked for several years, so that *something* must
Paul> have changed that the ordering of the result of `getdents64` is
Paul> different now.
Could be changes in the PCI or platform code that causes things to be
enumerated differently. Whatever it is, it has nothing to do with the
3ware drivers themselves since they have been dormant for a long time.
Paul> Fixing the scripts is unfortunately not that easy, as `tw_cli` is
Paul> a proprietary tool [1], and we do not have the sources. It does a
Paul> `readdir()`.
That's beside the point. Whatever you are doing that needs to address a
specific physical controller needs to use a different scheme than
discovery order to do so. Don't know if these cards provide a device
identification VPD or something with a serial number that you could key
off of?
--
Martin K. Petersen Oracle Linux Engineering
next prev parent reply other threads:[~2016-11-10 13:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-08 10:07 Ordering problems with 3ware controller Paul Menzel
2016-11-08 11:09 ` Paul Menzel
2016-11-08 23:45 ` Martin K. Petersen
2016-11-09 9:08 ` Paul Menzel
2016-11-10 13:59 ` Martin K. Petersen [this message]
2016-11-16 21:24 ` Donald Buczek
2016-11-17 14:55 ` Paul Menzel
2016-11-17 19:55 ` Donald Buczek
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=yq11syjo2py.fsf@sermon.lab.mkp.net \
--to=martin.petersen@oracle.com \
--cc=dvteam@molgen.mpg.de \
--cc=linux-scsi@vger.kernel.org \
--cc=pmenzel@molgen.mpg.de \
/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.