Date: Tue, 7 Oct 2014 17:50:06 -0400 From: Garrett Wollman <wollman@csail.mit.edu> To: Rick Macklem <rmacklem@uoguelph.ca> Cc: freebsd-fs@freebsd.org Subject: Re: 9.3 NFS client bug? Message-ID: <21556.24590.269326.188103@khavrinen.csail.mit.edu> In-Reply-To: <603326314.59995969.1412715962746.JavaMail.root@uoguelph.ca> References: <1109402573.59384867.1412683413852.JavaMail.root@uoguelph.ca> <603326314.59995969.1412715962746.JavaMail.root@uoguelph.ca>
next in thread | previous in thread | raw e-mail | index | archive | help
<<On Tue, 7 Oct 2014 17:06:02 -0400 (EDT), Rick Macklem <rmacklem@uoguelph.ca> said: >> By ay chance is your ZFS server allocating a ZFS inode (whatever they >> call it) with a fileno/inode# that doesn't fit in 32 bits? Nope. (And I want to emphasize that Ubuntu clients don't exhibit the problem, so whatever it is, it doesn't appear to be related to the backing filesystem on the server.) > Btw, I tried your bonnie++ command on my test machines, but they failed > part way through because they couldn't allocate boundary tags. (At least > now I can reproduce that easily, although it is the M_NOWAIT case where > the thread just loops in the kernel.) You really need to get some server-class hardware. Perhaps the Foundation can help? I'm currently using the following command, which seems to reproduce the problem reliably on my client and server: bonnie++ -s 0 -n 144:0:0:1:16384 -u 4294967294 -D This minimizes the amount of temporary storage required. -GAWollman
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?21556.24590.269326.188103>