Re: [PATCH 0/2] Fix regression on NFS in mainline kernel

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Fri, 2013-01-04 at 10:05 +-0000, Mario Bachmann wrote:
+AD4- Luis Henriques +ADw-luis.henriques+AEA-...+AD4- writes:
+AD4- 
+AD4- +AD4- 
+AD4- +AD4- On Thu, Apr 19, 2012 at 05:29:09PM +-0000, Myklebust, Trond wrote:
+AD4- +AD4- +AD4- On Thu, 2012-04-19 at 14:48 +-0100, Luis Henriques wrote:
+AD4- +AD4- +AD4- +AD4- On Thu, Apr 19, 2012 at 10:30:25AM +-0100, Luis Henriques wrote:
+AD4- +AD4- +AD4- +AD4- +AD4- On Wed, Apr 18, 2012 at 01:36:52PM -0400, Trond Myklebust wrote:
+AD4- +AD4- +AD4- +AD4- +AD4- +AD4- The first patch addresses the Oops.
+AD4- +AD4- +AD4- +AD4- +AD4- +AD4- The second will hopefully address the looping.
+AD4- +AD4- +AD4- +AD4- +AD4- +AD4- 
+AD4- +AD4- +AD4- +AD4- +AD4- +AD4- Trond Myklebust (2):
+AD4- +AD4- +AD4- +AD4- +AD4- +AD4-   NFSv4: Ensure that the LOCK code sets exception-+AD4-inode
+AD4- +AD4- +AD4- +AD4- +AD4- +AD4-   NFSv4: Ensure that we check lock exclusive/shared type against open
+AD4- +AD4- +AD4- +AD4- +AD4- +AD4-     modes
+AD4- +AD4- +AD4- +AD4- +AD4- +AD4- 
+AD4- +AD4- +AD4- +AD4- +AD4- +AD4-  fs/nfs/nfs4proc.c +AHw-   23 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+---
+AD4- +AD4- +AD4- +AD4- +AD4- +AD4-  1 files changed, 21 insertions(+-), 2 deletions(-)
+AD4- I use kernel 3.7.1 from kernel.org which has the patches included, 
+AD4- which should fix the problems (I checked the source code). But:
+AD4- I get +ACI-NFS: nfs4+AF8-reclaim+AF8-open+AF8-state: Lock reclaim failed+ACEAIg- on the 
+AD4- client, which mounts home over nfs4. 
+AD4- I get senseless network traffic (50MB/s on my gigabit network). 
+AD4- Finally I get Kernel Ops on the Server sometimes. 

Lock reclaiming is not guaranteed to succeed+ADs- it all depends on why the
lock was lost in the first place. Did the server restart, or did a
network partition occur? Was some other process able to take that lock
(or even delete the file, doh+ACE-), before your client could reclaim it?

That said, if the server is Oopsing, then you have a broken server. I'd
suggest posting that Oops to this list first.

-- 
Trond Myklebust
Linux NFS client maintainer

NetApp
Trond.Myklebust+AEA-netapp.com
www.netapp.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


[Index of Archives]     [Linux Filesystem Development]     [Linux USB Development]     [Linux Media Development]     [Video for Linux]     [Linux NILFS]     [Linux Audio Users]     [Yosemite Info]     [Linux SCSI]

  Powered by Linux