From: Hannes Reinecke <hare@suse.de>
To: Phillip Susi <phill@thesusis.net>
Cc: Simon Kirby <sim@hostway.ca>,
Bart Van Assche <bvanassche@acm.org>,
Damien Le Moal <damien.lemoal@opensource.wdc.com>,
linux-scsi@vger.kernel.org, linux-block@vger.kernel.org
Subject: Re: Unreliable disk detection order in 5.x
Date: Fri, 12 Nov 2021 07:38:41 +0100 [thread overview]
Message-ID: <ebefa00b-12ea-07d0-095a-bbb9ab834a3f@suse.de> (raw)
In-Reply-To: <87pmr65j1i.fsf@vps.thesusis.net>
On 11/12/21 1:11 AM, Phillip Susi wrote:
>
> Hannes Reinecke <hare@suse.de> writes:
>
>> Why is by-uuid not available?
>> The uuid is the disk-internal unique identification, and to my
>> knowledge all recent SCSI and SATA drives implement them.
>> So where is the problem here?
>
> It is probably just an oversight by the udev rules that create the
> by-uuid links.
>
So shouldn't we rather fix this?
Putting in some udev rules is always easier than trying to 'fix' things
in the kernel.
Cheers,
Hannes
--
Dr. Hannes Reinecke Kernel Storage Architect
hare@suse.de +49 911 74053 688
SUSE Software Solutions GmbH, Maxfeldstr. 5, 90409 Nürnberg
HRB 36809 (AG Nürnberg), Geschäftsführer: Felix Imendörffer
prev parent reply other threads:[~2021-11-12 6:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-05 6:46 Unreliable disk detection order in 5.x Simon Kirby
2021-11-05 7:45 ` Damien Le Moal
2021-11-07 2:24 ` Simon Kirby
2021-11-07 19:51 ` Bart Van Assche
2021-11-11 1:01 ` Simon Kirby
2021-11-11 1:16 ` Damien Le Moal
2021-11-11 6:57 ` Hannes Reinecke
2021-11-12 0:11 ` Phillip Susi
2021-11-12 6:38 ` Hannes Reinecke [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=ebefa00b-12ea-07d0-095a-bbb9ab834a3f@suse.de \
--to=hare@suse.de \
--cc=bvanassche@acm.org \
--cc=damien.lemoal@opensource.wdc.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=phill@thesusis.net \
--cc=sim@hostway.ca \
/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