···61616262 expectedDeviceName: "vda",
6363 },
6464+ {
6565+ name: "should find the device name for a lvm volume backed by a single disk",
6666+6767+ // ( lsblk output from the snapshotted machine)
6868+ // ~ # lsblk
6969+ // NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
7070+ // sda 8:0 0 7.3T 0 disk
7171+ // └─sda1 8:1 0 1024G 0 part /var/lib/plex
7272+ // nvme0n1 259:0 0 1.8T 0 disk
7373+ // ├─nvme0n1p1 259:1 0 529M 0 part
7474+ // ├─nvme0n1p2 259:2 0 99M 0 part
7575+ // ├─nvme0n1p3 259:3 0 16M 0 part
7676+ // ├─nvme0n1p4 259:4 0 293G 0 part
7777+ // ├─nvme0n1p5 259:5 0 512M 0 part /boot
7878+ // └─nvme0n1p6 259:6 0 1.5T 0 part
7979+ // └─pool-nixos 254:0 0 600G 0 lvm /nix/store
8080+ // / # test targets this device
8181+8282+ sysfsTarballFile: "sysfs.lvm.dm-0.tar.gz",
8383+8484+ deviceMajor: 254, // points to dm-0 device
8585+ deviceMinor: 0,
8686+8787+ // TODO@ggilmore: technically, dm-0 is a lvm volume backed by a partition stored on the nvme device.
8888+ // For consistency with the other test case, we should be returning nvme0n1 (the parent disk device) as the
8989+ // device name. I'll revisit this later, as I need to figure out how to programmatically determine
9090+ // the nvme01n1 <-> dm-0 translation.
9191+ expectedDeviceName: "dm-0",
9292+ },
6493 } {
6594 test := test
6695