NVMe namespace notes:

 Just a bunch of notes for my future self, as I am sure I will forget, and for anyone else who may benefit. 

What is a namespace?  Think of it just like a partition on a normal hard drive.  Except the partitioning of the drive is done at the hard drive level not at the operating system level.  Thus the operating system sees the name spaces as unique hard drives.  IE if one had a 1tb NVMe, and setup four 256gb name spaces, Windows would think there was four 256gb NVMe drives in the system.  

FROM LINUX (PartedMagic was used):

nvme list <--show what nvme name spaces are present and the model of the drive

nvme id-ctrl /dev/nvme0 | grep mcap <--shows" tnvmcap (total NVM capacity) and unvmcap (unallocated NVM capacity) attributes.

nvme id-ctrl /dev/nvme0 | grep cntlid <--show the controller(s) ID's

 

DELETE NAMENSPACES

nvme detach-ns /dev/nvme0 –n 1 –controllers=0 <-- detaches the namespace "1" from the controller "0" 

nvme delete-ns /dev/nvme0 -n 1 <--deletes the namespace "1" from the controller "0"

nvme ns-rescan /dev/nvme0 <--rescans the drive "0"

 

CREATE NAMESPACES

nvme create-ns /dev/nvme0 -s 26214387 -c 26214387 -b 4096  <--creates a 100gb name space, formatted to 4k

nvme ns-rescan /dev/nvme0 <--rescan
 

nvme attach-ns /dev/nvme0 -n 1 -c 0x1  <--attach the namespace to the controller
 

nvme ns-rescan /dev/nvme0  <--rescan

Ignore this stuff....just notes to me...

nvme create-ns /dev/nvme0 -s 7499000000 -c 7499000000 -b 512

11,995,709,440

3,840,755,982,336<--cap

----4096---

1,500,295,305 <-cap/256

1,000,196,870 <-cap/384 ==too big

960,188,995<-cap/400== too big

936,769,751<=cap/410==3.84

923258649<-cap/416== 3.78

857311603 <-cap/448 ==3.51tb

750,147,652 <-cap/512 == 3.08tb

93,768,456<--cap/4096 == 384gb

26,214,387<--example ==100gb

---512---

93,768,456 <--cap4096 ==48gb

948,334,810 <--cap/410 ==485gb

1,500,295,305 <-cap/256  ==768gb

3,800,000,000<---1950gb

5,000,000,000<---2560gb 

6,500,000,000<---3330gb 

7,500,000,000<--3840gb