Can you share the client’s cpt configuration?
$ lctl get_param cpu_partition_table cpu_partition_distance
Chris Horn
From: lustre-discuss on behalf of
Gwen Dawes via lustre-discuss
Date: Wednesday, February 14, 2024 at 11:19 AM
To: lustre-discuss@lists.lustre.org
Subject: Re:
Hi all,
I have a question regarding the performance bottleneck of a single OST. We have
high-performance SAN storage, which can provide high raw write bandwidth with a
single LUN (e.g., about 10GiB/s).
We evaluate the write performance of a single OST (based on a single LUN) via
Hello Jan,
More often than not, when I see stat() syscalls hanging, it's due to a
communication issue with an OSS rather than an MDS. I think the message about
"Lustre: comind-MDT: haven't heard from client ..." may be a downstream
effect of the client hanging (maybe due to an OSS issue),
I have the beginnings of a lustre filesystem, with a server, mds,
hosting the MGS and MDS, and a storage node, oss1. The disks, /mgt and
/mdt on mds and /ost on oss1 mount, apparently without error.
I have set up a client, pxe, which mounts /lustre:
root@node080027eb24b8:~# mount -t lustre
