Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S266139AbUIEDB1 (ORCPT ); Sat, 4 Sep 2004 23:01:27 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S266143AbUIEDB1 (ORCPT ); Sat, 4 Sep 2004 23:01:27 -0400 Received: from pat.uio.no ([129.240.130.16]:50161 "EHLO pat.uio.no") by vger.kernel.org with ESMTP id S266139AbUIEDBV convert rfc822-to-8bit (ORCPT ); Sat, 4 Sep 2004 23:01:21 -0400 Subject: Re: why do i get "Stale NFS file handle" for hours? From: Trond Myklebust To: Sven =?ISO-8859-1?Q?K=F6hler?= Cc: linux-kernel@vger.kernel.org, nfs@lists.sourceforge.net In-Reply-To: <413A789C.9000501@upb.de> References: <1094348385.13791.119.camel@lade.trondhjem.org> <413A7119.2090709@upb.de> <1094349744.13791.128.camel@lade.trondhjem.org> <413A789C.9000501@upb.de> Content-Type: text/plain; charset=iso-8859-1 Message-Id: <1094353267.13791.156.camel@lade.trondhjem.org> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Sat, 04 Sep 2004 23:01:07 -0400 Content-Transfer-Encoding: 8BIT X-MailScanner-Information: This message has been scanned for viruses/spam. Contact postmaster@uio.no if you have questions about this scanning X-UiO-MailScanner: No virus found X-UiO-Spam-info: not spam, SpamAssassin (score=0, required 12) Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1088 Lines: 28 P? lau , 04/09/2004 klokka 22:23, skreiv Sven K?hler: > Sorry? Why is my server broken? I'm using kernel 2.6.8.1 with nfs-utils > 1.0.6 on my server, and i don't see, what should be broken. When your server fails to work as per spec, then it is said to be "broken" no matter what kernel/nfs-utils combination you are using. The spec is that reboots are not supposed to clobber filehandles. So, there are 3 possibilities: 1) You are exporting a non-supported filesystem, (e.g. FAT). See the FAQ on http://nfs.sourceforge.org. 2) A bug in your initscripts is causing the table of exports to be clobbered. Running "exportfs" in legacy 2.4 mode (without having the nfsd filesystem mounted on /proc/fs/nfsd) appears to be broken for me at least... 3) There is some other bug in knfsd that nobody else appears to be seeing. Cheers, Trond - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/