Major ID for NVME devices and MD partitioned , are they supposed to be the same ?

babydr · 05-17-2023, 11:44 PM

Linux slackware64Current.baby-dragons.com 6.1.29 #1 SMP PREEMPT_DYNAMIC Wed May 17 15:06:04 CDT 2023 x86_64 AMD EPYC 7452 32-Core Processor AuthenticAMD GNU/Linux

Code:

# lsblk -i
NAME          MAJ:MIN RM   SIZE RO TYPE  MOUNTPOINTS
sda             8:0    0 442.5G  0 disk  
sdb             8:16   0 441.4G  0 disk  
`-sdb1          8:17   0 441.4G  0 part  
  `-md121       9:121  0 882.6G  0 raid0 
    `-md121p1 259:32   0 882.6G  0 part  
sdc             8:32   0 930.4G  0 disk  
`-sdc1          8:33   0 930.4G  0 part  
sdd             8:48   0 441.4G  0 disk  
`-sdd1          8:49   0 441.4G  0 part  
  `-md121       9:121  0 882.6G  0 raid0 
    `-md121p1 259:32   0 882.6G  0 part  
sde             8:64   0  25.5T  0 disk  
`-sde1          8:65   0  25.5T  0 part  
sdf             8:80   1 931.5G  0 disk  
|-sdf1          8:81   1   512M  0 part  /boot/efi
|-sdf2          8:82   1   128G  0 part  [SWAP]
`-sdf3          8:83   1   803G  0 part  /
sr0            11:0    1  1024M  0 rom   
nvme1n1       259:0    0 953.9G  0 disk  
|-nvme1n1p1   259:1    0 905.7G  0 part  
| `-md126       9:126  0 905.5G  0 raid1 
|   |-md126p1 259:30   0 887.5G  0 part  
|   `-md126p2 259:31   0    18G  0 part  
`-nvme1n1p2   259:2    0   512M  0 part  
nvme0n1       259:3    0 953.9G  0 disk  
|-nvme0n1p1   259:4    0 905.7G  0 part  
| `-md126       9:126  0 905.5G  0 raid1 
|   |-md126p1 259:30   0 887.5G  0 part  
|   `-md126p2 259:31   0    18G  0 part  
`-nvme0n1p2   259:5    0   512M  0 part  
nvme2n1       259:6    0   3.5T  0 disk  
`-nvme2n1p1   259:8    0   3.1T  0 part  
  `-md124       9:124  0   3.1T  0 raid1 
    `-md120     9:120  0  15.7T  0 raid0 
nvme3n1       259:7    0   3.5T  0 disk  
`-nvme3n1p1   259:9    0   3.1T  0 part  
  `-md123       9:123  0   3.1T  0 raid1 
    `-md120     9:120  0  15.7T  0 raid0 
nvme4n1       259:10   0   3.5T  0 disk  
`-nvme4n1p1   259:11   0   3.1T  0 part  
  `-md125       9:125  0   3.1T  0 raid1 
    `-md120     9:120  0  15.7T  0 raid0 
nvme5n1       259:12   0   3.5T  0 disk  
`-nvme5n1p1   259:14   0   3.1T  0 part  
  `-md127       9:127  0   3.1T  0 raid1 
    `-md120     9:120  0  15.7T  0 raid0 
nvme10n1      259:13   0   3.5T  0 disk  
`-nvme10n1p1  259:15   0   3.1T  0 part  
  `-md123       9:123  0   3.1T  0 raid1 
    `-md120     9:120  0  15.7T  0 raid0 
nvme12n1      259:16   0   3.5T  0 disk  
`-nvme12n1p1  259:18   0   3.1T  0 part  
  `-md127       9:127  0   3.1T  0 raid1 
    `-md120     9:120  0  15.7T  0 raid0 
nvme13n1      259:17   0   3.5T  0 disk  
`-nvme13n1p1  259:23   0   3.1T  0 part  
  `-md125       9:125  0   3.1T  0 raid1 
    `-md120     9:120  0  15.7T  0 raid0 
nvme8n1       259:19   0   3.5T  0 disk  
`-nvme8n1p1   259:25   0   3.1T  0 part  
  `-md122       9:122  0   3.1T  0 raid1 
    `-md120     9:120  0  15.7T  0 raid0 
nvme6n1       259:20   0   3.5T  0 disk  
`-nvme6n1p1   259:26   0   3.1T  0 part  
nvme7n1       259:21   0   3.5T  0 disk  
`-nvme7n1p1   259:27   0   3.1T  0 part  
nvme9n1       259:22   0   3.5T  0 disk  
`-nvme9n1p1   259:28   0   3.1T  0 part  
  `-md122       9:122  0   3.1T  0 raid1 
    `-md120     9:120  0  15.7T  0 raid0 
nvme11n1      259:24   0   3.5T  0 disk  
`-nvme11n1p1  259:29   0   3.1T  0 part  
  `-md124       9:124  0   3.1T  0 raid1 
    `-md120     9:120  0  15.7T  0 raid0

unInstance · 05-17-2023, 11:50 PM

What is wrong?

ctrlaltca · 05-18-2023, 03:58 AM

Yes, md devices have a different major number than physical drives, see here: https://www.kernel.org/doc/html/late...e/devices.html

michaelk · 05-18-2023, 06:42 AM

Quote:

259 block Block Extended Major
Used dynamically to hold additional partition minor
numbers and allow large numbers of partitions per device

At first glance it looks ok to me too. My nvme drive also has 259 major number. All of your MD raid devices are 9 but their partitions are 259.

BW-userx · 05-18-2023, 06:56 AM

mine look like this

Code:

$ lsblk
NAME         MAJ:MIN RM   SIZE RO TYPE MOUNTPOINTS
sda            8:0    0   1.8T  0 disk 
├─sda1         8:1    0   1.7T  0 part /media/storage
├─sda2         8:2    0    40G  0 part 
├─sda3         8:3    0  24.4G  0 part 
└─sda4         8:4    0  24.4G  0 part 
nvme0n1      259:0    0   1.9T  0 disk 
├─nvme0n1p2  259:1    0   100M  0 part /boot/efi
├─nvme0n1p3  259:2    0    16M  0 part 
├─nvme0n1p4  259:3    0 217.3G  0 part 
├─nvme0n1p5  259:4    0   114G  0 part 
├─nvme0n1p6  259:5    0  50.4G  0 part /
├─nvme0n1p7  259:6    0 206.2G  0 part /home
├─nvme0n1p8  259:7    0     4G  0 part 
├─nvme0n1p9  259:8    0  48.8G  0 part 
├─nvme0n1p10 259:9    0     1T  0 part /media/data
├─nvme0n1p11 259:10   0  50.8G  0 part /media/ntfs
└─nvme0n1p12 259:11   0 148.4G  0 part /media/projects

babydr · 05-18-2023, 07:29 PM

@michaelk & @ctrlaltca , My concern is , it is VERY difficult to identify device Types by Major ID with this (imo) overlapping of multiple devices types of different Technologies to the same Major ID .

@ctrlaltca , Thank you , for sending that link , It is informational , If not helpful , in helping to identify and differentiate these technologies .

@michaelk , Thank you , for the blurb , It too was informational .

Tho when an MD's partition has identical Major ID with a NVME Block device . I beleive that this is a bit wacky .

I'd have thought that by now 10+years after it's inception that NVME Block devices would have their own Block ID .

And that the MD's partitions would have maintained the MD's Major ID of 9 .

Just a bit of a rant on things . I am also aware that the Major ID's have some limits imposed apon their use , as well the Minor ID , or they did ...

Thank You all For your input . Twyl , JimL