From: "Alibek A." <alibek.a@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: Block device naming
Date: Thu, 9 May 2019 23:43:57 +0300 [thread overview]
Message-ID: <20190509234357.24025f65@tamaverik> (raw)
Hi!
I want to address the following problem:
On the system with hot-attached new storage volume, such as FC-switch update configuration for connected FC-HBA on servers, linux kernel reorder block devices and change names of block devices. Becouse scsi-id, wwn-id and other is a symbol links to block device names than on change block device name change path to device.
This causes the server to stop working.
For example, on server present ZFS pool with attached device by scsi-id
# zpool status
pool: pool
state: ONLINE
scan: scrub repaired 0 in 1h39m with 0 errors on Sun Oct 8 02:03:34 2017
config:
NAME STATE READ WRITE CKSUM
pool ONLINE 0 0 0
scsi-3600144f0c7a5bc61000058d3b96d001d ONLINE 0 0 0
Before export new block device from storage to hba, scsi-id have next path to device:
/dev/disk/by-id/scsi-3600144f0c7a5bc61000058d3b96d001d -> ../../sdd
When added new block device by FC-switch, FC-HBA kernel change block device names:
/dev/disk/by-id/scsi-3600144f0c7a5bc61000058d3b96d001d -> ../../sdf
and ZFS can't access to device until reboot (partprobe, zpool online -e pool scsi-3600144f0c7a5bc61000058d3b96d001d - may help or may not help)
Is there any way to fix or change this behavior of the kernel?
It may be more reasonable to immediately assign an unique persistent identifier of device and linking other identifiers with it?
With regards, Alibek!
next reply other threads:[~2019-05-09 20:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-09 20:43 Alibek A. [this message]
2019-05-15 11:46 ` Block device naming Alibek Amaev
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=20190509234357.24025f65@tamaverik \
--to=alibek.a@gmail.com \
--cc=linux-kernel@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