Just for public reference the solution was provided by Martin Audet
which was to add the --kmp flag when building MOFED. So you want:
mlnxofedinstall --add-kernel-support-build-only --kmp
Thanks Martin!
-Paul Edmon-
On 3/16/24 5:28 AM, Andreas Dilger wrote:
On Mar 15, 2024, at 09:18, Paul
nyone know the solution to this? Is there a work around?
-Paul Edmon-
___
lustre-discuss mailing list
lustre-discuss@lists.lustre.org
http://lists.lustre.org/listinfo.cgi/lustre-discuss-lustre.org
: 0x50
(needs_index update )
Persistent mount opts:
Parameters:
tunefs.lustre FATAL: must set target type: MDT,OST,MGS
tunefs.lustre: exiting with 22 (Invalid argument)
-Paul Edmon-
On 7/22/2022 10:37 AM, Thomas Roth via lustre-discuss wrote:
You could look at what the device
The individual LUN looks good but the controller is showing amber, which
is confusing us. However other LUN's going through that controller are
mounting fine.
-Paul Edmon-
On 7/20/2022 3:08 PM, Colin Faber wrote:
raid check?
On Wed, Jul 20, 2022, 12:41 PM Paul Edmon wrote:
[root
)
Relocate? no
It continues at length like that.
-Paul Edmon-
On 7/20/2022 2:31 PM, Colin Faber wrote:
Can you mount the target directly with -t ldiskfs ?
Also what does e2fsck report?
On Wed, Jul 20, 2022, 11:48 AM Paul Edmon via lustre-discuss
wrote:
We have a filesystem that we have
ZFS library: 256
mount.lustre: missing option mgsnode=
The weird thing is that we didn't build this with ZFS, the devices are
all ldiskfs. We suspect some of the data is corrupt on the disk but we
were wondering if anyone had seen this error before and if there was a
solution.
-Paul Edmon
You should just need 988, see:
https://wiki.lustre.org/Operating_System_Configuration_Guidelines_For_Lustre
-Paul Edmon-
On 6/13/2022 10:27 AM, Sharma, Amit via lustre-discuss wrote:
Hi Team,
can you please help me which ephemeral TCP ports need to be opened for
luster inter server
Excellent. That should work great.
-Paul Edmon-
On 3/13/19 10:25 AM, Chad DeWitt wrote:
Hi Paul,
lfs findmay do what you want:
lfs find /lustre_mount_point/ --ost /IDs_of_OSTs/
/
/
/IDs_of_OSTs/is comma delimited
Should even grab files that are striped and have a portion
I have a OSS that is offline. Is there a way to poll the MDT and grab a
list of files that are on the affected OST's? Or is the only method
just scaning the whole filesystem with normal find combined with lfs
getstripe commands?
-Paul Edmon
and unexpected. Some one else
on the list may have insight on these.
-Paul Edmon-
On 2/27/19 10:17 AM, Bernd Melchers wrote:
Hi all,
our environment: CentOS-7.6, lustre-2.12.0@zfs-0.7.12, 2 mds, 7 ods, 180
clients.
Is it possible to reboot the mds and ods server (e.g. for new kernel or
new lustre
I'm not aware of one, but I too would love to either learn of a tool to
do this or advocate for Lustre to add it.
-Paul Edmon-
On 12/20/18 9:41 AM, Jason Williams wrote:
It is entirely possible that this already exists, but my google-foo is
not what it used to be. However, I've searched
In the past for these situations I've used the lctl deactivate command
to deactivate specific OST's. That way you can still use the system
while you repair. This page has the lctl command in it.
http://wiki.lustre.org/Handling_Full_OSTs
-Paul Edmon-
On 12/13/18 5:24 AM, Tung-Han Hsieh
12 matches
Mail list logo