My environment has both TCP and IB clients, so my Lustre config has to
accommodate both, but I'm having a hard time figuring out the proper syntax
for it. Theoretically, I should be able to use comma-separated interfaces
in the mgsnode parameter like this:
--mgsnode=192.168.10.1@tcp0,172.16.10.1@o
I made a typo when setting failnode/servicenode parameters, but I can't
figure out how to remove the failnode parameter entirely
I can change the failnode NIDs, but I can't figure out how to completely
remove "failnode" from the system.
Does anyone have an example of a syntax (maybe lctl?) that w
I’m just going to guess, but you’ve got active/active OSTs, and some are
running on the standby node.
A lustre client will contact the MGS on mount and get the list of MDTs and
OSTs, along with their primary and secondary (etc.) locations. The client then
starts contacting the targets. The th
All,
I have been seeing this pretty regularly.
I reboot a system and mount a lustre filesystem.
It mounts, but when I do 'lfs df', I see numerous OSTs that are listed as
'inactive device'
If I wait, they all eventually mount. Odd thing is that I always get some that
mount fine and others that wa
