From owner-freebsd-fs@freebsd.org Tue Apr 24 15:47:02 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 7F981FA9C0D for ; Tue, 24 Apr 2018 15:47:02 +0000 (UTC) (envelope-from karli@inparadise.se) Received: from mail.inparadise.se (h-112-105.A444.priv.bahnhof.se [158.174.112.105]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id D60C3857F8 for ; Tue, 24 Apr 2018 15:47:01 +0000 (UTC) (envelope-from karli@inparadise.se) Received: from localhost (localhost [127.0.0.1]) by mail.inparadise.se (Postfix) with ESMTP id 36069431FA; Tue, 24 Apr 2018 17:47:00 +0200 (CEST) Received: from mail.inparadise.se ([127.0.0.1]) by localhost (mail.inparadise.se [127.0.0.1]) (amavisd-new, port 10032) with ESMTP id L47suSj99TAW; Tue, 24 Apr 2018 17:46:58 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by mail.inparadise.se (Postfix) with ESMTP id 3EC16431FF; Tue, 24 Apr 2018 17:46:58 +0200 (CEST) DKIM-Filter: OpenDKIM Filter v2.10.3 mail.inparadise.se 3EC16431FF X-Virus-Scanned: amavisd-new at inparadise.se Received: from mail.inparadise.se ([127.0.0.1]) by localhost (mail.inparadise.se [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id tFTECs-RLnH8; Tue, 24 Apr 2018 17:46:58 +0200 (CEST) Received: from nexus6p.inparadise.se (nexus6p.inparadise.se [172.16.1.122]) by mail.inparadise.se (Postfix) with ESMTPSA id 1A1E6431FA; Tue, 24 Apr 2018 17:46:58 +0200 (CEST) Date: Tue, 24 Apr 2018 17:46:57 +0200 User-Agent: K-9 Mail for Android In-Reply-To: References: , <1524471526.9560.51.camel@inparadise.se> , <1524550472.1130.10.camel@inparadise.se> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Subject: Re: pNFS server completed To: Rick Macklem , "freebsd-fs@freebsd.org" From: =?ISO-8859-1?Q?Karli_Sj=F6berg?= Message-ID: <7A931945-0783-48EF-8743-B7F7261E9343@inparadise.se> 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: Tue, 24 Apr 2018 15:47:02 -0000 Rick Macklem skrev: (24 april 2018 14:36:24 CEST) >Karli Sj=C3=B6berg wrote: >[stuff snipped] >>OK, I think I understand, thank you for the explanation! >> >>So you could say that this enhancement is more about the performance >>benifit of scaling out, rather than resiliance/tolerance? >Yes, although without the DS mirroring (which is optional and doesn't >have to >be done), you would go from one SPOF to N SPOFs=2E > >To be honest, this pNFS service will not be useful for many=2E Only >people who >need to scale out beyond the limits of one NFS server and find it more >convenient >that creating a second NFS server=2E > >Improving resiliance/tolerance for an NFS server is a separate topic >(and would >apply to the MDS of this pNFS service as well)=2E >I don't have any expertise w=2Er=2Et=2E this, but something like HA (whic= h I >just learned >about from the email thread) might be appropriate=2E If you can build a >storage >subsystem with internal redundancy (raid at the drive level) and then >have >two servers "attached" to the storage subsystem so that it can fail >over >from the 1st to 2nd server, that would be a good start=2E >With that, you would just need to have something that would tell the >nfs >servers to start/stop when the HA failover happens, I think? >This is a really interesting problem, but not one for me=2E Of course if >someone >gets to the point where it needs an nfsd tweak to make the fail over >work, I >could help with that=2E > >Thanks for your interest, rick And thank you for working on this! /K --=20 Skickat fr=C3=A5n min Android-enhet med K-9 Mail=2E Urs=C3=A4kta min f=C3= =A5ordighet=2E