Improve readbility of NVME "wwid" attribute
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest0 of 3 patches 0 repliesNew
Patches in v1 No applies recorded yet
None of the 3 patches the cover letter announces are in this archive.
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH 0/3] Improve readbility of NVME "wwid" attribute
Quoted 11 lines · Christoph Hellwig
Quoted 10 lines · Martin Wilck
With the current implementation, the default "fallback" WWID generation
code (if no nguid, euid etc. are defined) for Linux NVME host and target
results in the following WWID format:nvme.0000-3163653363666438366239656630386200- 4c696e7578000000000000000000000000000000000000000000000000000000000 0000000000000-00000002
Quoted 6 lines
Quoted 4 lines
This is not only hard to read, it poses real problems for multipath (dm WWIDs are limited to 128 characters), and it's not fully standards
compliant.What standard? The wwid field is a Linux invention.
I was referring to patch 1/3 in the series, the Linux target padding the "model" string with 0-bytes, which is not allowed.
Regards
Martin
Signature · 3 lines
Dr. Martin Wilck <mwilck at suse.com>, Tel. +49 (0)911 74053 2107 SUSE Linux GmbH, GF: Felix Imend?rffer, Jane Smithard, Graham Norton HRB 21284 (AG N?rnberg)