the servers are 2.12 and the client is 2.15. yes it was single
thread. it does still seem to be running in the background somewhere
as i see directories switch out of none,migratiing state over time.
i hope lsfck isn't the only fix, i can't exactly unmount the
filesystem at the moment.
On Wed, J
I just found this in my inbox without any answer.
If you are trying to use newer kernel versions, you also need to use a newer
Lustre client, 2.15.4 or the in-flight 2.15.5-RC2. Those are built and tested
with the newer kernel, and will interoperate with the older servers.
Cheers, Andreas
On
Hello,
On Mon, Jun 17, 2024 at 4:04 PM Michael DiDomenico via lustre-discuss <
lustre-discuss@lists.lustre.org> wrote:
> i am attempting to use lfs migrate to move some directories from one
> mdt to another. the lfs migrate part seemed to be okay as i didn't
> get any errors, but there are direc
Thanks Sebastien,
this put all clients into the correct LNet. And nodemap.exports looks as
expected.
(Had to add 'options lnet lnet_peer_discovery_disabled=1' for ‘-o
network=’ to work).
Regards
Thomas
On 6/19/24 08:31, Sebastien Buisson wrote:
Hi,
I am not sure the NIDs displayed under ‘
