28 points

I’m guessing it’s for some shit to make sure some ridiculous setup with two gazillion drives doesn’t have conflicts

permalink
report
reply
1 point

obligatory xkcd? Nah, you know exactly which one I mean.

permalink
report
parent
reply
2 points

I’m not sure if it is the standards one or the usecase one

permalink
report
parent
reply
57 points

nvme0n1p1

permalink
report
reply
4 points

The other dragons aren’t specifying a partition

permalink
report
parent
reply
1 point

So the 3rd dragon should just be /dev/nvme%d

permalink
report
parent
reply

mmcblkxpy
(SD Card)

x = device number
y = partition number

permalink
report
parent
reply
16 points

NVMe device names follow this pattern: nvme <number> n <namespace> , where: <number> is an integer that is assigned by Linux during the boot process. The first NVMe device that is detected is assigned 0

permalink
report
parent
reply
3 points

I still don’t understand the point of namespaces. I guess it’s less overhead to pass through a namespace to a VM rather than having a virtualised disk image or bind mount.

permalink
report
parent
reply
5 points

You also can have a ‘c’ in there, when it wants to model multipath nvme…

permalink
report
parent
reply
3 points

ONIPI

permalink
report
parent
reply
2 points

This made me chuckle, thank you!!

permalink
report
parent
reply
101 points
*

Well it’s sdx because they both use the SATA interface. The sdx convention actually comes from scsi though, and the fact that SATA and USB drives use it might point to some code reuse, or maybe a temporary solution that never got fixed due to breaking backwards compatibility.

Fun fact: IDE drives use the hdx naming convention.

permalink
report
reply
15 points

I thought they standardized on sd* even for IDE drive a few years back…

permalink
report
parent
reply
5 points
*

Yeah, that’s what I think as well…

Got a few old rigs with IDE drives in them running Void x86, the drives in /dev are named sdx.

permalink
report
parent
reply
3 points

I didn’t know that. Maybe nvme hasn’t been added to the standard yet then.

permalink
report
parent
reply
11 points

No, they decided that nvme were too fancy to be modeled by mundane ‘sdxn’ scheme. They hypothetically have ‘namespaces’ and ‘controller paths’ and they wanted to have the naming scheme model that fully.

permalink
report
parent
reply
48 points

I still muscle-memory type /dev/hd[TAB] once in a while when looking for storage devices.

permalink
report
parent
reply
6 points

Yeah, but I think they switched to also use sdx for IDE devices as well.

permalink
report
parent
reply
4 points

Virtual drives also have a fun and relevant prefix!

permalink
report
parent
reply
3 points

Yea, I get that the s in sdX stands for sata, but why cant we have an ndX with n for nvme?

permalink
report
parent
reply
30 points

Different bus, different naming.

Now, memory kinda hazy, but weren’t ide devices /dev/hdX?

permalink
report
reply
9 points

Yeah, they used to be, but they switched a few years back to consistently call all block devices sdx.

permalink
report
parent
reply
2 points

srsly? so it’s just all “grab whatever dev” and not at all associated with the bus?

permalink
report
parent
reply
6 points

ATA was rolled into the SCSI subsystem, so both sata and pata are covered by SDX.

permalink
report
parent
reply
3 points

/dev/nvme0n1 actually, but sure. Change bad

permalink
report
reply

linuxmemes

!linuxmemes@lemmy.world

Create post

I use Arch btw


Sister communities:
Community rules
  1. Follow the site-wide rules and code of conduct
  2. Be civil
  3. Post Linux-related content
  4. No recent reposts

Please report posts and comments that break these rules!

Community stats

  • 7.7K

    Monthly active users

  • 1.3K

    Posts

  • 69K

    Comments