On Oct 22, 2013, at 1:27 PM, Ben Greear <greearb@xxxxxxxxxxxxxxx> wrote: > On 10/22/2013 10:21 AM, Weston Andros Adamson wrote: >> … and I think it makes sense to me that this behavior was recently introduced and vers=3 fixes things, because nfsv4 has to do the upcall to GSSD even when sec=sys because it attempts to do krb5i on non superblock related operations (if possible will use, otherwise just uses sys) and this behavior was recently added. NFSv3 does not do this. >> >> -dros > > I have a gssd running on the client, from what I can tell, but no idea if it is working properly > or not. It should be whatever is standard with F17. It's my belief that a GSSD bug is causing this hang and that the bug has been in GSSD for a while, but wasn't hit until recent kernel changes. I'll share more as soon as I figure it out! -dros > > [root@ct523-9292 ~]# ps -auxww|grep gss > root 723 0.0 0.0 35192 504 ? Ss 10:17 0:00 /usr/sbin/rpc.gssd > root 5975 0.0 0.0 109408 872 pts/0 S+ 10:25 0:00 grep --color=auto gss > > Thanks, > Ben > > -- > Ben Greear <greearb@xxxxxxxxxxxxxxx> > Candela Technologies Inc http://www.candelatech.com > -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
