From: jthumshirn@suse.de (Johannes Thumshirn)
Subject: [PATCH] nvmet: preserve controller serial number between reboots
Date: Thu, 13 Jul 2017 14:52:12 +0200 [thread overview]
Message-ID: <20170713125212.GI5212@linux-x5ow.site> (raw)
In-Reply-To: <d32c32f6-3f8f-c63a-f961-ee16407c2fd6@grimberg.me>
On Thu, Jul 13, 2017@03:30:39PM +0300, Sagi Grimberg wrote:
> It seems weird that a subsystem has a serial.
The subsystem is more of a hack I admit. But we don't maintain
configurations for controllers in configfs, do we?
> I'm not sure that a dynamic controller should maintain
> a serial. Dynamic controllers by definition are allocated
> on demand with no state of prior associations. But not sure
> if a serial is a state (it probably isn't). The area is a little
> fuzzy for me.
I'm not certain as well, the only thing I know for sure currently is,
it changes but we use in the standard 60-persistent-storage.rules [1]
as a part of /dev/disk/by-id/nvme-$model-$serial-part%n [2] and I have a bit
of a headace when users use it to identify their partitions in say /etc/fstab
and the link changes as the target generated serial changes.
Maybe we should consider this more as an RFD than a patch.
I'm happy to withdraw if we find a better solution.
[1] https://github.com/systemd/systemd/blob/master/rules/60-persistent-storage.rules
[2] https://github.com/systemd/systemd/blob/master/rules/60-persistent-storage.rules#L27
Thanks,
Johannes
--
Johannes Thumshirn Storage
jthumshirn at suse.de +49 911 74053 689
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 N?rnberg
GF: Felix Imend?rffer, Jane Smithard, Graham Norton
HRB 21284 (AG N?rnberg)
Key fingerprint = EC38 9CAB C2C4 F25D 8600 D0D0 0393 969D 2D76 0850
WARNING: multiple messages have this Message-ID (diff)
From: Johannes Thumshirn <jthumshirn@suse.de>
To: Sagi Grimberg <sagi@grimberg.me>
Cc: Christoph Hellwig <hch@lst.de>,
Keith Busch <keith.busch@intel.com>,
mwilck@suse.de,
Linux Kernel Mailinglist <linux-kernel@vger.kernel.org>,
Linux NVMe Mailinglist <linux-nvme@lists.infradead.org>
Subject: Re: [PATCH] nvmet: preserve controller serial number between reboots
Date: Thu, 13 Jul 2017 14:52:12 +0200 [thread overview]
Message-ID: <20170713125212.GI5212@linux-x5ow.site> (raw)
In-Reply-To: <d32c32f6-3f8f-c63a-f961-ee16407c2fd6@grimberg.me>
On Thu, Jul 13, 2017 at 03:30:39PM +0300, Sagi Grimberg wrote:
> It seems weird that a subsystem has a serial.
The subsystem is more of a hack I admit. But we don't maintain
configurations for controllers in configfs, do we?
> I'm not sure that a dynamic controller should maintain
> a serial. Dynamic controllers by definition are allocated
> on demand with no state of prior associations. But not sure
> if a serial is a state (it probably isn't). The area is a little
> fuzzy for me.
I'm not certain as well, the only thing I know for sure currently is,
it changes but we use in the standard 60-persistent-storage.rules [1]
as a part of /dev/disk/by-id/nvme-$model-$serial-part%n [2] and I have a bit
of a headace when users use it to identify their partitions in say /etc/fstab
and the link changes as the target generated serial changes.
Maybe we should consider this more as an RFD than a patch.
I'm happy to withdraw if we find a better solution.
[1] https://github.com/systemd/systemd/blob/master/rules/60-persistent-storage.rules
[2] https://github.com/systemd/systemd/blob/master/rules/60-persistent-storage.rules#L27
Thanks,
Johannes
--
Johannes Thumshirn Storage
jthumshirn@suse.de +49 911 74053 689
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: Felix Imendörffer, Jane Smithard, Graham Norton
HRB 21284 (AG Nürnberg)
Key fingerprint = EC38 9CAB C2C4 F25D 8600 D0D0 0393 969D 2D76 0850
next prev parent reply other threads:[~2017-07-13 12:52 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-13 10:48 [PATCH] nvmet: preserve controller serial number between reboots Johannes Thumshirn
2017-07-13 10:48 ` Johannes Thumshirn
2017-07-13 12:30 ` Sagi Grimberg
2017-07-13 12:30 ` Sagi Grimberg
2017-07-13 12:52 ` Johannes Thumshirn [this message]
2017-07-13 12:52 ` Johannes Thumshirn
2017-07-13 13:06 ` Christoph Hellwig
2017-07-13 13:06 ` Christoph Hellwig
2017-07-13 13:11 ` Johannes Thumshirn
2017-07-13 13:11 ` Johannes Thumshirn
2017-07-13 16:38 ` Sagi Grimberg
2017-07-13 16:38 ` Sagi Grimberg
2017-07-13 17:17 ` Christoph Hellwig
2017-07-13 17:17 ` Christoph Hellwig
2017-07-13 15:08 ` Martin Wilck
2017-07-13 15:08 ` Martin Wilck
2017-07-13 15:16 ` Christoph Hellwig
2017-07-13 15:16 ` Christoph Hellwig
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=20170713125212.GI5212@linux-x5ow.site \
--to=jthumshirn@suse.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.