On Wed, Sep 20, 2017 at 04:55:46PM +0200, Christoph Hellwig wrote: > On Wed, Sep 20, 2017 at 01:09:59PM +0200, Johannes Thumshirn wrote: > > Using your patchset and doing the sanme double connect trick I get the same > > two block devices of cause. > > > > How do I connect using both paths? > > Same as above. But now in addition to the /dev/nvmeXnY devices you > should also see a /dev/nvme/nsZ device. The sysfs entry for it shows > which paths it belongs to. Ah OK, we maybe should update nvme-cli to recognize it as well then. I just looked at the output of nvme list and obviously didn't find it. -- Johannes Thumshirn Storage jthumshirn@xxxxxxx +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
