[lustre-discuss] SSK key refresh issue

Sebastien Buisson sbuisson at ddn.com
Wed Jun 3 09:01:38 PDT 2020


Hi,

Do you use one shared MGS for all your file systems, or does each file system have its own MGS? In the latter case, are the MGSes running on the same node?

You are mentioning a key refresh issue, so I am wondering if you see this issue with multiple file systems only, or if it occurs when you have just one file system setup?

Cheers,
Sebastien.

> Le 3 juin 2020 à 15:07, Hans Henrik Happe <happe at nbi.dk> a écrit :
> 
> Hi,
> 
> I'm trying to hunt down an issue where SSK is failing key refresh on
> 2.12.4. Mounting the filesystem works, but active sessions dies at refresh.
> 
> First I would like to get a few things cleared.
> 
> Is multiple Lustre filesystems on the same servers supported with SSK?
> 
> If so, is it supported to use the same nodemap on each filesystem?
> Obviously, with different keys for each fs.
> 
> A mount from an ssh to the root account will create this keyring on
> CentOS 7:
> 
> # keyctl show
> Session Keyring
> 669565440 --alswrv      0     0  keyring: _ses
> 458158660 --alswrv      0 65534   \_ keyring: _uid.0
> 129939379 --alswrv      0     0       \_ user: lustre:erda
> 
> 65534 usually is nfsnobody but is does not exist on the system. Would
> this be an issue? Even if nfsnobody existed?
> 
> A mount through sudo will create this keyring on CentOS 7:
> 
> # keyctl show
> Session Keyring
> 381836048 --alswrv      0 65534  keyring: _uid_ses.0
> 423400032 --alswrv      0 65534   \_ keyring: _uid.0
> 934942793 --alswrv      0     0       \_ user: lustre:erda
> 
> Again is this a problem?
> 
> 
> Cheers,
> Hans Henrik
> _______________________________________________
> lustre-discuss mailing list
> lustre-discuss at lists.lustre.org
> http://lists.lustre.org/listinfo.cgi/lustre-discuss-lustre.org



More information about the lustre-discuss mailing list