sent a v2: https://lore.proxmox.com/pve-devel/20250307095245.65698-1-f.we...@proxmox.com/T/
On 10/02/2025 11:47, Fabian Grünbichler wrote: > [...] > >> >> So I'm wondering: >> >> (a) could the ZFS initramfs script use `-aay` instead of `-ay`, so the >> `--setautoactivation` flag has an effect again for LVs that are visible >> at boot? > > probably ;) v2 contains a zfsonlinux patch for this, I'll also send it upstream. >> >> (b) assuming (a) can be fixed, is there any additional reason to prefer >> to --ignoreactivationskip/--setactivationskip approach over the >> `--setautoactivation n` approach? > > the only other reason I could think of is that there's a metric ton of > tutorials/howtos for various things that contain "vgchange -ay" which > would still entail potential breakage.. but then again, one could argue > that people blindly following such instructions are to blame, and the > reduced complexity on our end would be worth it.. Good point, though I'd hope users would run `vgchange -ay` only occasionally, triggering the issue for the current boot only but not for every subsequent boot. The v2 would probably still need to wait until PVE 9 (see its cover letter for details), so not much gained here in comparison to v1. I still find its approach less complex and would prefer it, but this is of course debatable :) >> >> [1] >> https://github.com/openzfs/zfs/blob/c2458ba921a8d59cd6b705f81b37f50531f8670b/contrib/initramfs/scripts/local-top/zfs >> >> [2] FWIW, one way to debug this: >> >> - attaching a serial console to the VM >> - removing `quiet` and adding `console=ttyS0` to the kernel command line >> - setting `log_level=debug` in >> /usr/share/initramfs-tools/scripts/init-top/udev >> - adding some debug printouts (echo XYZ > /dev/ttyS0) to >> /usr/share/initramfs-tools/scripts/local-top/zfs >> - don't forget `update-initramfs -u` >> - attach to serial console on host: `qm console VMID` >> >> > > > _______________________________________________ > pve-devel mailing list > pve-devel@lists.proxmox.com > https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel > > _______________________________________________ pve-devel mailing list pve-devel@lists.proxmox.com https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
