Pseudoflavor 390004 not found!
Subsystems (3)
With current git kernel 3.9-X (since 1 or 2 days) I'm getting the messages seen below at a user mode linux guest on which I run trinity.
On the guest I mount via NFSv4 (and in parallel via hostfs) an EXT4 fs from the host system. The EXT4 resides within a file on a tmpfs which is mounted via loop device.
So on the hosts it looks like :
$> df -m
tmpfs 3072 135 2938 5% /mnt/ramdisk/dev/loop0 241 5 224 3% /mnt/trinity
$ cat /etc/exports # /etc/exports: NFS file systems being exported. See exports(5). /mnt/trinity 192.168.0.0/16(rw,fsid=0,insecure,no_subtree_check,async,no_root_squash)
and the UML mounts the share /mnt/trinity just onto its mount points /mnt/n22 and /mnt/nfs/n22 respectively. And these are the messages I'm curious about :
2013-05-01T10:22:55.613+02:00 trinity kernel: gss_create: Pseudoflavor 390004 not found! 2013-05-01T10:22:55.613+02:00 trinity kernel: RPC: Couldn't create auth handle (flavor 390004)
Signature · 3 lines
MfG/Sincerely Toralf Förster pgp finger print: 7B1A 07F4 EC82 0F90 D4C2 8936 872A E508 7DB6 9DA3
Toralf Förster wrote:
2013-05-01T10:22:55.613+02:00 trinity kernel: gss_create: Pseudoflavor 390004 not found! 2013-05-01T10:22:55.613+02:00 trinity kernel: RPC: Couldn't create auth handle (flavor 390004)
I think that means you're trying to use krb5 but don't have the gss_krb5 module loaded. If you really do want to use krb5, check your kernel config. If not, check your mount options.
Quoted 15 lines · Toralf Förster
With current git kernel 3.9-X (since 1 or 2 days) I'm getting the messages seen below at a user mode linux guest on which I run trinity.
On the guest I mount via NFSv4 (and in parallel via hostfs) an EXT4 fs from the host system. The EXT4 resides within a file on a tmpfs which is mounted via loop device.
So on the hosts it looks like :
$> df -m
tmpfs 3072 135 2938 5%/mnt/ramdisk/dev/loop0241 5 224 3%/mnt/trinity$ cat /etc/exports # /etc/exports: NFS file systems being exported. See exports(5). /mnt/trinity 192.168.0.0/16(rw,fsid=0,insecure,no_subtree_check,async,no_root_squash)
Quoted 6 lines
and the UML mounts the share
/mnt/trinityjust onto its mount points/mnt/n22and/mnt/nfs/n22respectively. And these are the messages I'm curious about :2013-05-01T10:22:55.613+02:00 trinity kernel: gss_create: Pseudoflavor 390004 not found! 2013-05-01T10:22:55.613+02:00 trinity kernel: RPC: Couldn't create auth handle (flavor 390004)
It's a harmless message. The latest kernel will try to use krb5i to establish the lease (i.e. for the SETCLIENTID call) as per the recommendations in the RFC3530bis spec, but on systems such as yours where you have not enabled krb5, it will fall back to using sec=sys (auth_sys).
We should just disable the above warnings.
Note that even if the lease negotiation uses krb5i, the actual mount will continue to use whatever flavour you specify in your 'sec=' mount option (or it will use NFSv4 security negotiation) when doing operations on the filesystem.
The attached patch will turn off those messages for you.
Signature · 6 lines
Trond Myklebust Linux NFS client maintainer NetApp [email protected] www.netapp.com
From 9c9a7f0d781ae34cdf7770dcaa9e67ec7cb0475c Mon Sep 17 00:00:00 2001
From: Trond Myklebust <[email protected]>
Date: Wed, 1 May 2013 09:17:50 -0400
Subject: [PATCH] SUNRPC: Don't spam syslog with "Pseudoflavor not found"
messages
Just convert those messages to dprintk()s so that they can be used when debugging.
--- net/sunrpc/auth_gss/auth_gss.c | 3 +-- net/sunrpc/clnt.c | 2 +- 2 files changed, 2 insertions(+), 3 deletions(-)
net/sunrpc/auth_gss/auth_gss.c +1 -2
@@ -867,8 +867,7 @@ gss_create(struct rpc_clnt *clnt, rpc_authflavor_t flavor) err = -EINVAL ; gss_auth->mech =gss_mech_get_by_pseudoflavor (flavor);if (!gss_auth->mech) { -printk (KERN_WARNING "%s: Pseudoflavor %d not found!\n" , - __func__, flavor); +dprintk ("RPC: Pseudoflavor %d not found!\n" , flavor); goto err_free; } gss_auth->service =gss_pseudoflavor_to_service (gss_auth->mech, flavor);
net/sunrpc/clnt.c +1 -1
@@ -360,7 +360,7 @@ static struct rpc_clnt * rpc_new_client(const struct rpc_create_args *args, stru auth =rpcauth_create (args->authflavor, clnt);if (IS_ERR (auth)) { -printk (KERN_INFO "RPC: Couldn't create auth handle (flavor %u)\n" , +dprintk ("RPC: Couldn't create auth handle (flavor %u)\n" , args->authflavor); err =PTR_ERR (auth); goto out_no_auth;
Signature · 1 line
1.8.1.4
Quoted 9 lines · Trond
We should just disable the above warnings.
Note that even if the lease negotiation uses krb5i, the actual mount will continue to use whatever flavour you specify in your 'sec=' mount option (or it will use NFSv4 security negotiation) when doing operations on the filesystem.
The attached patch will turn off those messages for you.
Ah - thx for explanation.
I just applied the patch manually, my patch command was indisposed for some reasons to apply it against current git.
Signature · 3 lines
MfG/Sincerely Toralf Förster pgp finger print: 7B1A 07F4 EC82 0F90 D4C2 8936 872A E508 7DB6 9DA3