From owner-freebsd-stable@FreeBSD.ORG Tue Mar 27 16:28:53 2007 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id A475916A401 for ; Tue, 27 Mar 2007 16:28:53 +0000 (UTC) (envelope-from rblayzor@inoc.net) Received: from mx0-b.inoc.net (mx0-b.inoc.net [64.246.130.28]) by mx1.freebsd.org (Postfix) with ESMTP id 5E0EA13C43E for ; Tue, 27 Mar 2007 16:28:53 +0000 (UTC) (envelope-from rblayzor@inoc.net) Received: from [172.20.8.50] (vanguard.noc.albyny.inoc.net [64.246.135.8]) by mx0-b.inoc.net (build v7.0.4) with ESMTP id 121092651-1941382 for ; Tue, 27 Mar 2007 16:08:47 +0000 (UTC) Message-ID: <4609418E.1000200@inoc.net> Date: Tue, 27 Mar 2007 12:08:46 -0400 From: Robert Blayzor Organization: Independent Network Operations Consortium, LLC User-Agent: Thunderbird 1.5.0.10 (Macintosh/20070221) MIME-Version: 1.0 To: freebsd-stable@freebsd.org X-Enigmail-Version: 0.94.1.2 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Strange NFS Client issue X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Mar 2007 16:28:53 -0000 I ran into rather strange NFS client issue today. I had a directory on an NFS mount (client side) appear to have two empty directories in it, but in fact they were not empty. The directories on the NetApp and other NFS clients showed those same directories populated with files. These files are cloned from other locations using rsync if that makes any difference. On the client that showed the strangeness, if I tried to delete the empty directories "rm -r" returned an error stating "directory not empty", still to the client I could not see any files in the directory. Doing a "du -ks" on the top level dir showed other directories full, but these two empty. The only way I could fix the problem was the umount the mount point and remount it. After that, the directories looked normal again. The the directory was mounted using: filer0:/vol/opt /mnt/opt nfs -T,-L,-b,-i,rw 0 0 Not sure if it's a NFS client side bug, but it sure seems so.... -- Robert Blayzor, BOFH INOC, LLC rblayzor\@(inoc.net|gmail.com) PGP: 0x66F90BFC @ http://pgp.mit.edu Key fingerprint = 6296 F715 038B 44C1 2720 292A 8580 500E 66F9 0BFC YOUR PC's broken and I'VE got a problem? -- The BOFH Slogan