From: Keith Busch Date: Thu, 16 May 2019 15:45:34 +0000 (-0600) Subject: Add a note to format on device naming conventions X-Git-Tag: v1.9~61 X-Git-Url: https://www.infradead.org/git/?a=commitdiff_plain;h=d896a878e3450e130641a88009f86c8b5e9ce2dd;p=users%2Fsagi%2Fnvme-cli.git Add a note to format on device naming conventions Provide some help in the documentation on common user pitfalls. Signed-off-by: Keith Busch --- diff --git a/Documentation/nvme-format.txt b/Documentation/nvme-format.txt index 93ee813d..22701bb0 100644 --- a/Documentation/nvme-format.txt +++ b/Documentation/nvme-format.txt @@ -31,11 +31,19 @@ to any namespace with the 'namespace-id' option. If the block device is given, the namespace identifier will default to the namespace id of the block device given, but can be overridden with the same option. +Note, the numeric suffix on the character device, for example the '0' in +/dev/nvme0, does NOT indicate this device handle is the parent controller +of any namespaces with the same suffix. The namespace handle's numeral +may be coming from the subsystem identifier, which is independent of the +controller's identifier. Do not assume any particular device relationship +based on their names. If you do, you may irrevocably erase data on an +unintended device. + On success, the program will automatically issue BLKRRPART ioctl to -force rescanning the namespaces. If the driver is recent enough, this -will automatically update the physical block size. If it is not recent -enough, you will need to remove and rescan your device some other way -for the new block size to be visible. +force rescanning the namespaces. If the driver is recent enough, this will +automatically update the physical block size. If it is not recent enough, +you will need to remove and rescan your device some other way for the +new block size to be visible, if the size was changed with this command. OPTIONS -------