From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753372AbdFPJsf (ORCPT ); Fri, 16 Jun 2017 05:48:35 -0400 Received: from mx2.suse.de ([195.135.220.15]:35583 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1753111AbdFPJse (ORCPT ); Fri, 16 Jun 2017 05:48:34 -0400 Subject: Re: [PATCH v6 00/10] Implement NVMe Namespace Descriptor Identification To: Christoph Hellwig Cc: Sagi Grimberg , Linux Kernel Mailinglist , Linux NVMe Mailinglist , Keith Busch , Hannes Reinecke , Max Gurtovoy References: <20170607094536.32419-1-jthumshirn@suse.de> <20170615163141.GA27307@lst.de> <20170616094056.GA12465@lst.de> From: Johannes Thumshirn Message-ID: <905ed2e6-1c1c-f3a3-5391-66e42fb61861@suse.de> Date: Fri, 16 Jun 2017 11:48:32 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.1.1 MIME-Version: 1.0 In-Reply-To: <20170616094056.GA12465@lst.de> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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? Anyways, my shock's gone now. -- Johannes Thumshirn Storage jthumshirn@suse.de +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 From mboxrd@z Thu Jan 1 00:00:00 1970 From: jthumshirn@suse.de (Johannes Thumshirn) Date: Fri, 16 Jun 2017 11:48:32 +0200 Subject: [PATCH v6 00/10] Implement NVMe Namespace Descriptor Identification In-Reply-To: <20170616094056.GA12465@lst.de> References: <20170607094536.32419-1-jthumshirn@suse.de> <20170615163141.GA27307@lst.de> <20170616094056.GA12465@lst.de> Message-ID: <905ed2e6-1c1c-f3a3-5391-66e42fb61861@suse.de> 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? Anyways, my shock's gone now. -- Johannes Thumshirn Storage jthumshirn at suse.de +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