Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1329161
| From | Hannes Reinecke <hare@suse.de> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: complete boot failure in 4.5-rc1 caused by nvme: make SG_IO support optional |
| Date | 2016-02-08 16:20 +0100 |
| Message-ID | <qZVLA-74r-11@gated-at.bofh.it> (permalink) |
| References | (4 earlier) <qZGCS-4Wf-29@gated-at.bofh.it> <qZOAq-22G-7@gated-at.bofh.it> <qZQVA-3NI-5@gated-at.bofh.it> <qZR5f-3R9-5@gated-at.bofh.it> <qZVLA-74r-13@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On 02/08/2016 04:12 PM, Keith Busch wrote: > On Mon, Feb 08, 2016 at 11:13:50AM +0100, Christoph Hellwig wrote: >> On Mon, Feb 08, 2016 at 12:01:16PM +0200, Sagi Grimberg wrote: >>> >>>> Do we have defined sysfs attributes for NVMe devices nowadays? >>> >>> /sys/block/nvme0n1/uuid >> >> That's only supported for NVMe 1.1 and higher devices, and optional. >> For older or stupid devices we need to support the algorithm based >> on the serial attribute from nvme_fill_device_id_scsi_string() in >> drivers/nvme/host/scsi.c. > > It's even worse. NGUID was defined for 1.2 devices and higher. 1.1 > devices should have EUI-64 at: > > /sys/block/nvmeXnY/eui > > 1.2 devices will have either uuid or eui (or both). > > The majority of devices in circulation today are 1.0, and need to concat > these three entries to make a unique identifier: > > /sys/block/nvmeXnY/device/serial > /sys/block/nvmeXnY/device/model > /sys/block/nvmeXnY/nsid Ok, so what about having a 'wwid' attribute which provides combined information (like scsi has)? Cheers, Hannes -- Dr. Hannes Reinecke Teamlead Storage & Networking hare@suse.de +49 911 74053 688 SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg GF: F. Imendörffer, J. Smithard, J. Guild, D. Upmanyu, G. Norton HRB 21284 (AG Nürnberg)
Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
complete boot failure in 4.5-rc1 caused by nvme: make SG_IO support optional James Bottomley <James.Bottomley@HansenPartnership.com> - 2016-02-06 19:40 +0100
Re: complete boot failure in 4.5-rc1 caused by nvme: make SG_IO support optional Christoph Hellwig <hch@lst.de> - 2016-02-07 10:30 +0100
Re: complete boot failure in 4.5-rc1 caused by nvme: make SG_IO support optional James Bottomley <James.Bottomley@HansenPartnership.com> - 2016-02-07 17:10 +0100
Re: complete boot failure in 4.5-rc1 caused by nvme: make SG_IO support optional Jens Axboe <axboe@kernel.dk> - 2016-02-07 23:30 +0100
Re: complete boot failure in 4.5-rc1 caused by nvme: make SG_IO support optional James Bottomley <James.Bottomley@HansenPartnership.com> - 2016-02-08 00:10 +0100
Re: complete boot failure in 4.5-rc1 caused by nvme: make SG_IO support optional Christoph Hellwig <hch@lst.de> - 2016-02-08 08:30 +0100
Re: complete boot failure in 4.5-rc1 caused by nvme: make SG_IO support optional Hannes Reinecke <hare@suse.de> - 2016-02-08 08:40 +0100
Re: complete boot failure in 4.5-rc1 caused by nvme: make SG_IO support optional Sagi Grimberg <sagig@dev.mellanox.co.il> - 2016-02-08 11:10 +0100
Re: complete boot failure in 4.5-rc1 caused by nvme: make SG_IO support optional Christoph Hellwig <hch@lst.de> - 2016-02-08 11:20 +0100
Re: complete boot failure in 4.5-rc1 caused by nvme: make SG_IO support optional Hannes Reinecke <hare@suse.de> - 2016-02-08 16:20 +0100
Re: complete boot failure in 4.5-rc1 caused by nvme: make SG_IO support optional Keith Busch <keith.busch@intel.com> - 2016-02-08 17:20 +0100
Re: complete boot failure in 4.5-rc1 caused by nvme: make SG_IO support optional Keith Busch <keith.busch@intel.com> - 2016-02-08 16:20 +0100
Re: complete boot failure in 4.5-rc1 caused by nvme: make SG_IO support optional James Bottomley <James.Bottomley@HansenPartnership.com> - 2016-02-08 16:30 +0100
Re: complete boot failure in 4.5-rc1 caused by nvme: make SG_IO support optional Hannes Reinecke <hare@suse.de> - 2016-02-08 08:30 +0100
csiph-web