On Fri, 22 Jan 2010 17:13:09 -0500 (EST) Rick Macklem wrote:
On Fri, 22 Jan 2010, Rick Macklem wrote:
There should probably be some sort of 3 way handshake between
the code in nfs_asyncio() after calling nfs_nfsnewiod() and the
code near the beginning of nfssvc_iod(), but I think the
On Sat, 23 Jan 2010, Mikolaj Golub wrote:
I applied your patch to FreeBSD8.0 (the box I get on weekend :-), mounted 10
shares, set vfs.nfs.iodmaxidle=10 (to have nfsiod creation more frequently)
and have been running tests for 4 hours -- just to check the patch does not
break anything. No
On Tue, 19 Jan 2010 10:02:57 +0200 Mikolaj Golub wrote:
So, on some of our freebsd7.1 nfs clients (and it looks like we have had
similar case with 6.3), which have several nfs mounts to the same CentOS 5.3
NFS server (mount options: rw,-3,-T,-s,-i,-r=32768,-w=32768,-o=noinet6), at
some moment
On Fri, 22 Jan 2010, Mikolaj Golub wrote:
We have nonempty nm_bufq, nm_bufqiods = 1, but actually there is no nfsiod
thread run for this mount, which is wrong -- nm_bufq will not be emptied until
some other process starts writing to the nfsmount and starts nfsiod thread for
this mount.
On Fri, 22 Jan 2010 14:37:48 -0500 (EST) Rick Macklem wrote:
--- nfs_bio.c.orig 2010-01-22 15:38:02.0 +
+++ nfs_bio.c 2010-01-22 15:39:58.0 +
@@ -1385,7 +1385,7 @@ again:
*/
if (!gotiod) {
iod = nfs_nfsiodnew();
-
On Fri, 22 Jan 2010, Rick Macklem wrote:
There should probably be some sort of 3 way handshake between
the code in nfs_asyncio() after calling nfs_nfsnewiod() and the
code near the beginning of nfssvc_iod(), but I think the following
somewhat cheesy fix might do the trick:
[stuff deleted]
Hi,
In this thread I have posted to freebsd-fs@ several messages describing our
problem with freebsd7.1 nfs clients. As with the time new info has appeared
and having this all spread in several messages might be a bit confusing, I
want to summarise here what we see and know.
Also I cc to
On Tue, 19 Jan 2010 10:02:57 +0200 Mikolaj Golub wrote:
I have found in the Internet that other people have been observed the similar
problem with FreeBSD6.2 client:
http://forums.freebsd.org/showthread.php?t=1697
Reading this through carefully it looks like the guy did not experience the
