From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Aaron Wiebe" Subject: Re: nfs: lock stuck after interrupt Date: Fri, 18 Apr 2008 08:20:37 -0400 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: bfields-uC3wQj2KruNg9hUCZPvPmw@public.gmane.org, trond.myklebust-41N18TsMXrtuMpJDpNschA@public.gmane.org, eshel-6kx38NOBMPqrIzol8Bc5pA@public.gmane.org, neilb-l3A5Bk7waGM@public.gmane.org, akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org, linux-nfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, linux-fsdevel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: "Miklos Szeredi" Return-path: In-Reply-To: Content-Disposition: inline Sender: linux-nfs-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org List-Id: linux-fsdevel.vger.kernel.org On Fri, Apr 18, 2008 at 7:07 AM, Miklos Szeredi wrote: > 2) then I added your patch on top of that, which did change something > but not really for the better: now even the restarted lock request > doesn't succeed after the interrupt. > > According to my suspicion, this is an issue in the server, while both > referenced patches touch only the client. Note that my little patch purely resolves the situation we were seeing on the client side. We were using Netapps for servers. We're actually using that small patch, against 2.6.22, in production right now and it has still solved our issue. -Aaron -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html