From owner-freebsd-fs@FreeBSD.ORG Tue Sep 5 11:38:57 2006 Return-Path: X-Original-To: freebsd-fs@FreeBSD.ORG Delivered-To: freebsd-fs@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 49AC016A4DD; Tue, 5 Sep 2006 11:38:57 +0000 (UTC) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (lurza.secnetix.de [83.120.8.8]) by mx1.FreeBSD.org (Postfix) with ESMTP id 31CDE43D46; Tue, 5 Sep 2006 11:38:55 +0000 (GMT) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (qjylqn@localhost [127.0.0.1]) by lurza.secnetix.de (8.13.4/8.13.4) with ESMTP id k85BckRR059009; Tue, 5 Sep 2006 13:38:51 +0200 (CEST) (envelope-from oliver.fromme@secnetix.de) Received: (from olli@localhost) by lurza.secnetix.de (8.13.4/8.13.1/Submit) id k85BcjqO059008; Tue, 5 Sep 2006 13:38:45 +0200 (CEST) (envelope-from olli) Date: Tue, 5 Sep 2006 13:38:45 +0200 (CEST) Message-Id: <200609051138.k85BcjqO059008@lurza.secnetix.de> From: Oliver Fromme To: freebsd-amd64@FreeBSD.ORG, freebsd-fs@FreeBSD.ORG, lehmann@ans-netz.de In-Reply-To: <20060904201220.a2707581.lehmann@ans-netz.de> X-Newsgroups: list.freebsd-amd64 User-Agent: tin/1.8.0-20051224 ("Ronay") (UNIX) (FreeBSD/4.11-STABLE (i386)) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.1.2 (lurza.secnetix.de [127.0.0.1]); Tue, 05 Sep 2006 13:38:52 +0200 (CEST) Cc: Subject: Re: NFS lockup when copying a "special" file X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-amd64@FreeBSD.ORG, freebsd-fs@FreeBSD.ORG, lehmann@ans-netz.de List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Sep 2006 11:38:57 -0000 Oliver Lehmann wrote: > Oliver Fromme wrote: > > This doesn't seem to be amd64-specific, so I copy freebsd-fs. I still think it's not amd64-specific. > > [...] > > > > nfs server www:/mnt/space/www: not responding > > > > nfs server www:/mnt/space/www: not responding > > > > nfs server www:/mnt/space/www: not responding > > and again it hit me two times today where I was forced to reboot my > client... this all makes me feel kinda sad - Is there anything which can > be done to help fixing this? Did you try any of the suggestions in my previous mail? E.g.: use TCP NFS transport instead of UDP, and/or force NFSv2 instead of NFSv3. You could also try lowering the MTU (although I think it's not the cause of the problem in your case, but it might be worth a try nonetheless). What are your NFS mount options? What is the size of the file on which the mount became stuck? Do the contents of the file matter? i.e. when you create a file of the same size with dd(1) that contains only zeroes, can you copy it to the NFS share? A bit of tcpdump output might be helpful, too. Please use the options "-vv -s1600", otherwise it's useless. > I nearly lost a really really important pdf > which was generated online and my browser became stuck on showing me the > "save as" dialog... If it happens again, you can mount the NFS share again over the same mount point. Of course that's only an emergency measure, not a solution (and it won't help if an application is accessing the offending file again). Best regards Oliver -- Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing Dienstleistungen mit Schwerpunkt FreeBSD: http://www.secnetix.de/bsd Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. "One of the main causes of the fall of the Roman Empire was that, lacking zero, they had no way to indicate successful termination of their C programs." -- Robert Firth