i agree that is a very long name , given this is a nvme device it should show up as /dev/nvmeXYZ i suggest to report exactly that in nsddevices and retry. i vaguely remember we have some fixed length device name limitation , but i don't remember what the length is, so this would be my first guess too that the long name is causing trouble.
On Thu, Dec 29, 2016 at 5:02 PM Aaron Knister <[email protected]> wrote: > Interesting. Thanks Matt. I admit I'm somewhat grasping at straws here. > > That's a *really* long device path (and nested too), I wonder if that's > causing issues. > > What does a "tspreparedisk -S" show on that node? > > Also, what does your nsddevices script look like? I'm wondering if you > could have it give back "/dev/dm-XXX" paths instead of "/dev/disk/by-id" > paths if that would help things here. > > -Aaron > > On 12/29/16 10:57 AM, Matt Weil wrote: > > > > > >> ro_cache_S29GNYAH200016 0A6403AA586531E1 > >> > /dev/disk/by-id/nvme-Dell_Express_Flash_NVMe_SM1715_1.6TB_SFF_______S29GNYAH200016 > >> dmm ces1.gsc.wustl.edu server node > > > > > > On 12/28/16 5:19 PM, Aaron Knister wrote: > >> mmlssnsd -X | grep 0A6403AA58641546 > > > > _______________________________________________ > > gpfsug-discuss mailing list > > gpfsug-discuss at spectrumscale.org > > http://gpfsug.org/mailman/listinfo/gpfsug-discuss > > > > -- > Aaron Knister > NASA Center for Climate Simulation (Code 606.2) > Goddard Space Flight Center > (301) 286-2776 > _______________________________________________ > gpfsug-discuss mailing list > gpfsug-discuss at spectrumscale.org > http://gpfsug.org/mailman/listinfo/gpfsug-discuss >
_______________________________________________ gpfsug-discuss mailing list gpfsug-discuss at spectrumscale.org http://gpfsug.org/mailman/listinfo/gpfsug-discuss
