Ok.. for Namespacing (partitioning) - All commands must be SUDO/Root below
I recommend outputting to a file the following so you know how the factory NS was made. Note Ensure you have rebooted since a firmware upgrade
nvme id-ns /dev/nvme0 -n 1 -H > nsoutput.txt
# delete existing namespace, assuming this is factory, there is 1 NS, #1
nvme delete-ns /dev/nvme0 -n 1
# create partition (replace BLOCK Count with the amount of space in bytes, divided by the block size (set with the -f, in this example 4K), all
# parameter information is on the output you did above so you know the options
nvme create-ns /dev/nvme0 -s BLOCKCOUNT -c BLOCKCOUNT -f 2 -d 0 -m 1
# It will return a ns-id, starting with 1 (-n paramter) and you attach to controller (do an nvme id-ctrl /dev/nvme0 -H ) to get the controller id (cntl-id)
nvme attach-ns /dev/nvme0 -n 1 -c 0x21
And there you have a new namespace setup to the size you want. It won't let you assign more space than the drive has
If possible, after upgrading from the OLD OLD factory firmware, move the data to another drive, and re-namespace the drive (this also does a "quick format", of the space)
Hope this all helps some from what I learned the last cpl weeks about these incredible cards!
Christine
Wondering if you can help. I deleted the existing namespace but cant create ns. And now can't even see the drive anymore. Here is the nsoutput.txt. Any help would be much appreciated. I also tried moving it on a Windows machine and it sees the driver but I cant access it.
NVME Identify Namespace 1:
nsze : 0x2e93432b0
ncap : 0x2e93432b0
nuse : 0x2e93432b0
nsfeat : 0
[2:2] : 0 Deallocated or Unwritten Logical Block error Not Supported
[1:1] : 0 Namespace uses AWUN, AWUPF, and ACWU
[0:0] : 0 Thin Provisioning Not Supported
nlbaf : 3
flbas : 0x10
[4:4] : 0x1 Metadata Transferred at End of Data LBA
[3:0] : 0 Current LBA Format Selected
mc : 0x3
[1:1] : 0x1 Metadata Pointer Supported
[0:0] : 0x1 Metadata as Part of Extended Data LBA Supported
dpc : 0x1f
[4:4] : 0x1 Protection Information Transferred as Last 8 Bytes of Metadata Supported
[3:3] : 0x1 Protection Information Transferred as First 8 Bytes of Metadata Supported
[2:2] : 0x1 Protection Information Type 3 Supported
[1:1] : 0x1 Protection Information Type 2 Supported
[0:0] : 0x1 Protection Information Type 1 Supported
dps : 0
[3:3] : 0 Protection Information is Transferred as Last 8 Bytes of Metadata
[2:0] : 0 Protection Information Disabled
nmic : 0x1
[0:0] : 0x1 Namespace Multipath Capable
rescap : 0x7f
[6:6] : 0x1 Exclusive Access - All Registrants Supported
[5:5] : 0x1 Write Exclusive - All Registrants Supported
[4:4] : 0x1 Exclusive Access - Registrants Only Supported
[3:3] : 0x1 Write Exclusive - Registrants Only Supported
[2:2] : 0x1 Exclusive Access Supported
[1:1] : 0x1 Write Exclusive Supported
[0:0] : 0x1 Persist Through Power Loss Supported
fpi : 0x80
[7:7] : 0x1 Format Progress Indicator Supported
[6:0] : 0 Format Progress Indicator (Remaining 100%)
nawun : 0
nawupf : 0
nacwu : 0
nabsn : 0
nabo : 0
nabspf : 0
noiob : 0
nvmcap : 6401252745216
nguid : 343539304b9002360025384100000004
eui64 : 002538e9810000ec
LBA Format 0 : Metadata Size: 0 bytes - Data Size: 512 bytes - Relative Performance: 0x1 Better (in use)
LBA Format 1 : Metadata Size: 8 bytes - Data Size: 512 bytes - Relative Performance: 0x3 Degraded
LBA Format 2 : Metadata Size: 0 bytes - Data Size: 4096 bytes - Relative Performance: 0 Best
LBA Format 3 : Metadata Size: 8 bytes - Data Size: 4096 bytes - Relative Performance: 0x2 Good