From owner-freebsd-fs@freebsd.org Wed Apr 4 20:15:00 2018 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 20533F72F0E for ; Wed, 4 Apr 2018 20:15:00 +0000 (UTC) (envelope-from mike@sentex.net) Received: from smarthost2.sentex.ca (smarthost2.sentex.ca [IPv6:2607:f3e0:80:80::2]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client CN "smarthost.sentex.ca", Issuer "smarthost.sentex.ca" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 9CFD571670 for ; Wed, 4 Apr 2018 20:14:59 +0000 (UTC) (envelope-from mike@sentex.net) Received: from lava.sentex.ca (lava.sentex.ca [IPv6:2607:f3e0:0:5::11]) by smarthost2.sentex.ca (8.15.2/8.15.2) with ESMTPS id w34KEwKH016160 (version=TLSv1 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for ; Wed, 4 Apr 2018 16:14:59 -0400 (EDT) (envelope-from mike@sentex.net) Received: from [192.168.43.26] (saphire3.sentex.ca [192.168.43.26]) by lava.sentex.ca (8.15.2/8.15.2) with ESMTP id w34KEuap017258; Wed, 4 Apr 2018 16:14:56 -0400 (EDT) (envelope-from mike@sentex.net) Subject: Re: Linux NFS client and FreeBSD server strangeness To: Kaya Saman , =?UTF-8?Q?Karli_Sj=c3=b6berg?= , freebsd-fs@freebsd.org, Guido Falsi References: <369fab06-6213-ba87-cc66-c9829e8a76a0@sentex.net> <2019ee5a-5b2b-853d-98c5-a365940d93b5@madpilot.net> <4da08f8b-2c28-cf18-77d2-6b498004d435@gmail.com> From: Mike Tancsa Organization: Sentex Communications Message-ID: <2937ffcc-6b47-91af-8745-2117006660db@sentex.net> Date: Wed, 4 Apr 2018 16:14:57 -0400 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: <4da08f8b-2c28-cf18-77d2-6b498004d435@gmail.com> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 8bit X-Scanned-By: MIMEDefang 2.78 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Apr 2018 20:15:00 -0000 On 4/4/2018 4:04 PM, Kaya Saman wrote: > I think I posted a similar topic ages ago but got no response. It would > be interesting to see the cause for this. I have a hunch it could be > something to do with the nfs implementation of Linux but it is just pure > conjecture on my side. I know what you mean about the zfs / zil lockups. It makes a HUGE difference performance wise if you run with sync disabled on writes for the zfs dataset. Not sure I want to do that. I am going to try later with ZIL on some NVE devices and see I can have the best of both worlds. I have individual zfs data sets for each server to write their backups to. I might be able to live with the risk of running with sync disabled to receive backup files with. I think I may have found the setting on the LINUX client. If I mount with the options -o tcp,intr,noatime,sync,vers=3 ie sync I get the "smooth" traffic patterns. Its actually a bit slower than the with the default async which I guess is able to burst up higher. I am not sure how dangerous running async writes are on an nfs client. But for now, this mystery seems to be a bit better explained to me! ---Mike -- ------------------- Mike Tancsa, tel +1 519 651 3400 x203 Sentex Communications, mike@sentex.net Providing Internet services since 1994 www.sentex.net Cambridge, Ontario Canada