On Fri, Jun 16, 2017 at 11:48:32AM +0200, Johannes Thumshirn wrote: > On 06/16/2017 11:40 AM, Christoph Hellwig wrote: > > On Fri, Jun 16, 2017 at 10:20:04AM +0200, Johannes Thumshirn wrote: > >> Strange, as I tested with nvme-loop all the time... > > > > Yeah, it's actually there, but for some reason find on sysfs > > behaves strange: > > > > root@testvm:~# find /sys -name uuid > > root@testvm:~# cat /sys/class/nvme/nvme2/nvme2n1/uuid > > 6665a65b-f42f-469b-800e-a047238649eb > > Wasn't there something that find on sysfs isn't reliable?
Looks like it. Which is a pitty. > Anyways, my shock's gone now. Heh. Now we just need the nvme-cli patches to verify it independently :)
