Date: Wed, 25 Nov 2009 11:23:52 -0500 (EST) From: Rick Macklem <rmacklem@uoguelph.ca> To: =?utf-8?B?R2Vycml0IEvDvGhu?= <gerrit@pmp.uni-hannover.de> Cc: freebsd-stable@freebsd.org Subject: Re: zfs/nfs mkstemp() failure & subsequent hangs Message-ID: <Pine.GSO.4.63.0911251119170.4663@muncher.cs.uoguelph.ca> In-Reply-To: <20091120132945.e2031bfb.gerrit@pmp.uni-hannover.de> References: <20091120132945.e2031bfb.gerrit@pmp.uni-hannover.de>
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-959030623-1259166232=:4663 Content-Type: TEXT/PLAIN; charset=X-UNKNOWN; format=flowed Content-Transfer-Encoding: QUOTED-PRINTABLE On Fri, 20 Nov 2009, Gerrit K=C3=BChn wrote: > Hi all, > > I have a 8.0-PRERELEASE zfs/nfs server here that complains about i/o > errors when using rsync on a nfs client: > > rsync: mkstemp > "/usr/portage/metadata/cache/app-mobilephone/.ksms-0.1.2.4.BynVFw" failed= : > Input/output error (5) > > > I found this to be quite similar to kern/135412. However, this one > is said to be fixed and only applicable to 7-stable anyway. > Furthermore, after this happened, I tried to access files on the server > from the zfs filesystem concerned and found that I cannot access the fs > anymore. ls hangs in state zfs, so do mountd and zfs unmount. > > Questions: > Should I open a new PR for this? Gerrit reports that the fix recently committed to FreeBSD-current as r199616 (and will be MFC'd to stable/8 in about 2 weeks unless problems with it are reported) has fixed this problem. Thanks to Gerrit for reporting it and testing the fix, rick ---559023410-959030623-1259166232=:4663--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.GSO.4.63.0911251119170.4663>