Date: Tue, 2 Feb 2010 15:11:05 -0500 (EST) From: Rick Macklem <rmacklem@uoguelph.ca> To: alan bryan <alan.bryan@yahoo.com> Cc: freebsd-stable@freebsd.org Subject: Re: Zombie NFS writing from FreeBSD clients to FreeBSD 8.0 server with ZFS Message-ID: <Pine.GSO.4.63.1002021501510.9141@muncher.cs.uoguelph.ca> In-Reply-To: <878205.72256.qm@web50503.mail.re2.yahoo.com> References: <878205.72256.qm@web50503.mail.re2.yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. ---559023410-684387517-1265141465=:9141 Content-Type: TEXT/PLAIN; charset=X-UNKNOWN; format=flowed Content-Transfer-Encoding: QUOTED-PRINTABLE On Tue, 2 Feb 2010, alan bryan wrote: > --- On Wed, 1/6/10, Rick Macklem <rmacklem@uoguelph.ca> wrote: > From: Rick Macklem <rmacklem@uoguelph.ca> > Subject: Re: Zombie NFS writing from FreeBSD clients to FreeBSD 8.0 serve= r with ZFS > To: "alan bryan" <alan.bryan@yahoo.com> > Cc: freebsd-stable@freebsd.org > Date: Wednesday, January 6, 2010, 12:19 PM >=20 >=20 > On Wed, 6 Jan 2010, alan bryan wrote: >=20 > > I have a AMD64 FreeBSD 8.0 server with ZFS filesystem > being shared via NFS.=A0 These are being accessed by the > clients.=A0 The clients are a mix of FreeBSD 6.2 32bit > and FreeBSD 7.0 64bit.=A0 I have seen similar behavior > from both versions of FreeBSD as clients. > > > [stuff related to lotsa writes being done snipped] > > > > Any ideas on what to try, where to look for more > insight, etc...?? > > > - Are they the same write being retried over and over? yes - it appears so > - Is the server replying to them with an error? yes >=20 > The above might give some insight into what's happening, Didn't help much. The server is replying with NFS3ERR_IO (EIO) for some reason. Unfortunately EIO is the catch all for just about everything. (There is only one case in the NFS server code that generates EIO and that would be caused by a bogus data mbuf list.) As such, I suspect the EIO is coming from ZFS for some reason, but can't be sure. Btw, a binary capture using tcpdump can be read into wireshark, which is much better at decoding NFS etc than tcpdump. rick ---559023410-684387517-1265141465=:9141--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.GSO.4.63.1002021501510.9141>