namespace reconfigure doesn't work as documentation

[EthanZHF]

ndctl version v64.1 kernel version v4.17.5 There are a lot of namespaces created on region 1, and I tried to reconfigure one namespace with specified namspace name and uuid as following doc said https://docs.pmem.io/ndctl-users-guide/troubleshooting

ndctl list -N

{ "dev":"namespace0.0", "mode":"raw", "size":1054867456, "uuid":"ce15f005-d3bd-4a94-8565-55be77bed6f6", "sector_size":512, "blockdev":"pmem0", "numa_node":0 }

ndctl disable-namespace namespace0.0

disabled 1 namespace

ndctl create-namespace -e namespace0.0 -m fsdax -u "ce15f005-d3bd-4a94-8565-55be77bed6f6"

{ "dev":"namespace0.22", "mode":"fsdax", "map":"dev", "size":"1054867456", "uuid":"f45a6725-b80e-4174-a366-b07c91e66a58", "sector_size":512, "blockdev":"pmem0", "numa_node":0 }

But the ndctl still created another namespace with different dev name and different uuid for me, Seems ndctl destroyed the original namespace and created a new one for me though I specified the namespace0.0 and the uuid "ce15f005-d3bd-4a94-8565-55be77bed6f6", Is it a bug of ndctl or kernel driver issue ? Or there is something as premise I missed ?

Thanks, Ethan

[djbw]

Can you reproduce with the 4.19 long-term-stable kernel? The 4.17 kernel has ceased development since August of last year.

[stellarhopper]

Can you list the namespace using:

ndctl list -v --namespace=namespace0.22

I think the uuid supplied by '-u' to create namespace ends up as the 'raw_uuid'

On Thu, Apr 11, 2019 at 8:43 AM Dan Williams notifications@github.com wrote:

Can you reproduce with the 4.19 long-term-stable kernel? The 4.17 kernel has ceased development since August of last year.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/pmem/ndctl/issues/95#issuecomment-482143988, or mute the thread https://github.com/notifications/unsubscribe-auth/ABBRF_j7FOenI-rv6YyBdKZreFWQUU1Vks5vf0oYgaJpZM4co89G .

[EthanZHF]

Can you reproduce with the 4.19 long-term-stable kernel? The 4.17 kernel has ceased development since August of last year.

Yes， I am managing to reproduce it with 4.19 once get a server with AEP populated and give the feedback to you .

[EthanZHF]

I think the uuid supplied by '-u' to create namespace ends up as the 'raw_uuid' Will verify that once get a box with AEP again.

[EthanZHF]

I built and installed a LTS 4.19.34 kernel then reproduced the same result as following: Linux version 4.19.34 ndctl -v 64.1

ndctl list -NRi

 .......
    {
      "dev":"namespace1.135",
      "mode":"devdax",
      "map":"dev",
      "size":1054867456,
      "uuid":"2241de9d-65ee-4b9a-8947-ca371372bf31",
      "raw_uuid":"ba0d89df-7015-4578-830b-d9b1616d62d5",
      "daxregion":{
        "id":1,
        "size":1054867456,
        "align":2097152,
        "devices":[
          {
            "chardev":"dax1.135",
            "size":1054867456
          }
        ]
      },
      "align":2097152,
      "name":"test1455",
      "numa_node":1,
      "supported_alignments":[
        4096,
        2097152,
        1073741824
      ]
    }
  ]
},

ndctl create-namespace --reconfig=namespace1.135 -u "2241de9d-65ee-4b9a-8947-ca371372bf31" -m fsdax --force

{ "dev":"namespace1.470", "mode":"fsdax", "map":"dev", "size":"1006.00 MiB (1054.87 MB)", "uuid":"92924a55-1148-4dd5-8a0b-73da023df744", "sector_size":512, "align":2097152, "blockdev":"pmem1.470", "name":"test1455" }

It created a new namespace of "namespace1.470" with raw_uuid of "2241de9d-65ee-4b9a-8947-ca371372bf31"

[root@localhost ndctl]# ndctl list -v --namespace namespace1.470 [ { "dev":"namespace1.470", "mode":"fsdax", "map":"dev", "size":1054867456, "uuid":"92924a55-1148-4dd5-8a0b-73da023df744", "raw_uuid":"2241de9d-65ee-4b9a-8947-ca371372bf31", "sector_size":512, "align":2097152, "blockdev":"pmem1.470", "name":"test1455", "numa_node":1, "supported_alignments":[ 4096, 2097152, 1073741824 ] } ]

If any other information needed, feel free let me know.

Thanks, Ethan