From owner-freebsd-current@FreeBSD.ORG Fri May 3 21:09:21 2013 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 1314E46E for ; Fri, 3 May 2013 21:09:21 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from esa-jnhn.mail.uoguelph.ca (esa-jnhn.mail.uoguelph.ca [131.104.91.44]) by mx1.freebsd.org (Postfix) with ESMTP id 9C72114EB for ; Fri, 3 May 2013 21:09:19 +0000 (UTC) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AqIEAGEmhFGDaFvO/2dsb2JhbABQgz6DPLt3gRB0gh8BAQEDAQEBASArIAsFFhgCAg0ZAikBCRgBDQYIBwQBHASHZQYMsGuQW4EkjEsQfjQHgkCBEwOUaoJCgSaQDIMpIDKBBDU X-IronPort-AV: E=Sophos;i="4.87,607,1363147200"; d="scan'208";a="28332365" Received: from erie.cs.uoguelph.ca (HELO zcs3.mail.uoguelph.ca) ([131.104.91.206]) by esa-jnhn.mail.uoguelph.ca with ESMTP; 03 May 2013 17:09:18 -0400 Received: from zcs3.mail.uoguelph.ca (localhost.localdomain [127.0.0.1]) by zcs3.mail.uoguelph.ca (Postfix) with ESMTP id B3DEDB3F26; Fri, 3 May 2013 17:09:18 -0400 (EDT) Date: Fri, 3 May 2013 17:09:18 -0400 (EDT) From: Rick Macklem To: Hartmut Brandt Message-ID: <834323350.114339.1367615358721.JavaMail.root@erie.cs.uoguelph.ca> In-Reply-To: Subject: Re: files disappearing from ls on NFS MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Originating-IP: [172.17.91.202] X-Mailer: Zimbra 6.0.10_GA_2692 (ZimbraWebClient - FF3.0 (Win)/6.0.10_GA_2692) Cc: current@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: Fri, 03 May 2013 21:09:21 -0000 Hartmut Brandt wrote: > Hi Rick, > > I checked. readdirsize is 64k. > Since the server replied with 4K, I suspect you are seeing the same problem the other reporter has. I'll email if/when I have more information on it. > I will try to do a binary search for the problematic commit next week. > For > this I had to do a local checkout (usually I have the system sources > on > the file server and this fails, of course). > Ok, if you succeed in isolating the commit, that would be great. rick > harti > > On Fri, 3 May 2013, Rick Macklem wrote: > > RM>Hartmut Brandt wrote: > RM>> Hi, > RM>> > RM>> I've updated one of my -current machines this week (previous > update > RM>> was in > RM>> february). Now I see a strange effect (it seems only on NFS > mounts): > RM>> ls or > RM>> even echo * will list only some files (strange enough the first > files > RM>> from > RM>> the normal, alphabetically ordered list). If I change something > in the > RM>> directory (delete a file or create a new one) for some time the > RM>> complete > RM>> listing will appear but after sime time (seconds to a minute or > so) > RM>> again > RM>> only part of the files is listed. > RM>> > RM>> A ktrace on ls /usr/src/lib/libc/gen shows that getdirentries is > RM>> called > RM>> only once (returning 4096). For a full listing getdirentries is > called > RM>> 5 > RM>> times with the last returning 0. > RM>> > RM>> I can still open files that are not listed if I know their name, > RM>> though. > RM>> > RM>> The NFS server is a Windows 2008 server with an OpenText NFS > Server > RM>> which > RM>> works without problems to all the other FreeBSD machines. > RM>> > RM>> So what could that be? > RM>> > RM>Someone else reported missing files returned via "ls" recently, > when > RM>they used a small readdirsize (below 8K). I haven't yet had a > change to try > RM>and reproduce it or do any snooping around. > RM> > RM>There haven't been any recent changes to readdir in the NFS client, > RM>except a trivial one that adds a check for vnode type being VDIR, > RM>so I don't see that it can be a recent NFS change. > RM> > RM>If you can increase the readdirsize, try that to see if it avoids > RM>the problem. "nfsstat -m" shows you what the mount options end up > RM>being after doing the mount. The server might be limiting the > readdirsize > RM>to 4K, so you should check, even if you specify a large value for > RM>the mount. > RM> > RM>rick > RM> > RM>> Regards, > RM>> harti > RM>> _______________________________________________ > RM>> freebsd-current@freebsd.org mailing list > RM>> http://lists.freebsd.org/mailman/listinfo/freebsd-current > RM>> To unsubscribe, send any mail to > RM>> "freebsd-current-unsubscribe@freebsd.org" > RM> > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to > "freebsd-current-unsubscribe@freebsd.org"