gmane.linux.nfsv4

Re: [LONG] Kerberized NFSv4: rpc.idmapd only "sees" root principal

Guillaume Rousse — 2010-09-05T17:06:07

_______________________________________________
NOTE: THIS LIST IS DEPRECATED.  Please use linux-nfs< at >vger.kernel.org instead.
(To subscribe to linux-nfs< at >vger.kernel.org: send "subscribe linux-nfs" in the body of a message to majordomo< at >vger.kernel.org.)

NFSv4 mailing list
NFSv4< at >linux-nfs.org
http://linux-nfs.org/cgi-bin/mailman/listinfo/nfsv4

Re: krb5 authentication error with nfs client 1.2.x

Richard Smits — 2010-09-01T06:32:23

Yes, a co-worker pointed out to me that this was an official bug at 
suse. Also an email from someone.

Quote :
There is a bug report on openSUSE 11.3 for this issue. But, it looks
like SLED 11 SP1 also got affected.
https://bugzilla.novell.com/show_bug.cgi?id=614293

Thanks for the info. I know what to do.

Greetings ... Richard


_______________________________________________
NOTE: THIS LIST IS DEPRECATED.  Please use linux-nfs< at >vger.kernel.org instead.
(To subscribe to linux-nfs< at >vger.kernel.org: send "subscribe linux-nfs" in the body of a message to majordomo< at >vger.kernel.org.)

NFSv4 mailing list
NFSv4< at >linux-nfs.org
http://linux-nfs.org/cgi-bin/mailman/listinfo/nfsv4

Re: krb5 authentication error with nfs client 1.2.x

J. Bruce Fields — 2010-08-31T18:30:23

Have you filed a SELD bug?  Right off hand it looks like
599511589ca7ddb3b2eac8d3aa5b0b38be7a7691 in upstream libtirpc.

--b.

_______________________________________________
NOTE: THIS LIST IS DEPRECATED.  Please use linux-nfs< at >vger.kernel.org instead.
(To subscribe to linux-nfs< at >vger.kernel.org: send "subscribe linux-nfs" in the body of a message to majordomo< at >vger.kernel.org.)

NFSv4 mailing list
NFSv4< at >linux-nfs.org
http://linux-nfs.org/cgi-bin/mailman/listinfo/nfsv4

Re: Linux pNFS status meeting 08/26

Fred Isaman — 2010-08-31T18:11:06

Because in your suggested order, the IO code would not work correctly
until the layoutreturn code is added.  With our ordering, at each step
there is fully functional code that does not depend for correctness on
future patches.  (Note that the layoutcommit code is basically
optional for the file driver, so is last.)


Trond has said that enums taken direct from the spec can include their
full definitions, even if not all are used yet, so those that we
include should be complete.


This will be more like what you ask about below...the invocation of
pnfs code on mount/umount, and calls to pnfs_update_layout.


Very roughly, the pnfs.c code stripped of anything related to
LAYOUTRETURN, LAYOUTCOMMIT, or needed only for block/object drivers.


We've been told to avoid having dead code.  So any patch which
includes a function also has callers of that function.  Thus we need
to keep the ordering of 2 and 3.

Ignoring how we split up the code for our first submission for the
moment, we should be sending out the act

krb5 authentication error with nfs client 1.2.x

Richard Smits — 2010-08-31T14:49:19

Hello,

We are working on a problem here what is getting bigger. I will explain.

Our clients are using SLED 11. If they upgrade to sp1, they get a newer 
nfs client.

Client before update : nfs-client-1.1.3-18.17
Client after update : nfs-client-1.2.1-2.6.6

We are using krb5 authentication with an active directory. The nfs mount 
we are trying to make is on a netapp nashead.

The scenario is as followes. The client works as expected. When you ONLY 
upgrade the nfsclient package, we get an error :

mount /mnt/nfs/
mount.nfs4: access denied by server while mounting srvxxx:/vol/vol1/target

I have enabled logging on the rpcgssd :

Aug 31 16:17:09 vmlinux12 rpc.gssd[14072]: Full hostname for 
'srvxxx.domain.net' is 'srvxxx.domain.net'
Aug 31 16:17:09 vmlinux12 rpc.gssd[14072]: Full hostname for 
'server.domain.net' is 'server.domain.net'
Aug 31 16:17:09 vmlinux12 rpc.gssd[14072]: Key table entry not found 
while getting keytab entry for 'root
/server.domain.net< at >DOMAIN.NET'
Aug 31 16:17:09 vmlinux12 rpc.gssd[14

Re: [PATCH 0/2] Make libtirpc work with old style portmapper

Chuck Lever — 2010-08-30T23:48:02

On Aug 30, 2010, at 12:19 PM, Olaf Kirch wrote:


Agreed, but for various reasons, the symptoms don't necessarily immediately imply what is needed to correct the problem.

Re: [PATCH 0/2] Make libtirpc work with old style portmapper

Chuck Lever — 2010-08-30T15:59:18

On Aug 30, 2010, at 9:03 AM, Olaf Kirch wrote:


I've seen a couple of other requests for this feature, and wrote some patches last year that did something similar.  I never got around to finishing them.

I worried at the time that this might introduce a security weakness, since, after all, the rpcbind SET operation goes over AF_UNIX, which is authenticated, but pmap uses sockets with privileged ports to detect authorized users.  I see that your logic uses the pmap SET/UNSET calls by default.  This bypasses AF_UNIX completely in pretty much all local cases, which changes the behavior of rpcb_set() and rpcb_unset(), and could break the local rpcbind security model.  It might be better to use pmap_setunset() only when local_rpcb() fails.

Another minor problem I think I remember is that if libtirpc is used on a system (perhaps because it is statically linked with said ISV RPC-enabled application) that does not have /etc/netconfig installed, the transport creation logic in rpcb_clnt.c simply doesn't work.

Re: [RFC][PATCH] nfs4: set exception->state beforecallingnfs4_handle_exception() for locks

Bian Naimeng — 2010-08-25T05:45:32

   ... snip ...


En... Why we must invoke nfs4_state_mark_reclaim_nograce at nfs4_state_end_reclaim_reboot?
I think nfs4_state_mark_reclaim_nograce should be called when client catch a state error
(such as BAD_STATEID、EXPIRED) at no grace period. 

And it's not needed for reboot recovery (after client catch STALE_CLIENTID、STATLE_STATEID).

So, what about this one?

----------------------------------------------------------

Signed-off-by: Mi Jinlong <mijinlong< at >cn.fujitsu.com>
Signed-off-by: Bian Naimeng <biannm< at >cn.fujitsu.com>

---
 fs/nfs/nfs4proc.c  |   12 +++++++++---
 fs/nfs/nfs4state.c |    8 +++-----
 2 files changed, 12 insertions(+), 8 deletions(-)

diff --git a/fs/nfs/nfs4proc.c b/fs/nfs/nfs4proc.c
index 089da5b..a2f56bc 100644
--- a/fs/nfs/nfs4proc.c
+++ b/fs/nfs/nfs4proc.c
< at >< at > -4233,7 +4233,9 < at >< at > static int _nfs4_do_setlk(struct nfs4_state *state, int cmd, struct file_lock *f
 static int nfs4_lock_reclaim(struct nfs4_state *state, struct file_lock *request)
 {
 struct nfs_server *server = NFS

[RFC][PATCH] nfs4: set exception->state before callingnfs4_handle_exception() for locks

Mi Jinlong — 2010-08-24T09:36:29

At the latest kernel, it is calling nfs4_handle_exception() without 
setting exception->state for locks. That cause client can't get lock 
success when new_lock_owner != 0.

nfs4_recovery_handle_error() also be called after nfs4_proc_renew, 
but claim OPEN proc always after RENEW proc. Maybe the function 
nfs4_state_end_reclaim_reboot() shouldn't be called when client 
get a NFS4ERR_STALE_CLIENTID error.

This patch sets exception->state before calling nfs4_handle_exception()
and also modifies nfs4_recovery_handle_error().

Signed-off-by: Mi Jinlong <mijinlong< at >cn.fujitsu.com>

---
 fs/nfs/nfs4proc.c  |   12 +++++++++---
 fs/nfs/nfs4state.c |    4 ++--
 2 files changed, 11 insertions(+), 5 deletions(-)

diff --git a/fs/nfs/nfs4proc.c b/fs/nfs/nfs4proc.c
index 089da5b..a2f56bc 100644
--- a/fs/nfs/nfs4proc.c
+++ b/fs/nfs/nfs4proc.c
< at >< at > -4233,7 +4233,9 < at >< at > static int _nfs4_do_setlk(struct nfs4_state *state, int cmd, struct file_lock *f
 static int nfs4_lock_reclaim(struct nfs4_state *state, struct file_lock *reque

Re: [RFC] Should client get lock success after NFSv4 server restart?

Mi Jinlong — 2010-08-20T10:17:49

Hi all,

Trond Myklebust 写道:


When I try to fix this problem with a patch that as below,
but client get into infinite loop. Should it make a new state for exception there??

When using tcpdump, I found client just send RENEW, SETCLIENTID, SETCLIENTID_CONFIRM,
but not send OPEN request. After that, client get into infinite loop of LOCK.

---------------
diff --git a/fs/nfs/nfs4proc.c b/fs/nfs/nfs4proc.c
index 7ffbb98..c26dc5a 100644
--- a/fs/nfs/nfs4proc.c
+++ b/fs/nfs/nfs4proc.c
< at >< at > -4315,7 +4315,9 < at >< at > out:
 
 static int nfs4_proc_setlk(struct nfs4_state *state, int cmd, struct file_lock *request)
 {
-struct nfs4_exception exception = { };
+struct nfs4_exception exception = {
+.state = state,
+};
 int err;
 
 do {

Thanks,
Mi Jinlong

_______________________________________________
NOTE: THIS LIST IS DEPRECATED.  Please use linux-nfs< at >vger.kernel.org instead.
(To subscribe to linux-nfs< at >vger.kernel.org: send "subscribe linux-nfs" in the body of a message to majordomo< at >vger.kernel.org.)

NFSv4 mailing

Re: Can create and delete but not overwrite

David Brodbeck — 2010-08-13T22:17:57

On Aug 13, 2010, at 1:47 PM, Steve Gaarder wrote:

Is ID mapping working properly?

Can create and delete but not overwrite

Steve Gaarder — 2010-08-13T20:47:42

I have a strange problem with Kerberos security and NFVv4.

I have two servers, one running RHEL 4 (kernel 2.6.9-89.0.25.ELsmp) and 
the other RHEL 5 (2.6.18-194.3.1.el5).  Clients running either OS work 
fine.

I have one user who is using Ubuntu (9.04 Jaunty; the kernel is 
2.6.28-19-generic #61-Ubuntu).  On that machine, he can access filesystems 
on the RHEL 5 server fine. Using filesystems mounted from the RHEL 4 
server, authenticated users can create and write files, but they cannot 
write to an existing file. SO, for example,

echo foo >foo

works, but a subsequent

echo foo >foo

says "Input/Output Error".

Any ideas?

就知道中秋节你会被铺天盖地的短信包围，英明的乙辉缇腿米８？绻，闪过卖茶叶蛋的老太太，钻进你的耳朵：祝中秋炖郑

carrierebouvy — 2010-08-10T21:46:15

_______________________________________________
NOTE: THIS LIST IS DEPRECATED.  Please use linux-nfs< at >vger.kernel.org instead.
(To subscribe to linux-nfs< at >vger.kernel.org: send "subscribe linux-nfs" in the body of a message to majordomo< at >vger.kernel.org.)

NFSv4 mailing list
NFSv4< at >linux-nfs.org
http://linux-nfs.org/cgi-bin/mailman/listinfo/nfsv4

Re: remote I/O error nfs4err_resource

Swaran Singh Mommy — 2010-08-08T05:32:35

_______________________________________________
NOTE: THIS LIST IS DEPRECATED.  Please use linux-nfs< at >vger.kernel.org instead.
(To subscribe to linux-nfs< at >vger.kernel.org: send "subscribe linux-nfs" in the body of a message to majordomo< at >vger.kernel.org.)

NFSv4 mailing list
NFSv4< at >linux-nfs.org
http://linux-nfs.org/cgi-bin/mailman/listinfo/nfsv4

办公技能

高级管理人员 — 2010-08-06T21:12:33

您   好：


        我司将于2010年8月13-14日 上 海 、8月20-21日  深 圳 、8月27-28日  北 京 三地举办:

《 企业白领核心办公技能（PPT+Excel）高级应用v3.0 》公开课！由企业信息化领域资深专家，

微软认证专家、IPMA认证项目经理、经济分析师、国际职业讲师协会认证讲师----陈 剑 先生主讲！

详细内容请来电咨询或发邮件至：baoming01< at >126.com 索取！　（来信请注明课程名称！）谢谢！ 


咨*询*电*话：0-2-0--3-4-8-0-6-0-3-9 、3-5-6-2-9-4-8-9  陈先生 、曾小姐

报*名*邮*箱：baoming01< at >126.com


如不需要此类信息,请发送主题“移除”或“delete”到：tuidin01< at >163.com 　谢谢!
_______________________________________________
NOTE: THIS LIST IS DEPRECATED.  Please use linux-nfs< at >vger.kernel.org instead.
(To subscribe to linux-nfs< at >vger.kernel.org: send "subscribe linux-nfs" in the body of a message to majordomo< at >vger.kernel.org.)

NFSv4 mailing list
NFSv4< at >linux-nfs.org
htt

Linux pNFS status meeting 08/05

Marc Eshel — 2010-08-05T03:53:29

Meeting on Thursday 08/05/10 at 9:30 AM pacific time (12:30 PM UMICH time)

Marc. 
_______________________________________________
NOTE: THIS LIST IS DEPRECATED.  Please use linux-nfs< at >vger.kernel.org instead.
(To subscribe to linux-nfs< at >vger.kernel.org: send "subscribe linux-nfs" in the body of a message to majordomo< at >vger.kernel.org.)

NFSv4 mailing list
NFSv4< at >linux-nfs.org
http://linux-nfs.org/cgi-bin/mailman/listinfo/nfsv4

Re: [RFC] Should client get lock success after NFSv4 server restart?

Trond Myklebust — 2010-08-04T01:42:42

Doh! We're calling nfs4_handle_exception() without setting
exception->state in nfs4_proc_setlk(), nfs4_lock_expired() and
nfs4_lock_reclaim().

Sorry about that. I'll draft a patch tomorrow.

Cheers
  Trond

_______________________________________________
NOTE: THIS LIST IS DEPRECATED.  Please use linux-nfs< at >vger.kernel.org instead.
(To subscribe to linux-nfs< at >vger.kernel.org: send "subscribe linux-nfs" in the body of a message to majordomo< at >vger.kernel.org.)

NFSv4 mailing list
NFSv4< at >linux-nfs.org
http://linux-nfs.org/cgi-bin/mailman/listinfo/nfsv4

Re: [RFC] Should client get lock success after NFSv4 server restart?

Mi Jinlong — 2010-08-04T01:32:20

Hi Trond,

Trond Myklebust 写道:

  No. 

  I think those release after your's patch a2c0b9e291208f65221a0ad8a0c80a377707d480
  have this problem as well.

  Because, I test at 2.6.32 with this patch, the problem appears;
  without it, there is no problem. So, I think this patch cause this problem.

  As reading code of 2.6.35, the problem appears at 

     nfs4_proc_setlk
      |
       ->nfs4_handle_exception
          |
           ->  256      case -NFS4ERR_STALE_STATEID:
               257              if (state == NULL)
               258                    break;

thanks,
Mi Jinlong

_______________________________________________
NOTE: THIS LIST IS DEPRECATED.  Please use linux-nfs< at >vger.kernel.org instead.
(To subscribe to linux-nfs< at >vger.kernel.org: send "subscribe linux-nfs" in the body of a message to majordomo< at >vger.kernel.org.)

NFSv4 mailing list
NFSv4< at >linux-nfs.org
http://linux-nfs.org/cgi-bin/mailman/listinfo/nfsv4

Re: remote I/O error nfs4err_resource

Richard Smits — 2010-08-03T20:49:27

Hello,

This issue is resolved. The upgrade to ontap 7.3.3P4 has fixed this issue.

 > Current versions of Linux have an issue when you use file locking: 
they can end up using a lot of stateids if you have one or several
applications does a lot of lock/unlock cycles but where the file stateid
never gets closed.

netapp just changed the respond from err_resource to err_jukebox

Greetings ...

On 15-7-2010 22:34, Guillaume Rousse wrote:
_______________________________________________
NOTE: THIS LIST IS DEPRECATED.  Please use linux-nfs< at >vger.kernel.org instead.
(To subscribe to linux-nfs< at >vger.kernel.org: send "subscribe linux-nfs" in the body of a message to majordomo< at >vger.kernel.org.)

NFSv4 mailing list
NFSv4< at >linux-nfs.org
http://linux-nfs.org/cgi-bin/mailman/listinfo/nfsv4

Re: [RFC] Should client get lock success after NFSv4 server restart?

Trond Myklebust — 2010-08-03T17:07:12

Well, yes, but I understand Mi to be saying that this reclaim process
should be invisible to the user processes.

IOW: the second fcntl() should return the same result to the user
process whether or not there was a server reboot in Step 2. I would
agree with that.

Is this happening on the just-released 2.6.35?

Cheers
  Trond

_______________________________________________
NOTE: THIS LIST IS DEPRECATED.  Please use linux-nfs< at >vger.kernel.org instead.
(To subscribe to linux-nfs< at >vger.kernel.org: send "subscribe linux-nfs" in the body of a message to majordomo< at >vger.kernel.org.)

NFSv4 mailing list
NFSv4< at >linux-nfs.org
http://linux-nfs.org/cgi-bin/mailman/listinfo/nfsv4

Re: [RFC] Should client get lock success after NFSv4 server restart?

Chuck Lever — 2010-08-03T15:14:47

I don't think so.  After an NFSv4 server restarts, it won't recognize
any of the clients any longer.  My understanding is that it returns
STALE_STATEID to request that the client perform reboot recovery (ie,
perform SETCLIENTID again, and then attempt to re-establish previous
lock state using CLAIM_PREV opens).
_______________________________________________
NOTE: THIS LIST IS DEPRECATED.  Please use linux-nfs< at >vger.kernel.org instead.
(To subscribe to linux-nfs< at >vger.kernel.org: send "subscribe linux-nfs" in the body of a message to majordomo< at >vger.kernel.org.)

NFSv4 mailing list
NFSv4< at >linux-nfs.org
http://linux-nfs.org/cgi-bin/mailman/listinfo/nfsv4