From owner-freebsd-fs@freebsd.org Wed Apr 4 20:23:41 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 BDDC7F73A74 for ; Wed, 4 Apr 2018 20:23:41 +0000 (UTC) (envelope-from kayasaman@gmail.com) Received: from mail-io0-x22d.google.com (mail-io0-x22d.google.com [IPv6:2607:f8b0:4001:c06::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4F85171F0A for ; Wed, 4 Apr 2018 20:23:41 +0000 (UTC) (envelope-from kayasaman@gmail.com) Received: by mail-io0-x22d.google.com with SMTP id q80so27847852ioi.13 for ; Wed, 04 Apr 2018 13:23:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=QJUiGhmSPQlD6Ra1xzFesbGETYjVZktoAEovtYlATzo=; b=f6vTOf9c04uo1xeITg2pKRuKHkPir2woFzBhSqL0qmmM4rAllJLrTow4Alli7Px2iD x77eKG4H/v6i/dxtD/qmu8D9djedZFwFxRVjIhR39DxFDUJ/qqXTNY2EiC+SNetJzN9j RsjM/xYWG1hEf/DPANb+ThFrfFuOMeWwKleV/lKspmopqbUTi4Uvins8XWclh5EC0uWH kCH4JemjKNwVxG2qNT7NAwG1gb9nICUtp+3EZnkI37x9sZO/3QT76DbvUz3zGWm6ugC4 leOBBZbXMXQwBNQyxMEbug1KzLjRugeNKuznCJC+HD9Kw+zQziCaqxW2tRGyl1YWocQ0 f+Zg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=QJUiGhmSPQlD6Ra1xzFesbGETYjVZktoAEovtYlATzo=; b=SP77ocySu+NwtczSzFevKhjKdEEFs/BAveePMy/jC052ssAlX4GjvDKntfSwBrwpyy /KjANVGBxW64rIprCTVBwXXoQ4I1h6+q3f4PWcmW8WKWmI0zgN/Ma54I45/yizfCG7QK Izf2R2JIofFzF0ywqj3WKrA6+3C6xRh6JWxjJaMnW0CHVYZo65LL0biS17cjnc5dnZrG gb2YQYVWIxPylFXByzUf4w6X2X7WY7W/Jxb7+wedtX6UBH6pYtuyQNztmlJLcVM3nT0p qzKQOIiwzsjwVSI9qIok8qrrmYOwfADANzYeJ5OHbahUXu5NQN3JsQKUGaDknDdPmVhx xmmw== X-Gm-Message-State: AElRT7EkmUA2cfmEklBt85Pn1tGgChW6YNNyT9tfw3QwOlmuihjNrNGb WTZbd+L9N8H978OPW+9X7FpHXR7vSR+USXB76zM= X-Google-Smtp-Source: AIpwx49CDjFiRkQi5LfCdI5vavs+fD3lvnUvZGewV6x606bolEtYlr93cf5KhWywZtG8tEpxOYW+XprOGX5wLg4W0Hg= X-Received: by 10.107.178.70 with SMTP id b67mr18231651iof.186.1522873420818; Wed, 04 Apr 2018 13:23:40 -0700 (PDT) MIME-Version: 1.0 Received: by 10.192.148.22 with HTTP; Wed, 4 Apr 2018 13:23:40 -0700 (PDT) In-Reply-To: <2937ffcc-6b47-91af-8745-2117006660db@sentex.net> 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: Kaya Saman Date: Wed, 4 Apr 2018 21:23:40 +0100 Message-ID: Subject: Re: Linux NFS client and FreeBSD server strangeness To: Mike Tancsa Cc: =?UTF-8?Q?Karli_Sj=C3=B6berg?= , FreeBSD Filesystems , Guido Falsi Content-Type: text/plain; charset="UTF-8" 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:23:42 -0000 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 though I could get rid of the tcp as that's also a default. The rsize and wsize options are for running Jumbo Frames ie. larger MTU then 1500; in my case 9000 for 1Gbps links. At least for Arch Linux the guide does explain quite a bit, though the 'man' page does too ;-) https://wiki.archlinux.org/index.php/NFS On Wed, Apr 4, 2018 at 9:14 PM, Mike Tancsa wrote: > 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