From owner-freebsd-fs@FreeBSD.ORG Thu Oct 25 19:41:32 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 6A82650E for ; Thu, 25 Oct 2012 19:41:32 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from esa-jnhn.mail.uoguelph.ca (esa-jnhn.mail.uoguelph.ca [131.104.91.44]) by mx1.freebsd.org (Postfix) with ESMTP id 1C3A68FC14 for ; Thu, 25 Oct 2012 19:41:31 +0000 (UTC) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Ap4EAIyUiVCDaFvO/2dsb2JhbABEhha9KYIeAQEEASMmMAUWDgoCAg0ZAiM2BhOHcgMJBqtJiRYNiVSBIIlaZ4VagRMDlCGBVYsthRCDC4F9 X-IronPort-AV: E=Sophos;i="4.80,650,1344225600"; d="scan'208";a="185231321" Received: from erie.cs.uoguelph.ca (HELO zcs3.mail.uoguelph.ca) ([131.104.91.206]) by esa-jnhn-pri.mail.uoguelph.ca with ESMTP; 25 Oct 2012 15:41:30 -0400 Received: from zcs3.mail.uoguelph.ca (localhost.localdomain [127.0.0.1]) by zcs3.mail.uoguelph.ca (Postfix) with ESMTP id 831C9B4069; Thu, 25 Oct 2012 15:41:30 -0400 (EDT) Date: Thu, 25 Oct 2012 15:41:30 -0400 (EDT) From: Rick Macklem To: Yamagi Burmeister Message-ID: <974991789.2863688.1351194090522.JavaMail.root@erie.cs.uoguelph.ca> In-Reply-To: <20121025191745.7f6a7582d4401de467d3fe18@yamagi.org> Subject: Re: Can not read from ZFS exported over NFSv4 but write to it MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Originating-IP: [172.17.91.201] X-Mailer: Zimbra 6.0.10_GA_2692 (ZimbraWebClient - FF3.0 (Win)/6.0.10_GA_2692) Cc: freebsd-fs@freebsd.org X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 25 Oct 2012 19:41:32 -0000 Yamagi Burmeister wrote: > Hello :) > > On Thu, 25 Oct 2012 11:03:44 -0700 > YongHyeon PYUN wrote: > > > 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. > > Yeah I was the one who reported it. This is the same machine... > If disabled TSO and it seems to work. I've copied ~10GB from > the client to the server and the other way round without any > problem. > Just in case it might be related, the client will sosend() a segment just a little over 64Kbytes in size for writes. (I vaguely remember a recent thread related to TSO of segments a little over 64Kbytes. I don't know if that issue was specific to one type of network interface.) Good luck with it, rick > The dmesg (with verbose boot enabled) is: > > age0: mem > 0xfeac0000-0xfeafffff irq 18 at device 0.0 on pci2 age0: PCI device > revision : 0x00b0 age0: Chip id/revision : 0x9006 > age0: 1280 Tx FIFO, 2364 Rx FIFO > age0: MSIX count : 0 > age0: MSI count : 1 > age0: attempting to allocate 1 MSI vectors (1 supported) > msi: routing MSI IRQ 256 to local APIC 0 vector 48 > age0: using IRQ 256 for MSI > age0: Using 1 MSI messages. > age0: Read request size : 512 bytes. > age0: TLP payload size : 128 bytes. > age0: 4GB boundary crossed, switching to 32bit DMA addressing mode. > age0: PCI VPD capability not found! > miibus0: on age0 > atphy0: PHY 0 on miibus0 > atphy0: OUI 0x00c82e, model 0x0001, rev. 5 > atphy0: none, 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, > 1000baseT-FDX, 1000baseT-FDX-master, auto age0: bpf attached > age0: Ethernet address: 00:23:54:31:a0:12 > pci3: driver added > age0: link state changed to DOWN > age0: interrupt moderation is 100 us. > age0: link state changed to UP > > Ciao, > Yamagi > > -- > Homepage: www.yamagi.org > XMPP: yamagi@yamagi.org > GnuPG/GPG: 0xEFBCCBCB