From owner-freebsd-fs@FreeBSD.ORG Thu Oct 25 02:03:54 2012 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 45D12A08 for ; Thu, 25 Oct 2012 02:03:54 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from mail-pa0-f54.google.com (mail-pa0-f54.google.com [209.85.220.54]) by mx1.freebsd.org (Postfix) with ESMTP id 0DAF68FC0A for ; Thu, 25 Oct 2012 02:03:53 +0000 (UTC) Received: by mail-pa0-f54.google.com with SMTP id bi1so839127pad.13 for ; Wed, 24 Oct 2012 19:03:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:date:to:cc:subject:message-id:reply-to:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; bh=qdCWmp5nga+mY1Vi1DmJlF6jjWTZUhCXldPJ2M/ymEA=; b=KTFqYM9dE+kQ5q+eDeU7DbRSeZ4lXAo/EIwIHrBAR3Kd7IoxZKZqEl2r3noz7BwgoS YbBlUpIH2XnprPGCNqoIKiK2T/k2Ds54P6DD5u3PJGRFFJ73MW3GFm0CeqeD1daZbG9K Q9ofADDQHNzLPqpIzLm6PFqJJeaa1zHkHjvZ6+Vi66mXoLlqOee6+rYN3vMVnSHNZ/6L PdVPSW8q8CamDwvxYY7aRnaczHfqmqjvzNL3QIFlIGjCXtWOxG3FxDaKPnLx/0R72RGk IKRk8ZxlFJKj6Kdy/u1ha/B8NUQTVHcGibnCEkB5xMvVJBgLGE7bHSyAF90ax1U0iOv4 M+BQ== Received: by 10.68.226.167 with SMTP id rt7mr55755186pbc.94.1351130633326; Wed, 24 Oct 2012 19:03:53 -0700 (PDT) Received: from pyunyh@gmail.com (lpe4.p59-icn.cdngp.net. [114.111.62.249]) by mx.google.com with ESMTPS id pf4sm9492879pbc.38.2012.10.24.19.03.49 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 24 Oct 2012 19:03:51 -0700 (PDT) Received: by pyunyh@gmail.com (sSMTP sendmail emulation); Thu, 25 Oct 2012 11:03:44 -0700 From: YongHyeon PYUN Date: Thu, 25 Oct 2012 11:03:44 -0700 To: Yamagi Burmeister Subject: Re: Can not read from ZFS exported over NFSv4 but write to it Message-ID: <20121025180344.GC3267@michelle.cdnetworks.com> References: <20121023204623.a1eef4f99b5f786050229b6c@yamagi.org> <1579346453.2736080.1351029315835.JavaMail.root@erie.cs.uoguelph.ca> <20121024213602.b727c557f0332f28a66f87cc@yamagi.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20121024213602.b727c557f0332f28a66f87cc@yamagi.org> User-Agent: Mutt/1.4.2.3i Cc: freebsd-fs@freebsd.org X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: pyunyh@gmail.com List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 25 Oct 2012 02:03:54 -0000 On Wed, Oct 24, 2012 at 09:36:02PM +0200, Yamagi Burmeister wrote: > Hello > > On Tue, 23 Oct 2012 17:55:15 -0400 (EDT) > Rick Macklem wrote: > > > > # ZFS > > > /usr/home/yamagi > > > # UFS > > > /mnt > > > V4: / -sec=sys 192.168.0.13 > > > > > For ZFS, all volumes down to yamagi must be exported. > > You don't show what your ZFS setup is, but you either > > need to export "home" and "usr" if those are ZFS volumes. > > (The above /etc/exports would be ok, only if /, /usr and > > /home are all UFS volumes and /usr/home/yamagi is the root > > of a ZFS volume.) For UFS, non-exported volumes can be > > traversed by "mount", but for ZFS that is not the case. > > > > The only way I know of to fix this inconsistency is to > > disable the traversal capability for UFS, but that would > > be a POLA violation, so the inconsistency (caused by ZFS > > checking exports itself instead of leaving to the VFS layer) > > remains. > > > > OR > > you can specify the root of V4 in the exported volume. > > For example, you could: > > # ZFS > > /usr/home/yamagi > > V4: /usr/home/yamagi -sec=sys 192.168.0.13 > > > > And then the client mount would be: > > a:/ on /mnt > > since "/" would be at /usr/home/yamagi. (If you do this, > > the /mnt UFS volume wouldn't be mountable via NFSv4.) > > Okay, I didn't know that. What about adding a small notice to the nfsv4 > (4) manpage to put users into the right direction? > > A correct /etc/exports didn't solve the problem. So I took some > tcpdumps, while analyzing them I noticed that packages send by client > never arived at the server. After I changed the NIC (I was using a > rather cheap age(4) onboard NIC) everything worked okay. Apparently > NFSv4 exhibited a bug in the driver that never showed up before. I'm age(4) is cheap and consumer grade controller but it shows good performance on various network loads. It's much better choice than using other cheap controllers. Would you show me dmesg output(age(4) and atphy(4) only)? And try disabling TSO or TX checksum offloading and see whether that makes any difference. I remember age(4) had a 64bit DMA bug but it was fixed long time ago. > sorry that i've wasted your time. > > Thanks again, > Yamagi