From owner-freebsd-current@FreeBSD.ORG Wed Jul 10 12:32:26 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id E0693D27 for ; Wed, 10 Jul 2013 12:32:26 +0000 (UTC) (envelope-from clbuisson@orange.fr) Received: from smtp.smtpout.orange.fr (smtp05.smtpout.orange.fr [80.12.242.127]) by mx1.freebsd.org (Postfix) with ESMTP id 86D531AE0 for ; Wed, 10 Jul 2013 12:32:25 +0000 (UTC) Received: from localhost ([92.136.146.119]) by mwinf5d61 with ME id ycYJ1l0022anTkU03cYJ7W; Wed, 10 Jul 2013 14:32:19 +0200 Message-ID: <51DD5451.2010801@orange.fr> Date: Wed, 10 Jul 2013 14:32:17 +0200 From: Claude Buisson User-Agent: Mozilla/5.0 (X11; FreeBSD i386; rv:17.0) Gecko/20130624 Thunderbird/17.0.7 MIME-Version: 1.0 To: FreeBSD Current Subject: "Stale NFS file handle" for NFS exported UFS from r252435 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: rmacklem@freebsd.org, pfg@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Jul 2013 12:32:26 -0000 Hi, Upgrading a CURRENT amd64 pure UFS system (watson) from r249744 to r253007, I have hit the following: claude@zorglub$ mount_nfs watson:/home /mnt claude@zorglub$ /bin/ls /mnt/ claude doc.old ports.old sysref distfiles obj portsperso xorg-dev doc ports src xtrafiles claude@zorglub$ /bin/ls /mnt/claude ls: /mnt/claude: Stale NFS file handle claude@zorglub$ /bin/ls /mnt/ports.old CHANGES UPDATING dns multimedia textproc COPYRIGHT accessibility editors net www ... some directories may be listed, for the others the result is "Stale NFS file handle" This exists for a 8.4-STABLE client system, for a 9.1-STABLE client system, and also with a local mount (localhost) on the server system itself. I checked with memsticks of official snapshots (to eliminate the influence of local patches and customized kernels), with the result: FreeBSD-10.0-CURRENT-amd64-20130630-r252387-memstick is not affected FreeBSD-10.0-CURRENT-amd64-20130707-r252887-memstick is affected Doing a binary search on the kernel source (without any patch) lead to the "culprit": ---------------------------------------------------------------------- Author: pfg Date: Mon Jul 1 03:00:15 2013 New Revision: 252435 URL: http://svnweb.freebsd.org/changeset/base/252435 Log: Change i_gen in UFS to an unsigned type. In UFS, i_gen is a random generated value and there is not way for it to be negative. Actually, the value of i_gen is just used to match bit patterns and it is of not consequence if the values are signed or not. Following other filesystems, set it to unsigned and use it as such, Discussed by: mckusick Reviewed by: mckusick (previous version) MFC after: 4 weeks Modified: head/sys/ufs/ffs/ffs_vfsops.c head/sys/ufs/ufs/dinode.h head/sys/ufs/ufs/inode.h head/sys/ufs/ufs/ufs_extattr.c ---------------------------------------------------------------------- which is entirely UFS (not NFS) related. CCing pfg@ as the committer, and rmacklem@ just in case.. Thanks for your attention Claude Buisson