From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753391AbdFPJ6k (ORCPT ); Fri, 16 Jun 2017 05:58:40 -0400 Received: from verein.lst.de ([213.95.11.211]:43405 "EHLO newverein.lst.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753084AbdFPJ6j (ORCPT ); Fri, 16 Jun 2017 05:58:39 -0400 Date: Fri, 16 Jun 2017 11:58:37 +0200 From: Christoph Hellwig To: Johannes Thumshirn Cc: Christoph Hellwig , Sagi Grimberg , Linux Kernel Mailinglist , Linux NVMe Mailinglist , Keith Busch , Hannes Reinecke , Max Gurtovoy Subject: Re: [PATCH v6 00/10] Implement NVMe Namespace Descriptor Identification Message-ID: <20170616095837.GA14217@lst.de> References: <20170607094536.32419-1-jthumshirn@suse.de> <20170615163141.GA27307@lst.de> <20170616094056.GA12465@lst.de> <905ed2e6-1c1c-f3a3-5391-66e42fb61861@suse.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <905ed2e6-1c1c-f3a3-5391-66e42fb61861@suse.de> User-Agent: Mutt/1.5.17 (2007-11-01) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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 :) From mboxrd@z Thu Jan 1 00:00:00 1970 From: hch@lst.de (Christoph Hellwig) Date: Fri, 16 Jun 2017 11:58:37 +0200 Subject: [PATCH v6 00/10] Implement NVMe Namespace Descriptor Identification In-Reply-To: <905ed2e6-1c1c-f3a3-5391-66e42fb61861@suse.de> References: <20170607094536.32419-1-jthumshirn@suse.de> <20170615163141.GA27307@lst.de> <20170616094056.GA12465@lst.de> <905ed2e6-1c1c-f3a3-5391-66e42fb61861@suse.de> Message-ID: <20170616095837.GA14217@lst.de> On Fri, Jun 16, 2017@11:48:32AM +0200, Johannes Thumshirn wrote: > On 06/16/2017 11:40 AM, Christoph Hellwig wrote: > > On Fri, Jun 16, 2017@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 at testvm:~# find /sys -name uuid > > root at 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 :)