Andrei, thanks for the response and excuse the delay. My replies
inline below...
On Mon, 2 Sep 2019 20:53:08 +0300
Andrei Borzenkov
02.09.2019 16:13, Ralph пишет:
[Leap 15.1, xfce, kernel 5.2.11-1.g6385110-default]
I have a machine with 2 nvme drives, 1 in the built-in motherboard m.2 slot (grub2 boots 15.1,"SX8200NP"), other in an m.2 slot on a pci-e expansion card (boots 15.0,"SX7000NP"). The dev names of the 2 nvmes seem to keep changing within the same boot. Here's an example from the logs
Show full logs from boot (journalctl -b).
Original journal under discussion is gone because apparently the default of a new 15.1 install is to not write journals to permanent storage. Bad idea, imho. Anyway, fixed now. Current log is at: https://paste.opensuse.org/9a901053 with same nvme device number problem as before. Note that journal is truncated at point of first user info as I log some file accesses and etc and I would need to edit it for privacy before posting beyond this point. If you need anything beyond this point in the journal, advise. Note that yast2 info on the nvme devices is the same now as given below.
with the mb nvme first called nvme0 by the kernel, then nvme1 by btrfs, then nvme0 by both smart and btrfs. But the device according to yast is still nvme1. Confusing, to say the least. I need someone smarter than me (which is just about anyone) to tell me what is going on here. What have I done :(
Devices according to yast2 (partitioner):
Device: /dev/nvme1n1 Device Path: pci-0000:02:00.0-nvme-1 Device ID 1: nvme-ADATA_SX8200NP_2I4520013773
Device: /dev/nvme0n1 Device Path: pci-0000:05:00.0-nvme-1 Device ID 1: nvme-ADATA_SX7000NP_2H4220054168
according to the journal, in chronological order:
kernel: nvme nvme0: pci function 0000:02:00.0 kernel: nvme nvme1: pci function 0000:05:00.0
BTRFS: device label openSUSE-15 devid 1 transid 778057 /dev/nvme0n1p3 BTRFS: device label openSUSE-15.1 devid 1 transid 37777 /dev/nvme1n1p4
(note: if not apparent, this below is / on SX8200NP) kernel: BTRFS info (device nvme1n1p4): disk space caching is enabled kernel: BTRFS info (device nvme1n1p4): has skinny extents kernel: BTRFS info (device nvme1n1p4): enabling ssd optimizations kernel: BTRFS info (device nvme1n1p4): disk space caching is enabled
smartd[1494]: Device: /dev/nvme0, opened smartd[1494]: Device: /dev/nvme0, ADATA SX8200NP, S/N:2I4520013773, FW:SVN139B
smartd[1494]: Device: /dev/nvme1, opened smartd[1494]: Device: /dev/nvme1, ADATA SX7000NP, S/N:2H4220054168, FW:CB1.1.1
(note: if not apparent, this below is / on SX7000NP and the journal entry appears to be triggered by snapper. Why is snapper looking at something other than the running system? Is it confused, too?)
snapper is mentioned nowhere in lines you posted.
In the original journal of that day, snapper process was wrapped around the journal entry and appeared to be triggering those entries. Not evident in the current journal.
kernel: BTRFS info (device nvme0n1p3): disk space caching is enabled kernel: BTRFS info (device nvme0n1p3): has skinny extents kernel: BTRFS info (device nvme0n1p3): enabling ssd optimizations kernel: BTRFS info (device nvme0n1p3): disk space caching is enabled kernel: BTRFS info (device nvme0n1p3): has skinny extents kernel: BTRFS info (device nvme0n1p3): enabling ssd optimizations
Thanks.
Ralph
-- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org