From owner-freebsd-fs@freebsd.org Thu Apr 5 15:49:10 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 89635F8EED4 for ; Thu, 5 Apr 2018 15:49:10 +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 0E64682DFF for ; Thu, 5 Apr 2018 15:49:09 +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 w35Fn9VZ083570 (version=TLSv1 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for ; Thu, 5 Apr 2018 11:49:09 -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 w35Fn792021206; Thu, 5 Apr 2018 11:49:07 -0400 (EDT) (envelope-from mike@sentex.net) Subject: Re: Linux NFS client and FreeBSD server strangeness To: Kaya Saman Cc: FreeBSD Filesystems References: <369fab06-6213-ba87-cc66-c9829e8a76a0@sentex.net> <2019ee5a-5b2b-853d-98c5-a365940d93b5@madpilot.net> <4da08f8b-2c28-cf18-77d2-6b498004d435@gmail.com> <2937ffcc-6b47-91af-8745-2117006660db@sentex.net> From: Mike Tancsa Organization: Sentex Communications Message-ID: <5aee728a-bf51-9f8c-3c75-4e4768cc84af@sentex.net> Date: Thu, 5 Apr 2018 11:49:08 -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: 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: Thu, 05 Apr 2018 15:49:10 -0000 On 4/4/2018 4:23 PM, Kaya Saman wrote: > If I recall correctly the "sync" option is default. Though it might be > different depending on the Linux distro in use? > > I use this: vers=3,defaults,auto,tcp,rsize=8192,wsize=8192 Thanks. For ubuntu 16, it looks like the default is async. It would be nice if all of these defaults were exposed to view. Also the rw buffers are higher than the above at 131072. I too am using 9000 for the MTU. After doing mount.nfs -o intr,noatime,vers=3 -v the options that come up are mount.nfs: prog 100003, trying vers=3, prot=6 mount.nfs: trying 192.168.242.254 prog 100003 vers 3 prot TCP port 2049 mount.nfs: prog 100005, trying vers=3, prot=17 mount.nfs: trying 192.168.242.254 prog 100005 vers 3 prot UDP port 944 kind of odd in that they dont display all of them mount | grep nfs 192.168.xx.yy:/zbackup1/virtbox4b/backup on /backup type nfs (rw,noatime,vers=3,rsize=131072,wsize=131072,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=192.168.xx.yy,mountvers=3,mountport=944,mountproto=udp,local_lock=none,addr=192.168.xx.yy) The sync/async The sync mount option The NFS client treats the sync mount option differently than some other file systems (refer to mount(8) for a description of the generic sync and async mount options). If neither sync nor async is specified (or if the async option is specified), the NFS client delays sending application writes to the server until any of these events occur: Memory pressure forces reclamation of system memory resources. An application flushes file data explicitly with sync(2), msync(2), or fsync(3). An application closes a file with close(2). The file is locked/unlocked via fcntl(2). ---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