search for: el8_6

...id you get the .80.1 kernel from? I'm a bit confused because I can > > only see .76.1 on my systems. > > Simon > > I'm actually running Scientific Linux, which seems to be a little ahead here. > > Probably not related, but vmlinuz-4.18.0-372.32.1.el8_6.x86_64 (AlmaLinux 8.6) had a kernel panic > on a Intel Xeon E5504 processor, but works fine on Xeon E56XX processors (5620 specifically in our > tests). * Believe from kernel version, the original email is for Centos 7, possible the same > change that went into the EL8 kernel went also...

...gt; only see .76.1 on my systems. > >>> > >>> Simon > >>> > >>> I'm actually running Scientific Linux, which seems to be a little > >>> ahead here. > >>> Probably not related, but vmlinuz-4.18.0-372.32.1.el8_6.x86_64 > >>> (AlmaLinux 8.6) had a kernel panic on a Intel Xeon E5504 processor, > >>> but works fine on Xeon E56XX processors (5620 specifically in our > >>> tests). * Believe from kernel version, the original email is for > >>> Centos 7, possible th...

Hello, we are using ctdb 4.15.5 on RHEL8 (Kernel 4.18.0-372.32.1.el8_6.x86_64) to provide NFS v3 (via tcp) to RHEL7/8 clients. Whenever an ip takeover happens most clients report something like this: [Mon Feb 13 12:21:22 2023] nfs: server x.x.253.252 not responding, still trying [Mon Feb 13 12:21:28 2023] nfs: server x.x.253.252 not responding, still trying [Mon Feb...

Hi Uli, [Sorry for slow response, life is busy...] On Mon, 13 Feb 2023 15:06:26 +0000, Ulrich Sibiller via samba <samba at lists.samba.org> wrote: > we are using ctdb 4.15.5 on RHEL8 (Kernel > 4.18.0-372.32.1.el8_6.x86_64) to provide NFS v3 (via tcp) to RHEL7/8 > clients. Whenever an ip takeover happens most clients report > something like this: > [Mon Feb 13 12:21:22 2023] nfs: server x.x.253.252 not responding, still trying > [Mon Feb 13 12:21:28 2023] nfs: server x.x.253.252 not responding, st...