All of lore.kernel.org
 help / color / mirror / Atom feed
From: James Bardin <jbardin@bu.edu>
To: Steve Dickson <SteveD@redhat.com>
Cc: nfs@lists.sourceforge.net
Subject: Re: nfs sec=krb5 on RHEL and CentOS
Date: Wed, 24 Jan 2007 15:58:04 -0500	[thread overview]
Message-ID: <45B7C85C.80105@bu.edu> (raw)
In-Reply-To: <45B73D93.1020508@RedHat.com>

Sorry Steve,

I accidentally rebooted into kernel 2.6.19 when I tested the patches.
Same problem still, and on our 64bit systems, everything fails with 
statfs error 13.

Here's the dmesg errors:
call_verify: auth check failed
call_verify: auth check failed
call_verify: auth check failed
RPC call_verify: retry failed, exit EIO

and:
nfs_statfs: statfs error = 13

Attached is the trace

the commands were:
$ mkdir newdir
$ ls
$ cd newdir
$ echo TESTSTRING > newfile
$ ls

thanks
-jim


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

  parent reply	other threads:[~2007-01-24 20:58 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-21 22:11 nfs sec=krb5 on RHEL and CentOS james bardin
2007-01-24 11:05 ` Steve Dickson
2007-01-24 15:03   ` James Bardin
2007-01-24 20:58   ` James Bardin [this message]
2007-01-24 23:39     ` J. Bruce Fields
2007-01-25  0:14       ` james bardin
2007-01-25 19:43         ` James Bardin
2007-01-25 21:56           ` James Bardin
2007-01-25 23:14             ` Kevin Coffman
2007-01-25 23:40               ` James Bardin
2007-01-26 17:07                 ` James Bardin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=45B7C85C.80105@bu.edu \
    --to=jbardin@bu.edu \
    --cc=SteveD@redhat.com \
    --cc=nfs@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.