Bug 1990389 Comment 11 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

Ah.  Because the boot disk is on nvme0n1:
```
 Oct 08 17:27:11 gecko-t-t-linux-docker-amd-jhp5qmujtf2j6ynvs3av2w multipath nvme0n1: uid = nvme.1ae0-6e766d655f636172642d7064-6e766d655f636172642d7064-00000001 (sysfs)
Oct 08 17:27:11 gecko-t-t-linux-docker-amd-jhp5qmujtf2j6ynvs3av2w systemd-fsck /dev/nvme0n1p15: 12 files, 12499/213663 clusters
Oct 08 17:27:11 gecko-t-t-linux-docker-amd-jhp5qmujtf2j6ynvs3av2w kernel  nvme0n1: p1 p14 p15 p16
Oct 08 17:27:15 gecko-t-t-linux-docker-amd-jhp5qmujtf2j6ynvs3av2w kernel EXT4-fs (nvme0n1p1): Supports (experimental) DIO atomic writes awu_min: 4096, awu_max: 4096
Oct 08 17:27:15 gecko-t-t-linux-docker-amd-jhp5qmujtf2j6ynvs3av2w kernel EXT4-fs (nvme0n1p1): mounted filesystem f8b1fd37-145c-44d7-bd5d-420a37a1468c ro with ordered data mode. Quota mode: none.
Oct 08 17:27:15 gecko-t-t-linux-docker-amd-jhp5qmujtf2j6ynvs3av2w kernel EXT4-fs (nvme0n1p1): re-mounted f8b1fd37-145c-44d7-bd5d-420a37a1468c r/w.
Oct 08 17:27:15 gecko-t-t-linux-docker-amd-jhp5qmujtf2j6ynvs3av2w kernel EXT4-fs (nvme0n1p16): Supports (experimental) DIO atomic writes awu_min: 4096, awu_max: 4096
Oct 08 17:27:15 gecko-t-t-linux-docker-amd-jhp5qmujtf2j6ynvs3av2w kernel EXT4-fs (nvme0n1p16): mounted filesystem 44bd5d32-077f-4b29-871d-cfeb7677f0f6 r/w with ordered data mode. Quota mode: none.
Oct 08 17:27:15 gecko-t-t-linux-docker-amd-jhp5qmujtf2j6ynvs3av2w kernel EXT4-fs (nvme0n1p1): resizing filesystem from 15466235 to 19398395 blocks
Oct 08 17:27:15 gecko-t-t-linux-docker-amd-jhp5qmujtf2j6ynvs3av2w kernel EXT4-fs (nvme0n1p1): resized filesystem to 19398395
Oct 08 17:27:18 gecko-t-t-linux-docker-amd-jhp5qmujtf2j6ynvs3av2w configure-generic-worker-disks Found 1 nvme0n* devices: /dev/nvme0n1
Oct 08 17:27:18 gecko-t-t-linux-docker-amd-jhp5qmujtf2j6ynvs3av2w configure-generic-worker-disks   Cannot use /dev/nvme0n1: device is partitioned
Oct 08 18:58:39 gecko-t-t-linux-docker-amd-jhp5qmujtf2j6ynvs3av2w fstrim /boot/efi: 98.2 MiB (102995968 bytes) trimmed on /dev/nvme0n1p15
Oct 08 18:58:39 gecko-t-t-linux-docker-amd-jhp5qmujtf2j6ynvs3av2w fstrim /boot: 795 MiB (833662976 bytes) trimmed on /dev/nvme0n1p16
Oct 08 18:58:39 gecko-t-t-linux-docker-amd-jhp5qmujtf2j6ynvs3av2w fstrim /: 16.2 GiB (17419616256 bytes) trimmed on /dev/nvme0n1p1
```
So where's the local ssd?
Ah.  Because the boot disk is on nvme0n1:
```
Oct 08 17:27:11 gecko-t-t-linux-docker-amd-jhp5qmujtf2j6ynvs3av2w multipath nvme0n1: uid = nvme.1ae0-6e766d655f636172642d7064-6e766d655f636172642d7064-00000001 (sysfs)
Oct 08 17:27:11 gecko-t-t-linux-docker-amd-jhp5qmujtf2j6ynvs3av2w systemd-fsck /dev/nvme0n1p15: 12 files, 12499/213663 clusters
Oct 08 17:27:11 gecko-t-t-linux-docker-amd-jhp5qmujtf2j6ynvs3av2w kernel  nvme0n1: p1 p14 p15 p16
Oct 08 17:27:15 gecko-t-t-linux-docker-amd-jhp5qmujtf2j6ynvs3av2w kernel EXT4-fs (nvme0n1p1): Supports (experimental) DIO atomic writes awu_min: 4096, awu_max: 4096
Oct 08 17:27:15 gecko-t-t-linux-docker-amd-jhp5qmujtf2j6ynvs3av2w kernel EXT4-fs (nvme0n1p1): mounted filesystem f8b1fd37-145c-44d7-bd5d-420a37a1468c ro with ordered data mode. Quota mode: none.
Oct 08 17:27:15 gecko-t-t-linux-docker-amd-jhp5qmujtf2j6ynvs3av2w kernel EXT4-fs (nvme0n1p1): re-mounted f8b1fd37-145c-44d7-bd5d-420a37a1468c r/w.
Oct 08 17:27:15 gecko-t-t-linux-docker-amd-jhp5qmujtf2j6ynvs3av2w kernel EXT4-fs (nvme0n1p16): Supports (experimental) DIO atomic writes awu_min: 4096, awu_max: 4096
Oct 08 17:27:15 gecko-t-t-linux-docker-amd-jhp5qmujtf2j6ynvs3av2w kernel EXT4-fs (nvme0n1p16): mounted filesystem 44bd5d32-077f-4b29-871d-cfeb7677f0f6 r/w with ordered data mode. Quota mode: none.
Oct 08 17:27:15 gecko-t-t-linux-docker-amd-jhp5qmujtf2j6ynvs3av2w kernel EXT4-fs (nvme0n1p1): resizing filesystem from 15466235 to 19398395 blocks
Oct 08 17:27:15 gecko-t-t-linux-docker-amd-jhp5qmujtf2j6ynvs3av2w kernel EXT4-fs (nvme0n1p1): resized filesystem to 19398395
Oct 08 17:27:18 gecko-t-t-linux-docker-amd-jhp5qmujtf2j6ynvs3av2w configure-generic-worker-disks Found 1 nvme0n* devices: /dev/nvme0n1
Oct 08 17:27:18 gecko-t-t-linux-docker-amd-jhp5qmujtf2j6ynvs3av2w configure-generic-worker-disks   Cannot use /dev/nvme0n1: device is partitioned
Oct 08 18:58:39 gecko-t-t-linux-docker-amd-jhp5qmujtf2j6ynvs3av2w fstrim /boot/efi: 98.2 MiB (102995968 bytes) trimmed on /dev/nvme0n1p15
Oct 08 18:58:39 gecko-t-t-linux-docker-amd-jhp5qmujtf2j6ynvs3av2w fstrim /boot: 795 MiB (833662976 bytes) trimmed on /dev/nvme0n1p16
Oct 08 18:58:39 gecko-t-t-linux-docker-amd-jhp5qmujtf2j6ynvs3av2w fstrim /: 16.2 GiB (17419616256 bytes) trimmed on /dev/nvme0n1p1
```
So where's the local ssd?

Back to Bug 1990389 Comment 11