Wouldn't it make more sense to downgrade/install 2.4.2 in that case?
On Wed, Jan 8, 2014 at 4:58 PM, Oliver Mangold
oliver.mang...@emea.nec.comwrote:
Hello,
we installed Lustre 2.5.0 servers at a customer site and ran into
massive stability problems. Because of this we would like to
We weren't able to use lustre (2.4.2/2.5.x) with kernel 3.12.4 (staging
kernel driver - kernel panics on mount)
After compiling 3.13-rc we have a working system (though it has not yet
being put through its' paces except for some simultaneous dd)
On Wed, Jan 8, 2014 at 5:02 PM, E.S. Rosenberg
Hello!
On Jan 8, 2014, at 9:58 AM, Oliver Mangold wrote:
Lustre: MGS MGS started
LustreError: 5476:0:(mgc_request.c:76:mgc_name2resid()) missing name:
-sptlrpc
Lustre: 5528:0:(ldlm_lib.c:952:target_handle_connect()) MGS: connection
LustreError: 5476:0:(mgc_request.c:286:config_log_add())
On 08.01.2014 16:02, E.S. Rosenberg wrote:
Wouldn't it make more sense to downgrade/install 2.4.2 in that case?
Might consider it, if I run out of other options, but the little experience I
had with the 2.4 series didn't leave a good impression with me concerning
stability. I would prefer 2.1.6
On Jan 8, 2014, at 10:15 AM, Oliver Mangold wrote:
Is this some sort of kerberos enabled deployment?
No nothing like that. Even group upcall is disabled.
There's all this sptlrpc chatter coming out from somewhere that should not be
there.
I suspect there might be a bad entry in your mgs
On 08.01.2014 16:35, Drokin, Oleg wrote:
On Jan 8, 2014, at 10:15 AM, Oliver Mangold wrote:
Is this some sort of kerberos enabled deployment?
No nothing like that. Even group upcall is disabled.
There's all this sptlrpc chatter coming out from somewhere that should not be
there.
I suspect
