Hi all,
Thanks - the problem turned out to be the kernel-devel module.
Cheers,
Alastair.
On Tue, 2 Jun 2020, Pascal Suter wrote:
Hi
where you using the rpms from the whamcloud repo?
if so, check if you have installed the kmod-lustre-osd-zfs and
lustre-osd-zfs-mount packages.
IIRC i had
Hi George
that used to be the case until before 2.10.1, but since 2.10.1 even
ldiskfs does not require a patch anymore. I have actually updated from a
patched 2.10.3 to 2.12.4 patchless and i am using ldiskfs for my MDTs
and ZFS for the OSTs
but i think i just found out why there are still
IIRC "patchless server" can only serve ZFS based backends.So, it you really need ldiskfs - you're stuck with patched kernel for now. 27.05.2020, 18:41, "Pascal Suter" :Hi alli am currently upgrading a lustre 2.10.3 to 2.12.4 on CentOS 7.7 and Iam unsure if I should use the patchless or patched
Hi
where you using the rpms from the whamcloud repo?
if so, check if you have installed the kmod-lustre-osd-zfs and
lustre-osd-zfs-mount packages.
IIRC i had the same errors when the kmod-lustre-osd-zfs package was
missing on my system.
cheers
Pascal
On 6/2/20 1:20 AM, Alastair Basden
Hi all,
we use TBF policy(details:
https://jira.whamcloud.com/secure/attachment/14201/Lustre%20NRS%20TBF%20documentation%200.1.pdf)
to limit rpcrate coming from clients; but I do not know how to mapping of
rpcrate to bandwidth or iops.
For example:
if I set a client's rpcrate=10，how much bandwith
Hi Jeff,
Yes zfs modules are there - at least, I can see the zpools okay.
But, dkms status reports:
lustre-zfs, 2.12.3, 3.10.0-957.10.1.el7_lustre.x86_64, x86_64: installed
(WARNING! Diff between built and installed module!) (WARNING! Diff between
built and installed module!) (WARNING! Diff
