Helo Alastair, thank you for your patch. I commented on the Github PR, but I'll post the same for future reference for the lustre-discuss audience, that the GitHub PRs are not a pathway for landing patches to Lustre. Patches need to be submitted to Gerrit so that they can be reviewed, tested, and landed.
See https://wiki.lustre.org/Submitting_Changes for details. Cheers, Andreas On Jan 17, 2025, at 10:13, Alastair Basden <a.g.bas...@durham.ac.uk> wrote: Hi all, Problem solved - the lustre zfs dkms wasn't building due to a bug in /usr/src/lustre-zfs-2.16.1/dkms.conf pointing to 3 of the wrong directories. We've done a pull request in the lustre-release github. Cheers, Alastair. On Fri, 17 Jan 2025, Alastair Basden wrote: [EXTERNAL EMAIL] Hi all, We are upgrading lustre servers from 2.12 to 2.16 (Rocky9). The OSTs are zfs. (2.1.15) The zpools are imported fine, with the warning that a zpool upgrade is necessary for all features to become available. We haven't done this yet, as it removed backwards compatibility. To mount the OSTs, we do what we've always done, e.t.c mount -t lustre tank1/ost1 /mnt/lustre/ost1 Upon trying to mount the OSTs, we get: mount.lustre: tank1/ost1 has not been formatted with mkfs.lustre or the backend filesystem type is not supported by this tool Has anyone tried this Lustre upgrade with zfs? Is it known to work? Is the solution to do a zpool upgrade? Cheers, Alastair. _______________________________________________ lustre-discuss mailing list lustre-discuss@lists.lustre.org http://lists.lustre.org/listinfo.cgi/lustre-discuss-lustre.org _______________________________________________ lustre-discuss mailing list lustre-discuss@lists.lustre.org http://lists.lustre.org/listinfo.cgi/lustre-discuss-lustre.org Cheers, Andreas — Andreas Dilger Lustre Principal Architect Whamcloud/DDN
_______________________________________________ lustre-discuss mailing list lustre-discuss@lists.lustre.org http://lists.lustre.org/listinfo.cgi/lustre-discuss-lustre.org
