From owner-freebsd-stable@freebsd.org Fri May 3 13:30:13 2019 Return-Path: <owner-freebsd-stable@freebsd.org> Delivered-To: freebsd-stable@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 1A237159072D for <freebsd-stable@mailman.ysv.freebsd.org>; Fri, 3 May 2019 13:30:13 +0000 (UTC) (envelope-from petefrench@ingresso.co.uk) Received: from constantine.ingresso.co.uk (constantine.ingresso.co.uk [31.24.6.74]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 0CE50715CE for <freebsd-stable@freebsd.org>; Fri, 3 May 2019 13:30:11 +0000 (UTC) (envelope-from petefrench@ingresso.co.uk) Received: from [82.47.240.30] (helo=foula.local) by constantine.ingresso.co.uk with esmtpsa (TLSv1.3:TLS_AES_128_GCM_SHA256:128) (Exim 4.92 (FreeBSD)) (envelope-from <petefrench@ingresso.co.uk>) id 1hMYGQ-00067h-1o for freebsd-stable@freebsd.org; Fri, 03 May 2019 13:30:10 +0000 Subject: Re: ZFS... To: freebsd-stable@freebsd.org References: <3d0f6436-f3d7-6fee-ed81-a24d44223f2f@netfence.it> <17B373DA-4AFC-4D25-B776-0D0DED98B320@sorbs.net> <70fac2fe3f23f85dd442d93ffea368e1@ultra-secure.de> <70C87D93-D1F9-458E-9723-19F9777E6F12@sorbs.net> <CAGMYy3tYqvrKgk2c==WTwrH03uTN1xQifPRNxXccMsRE1spaRA@mail.gmail.com> <fe6880bc-d40a-2377-6bea-28bfd8229e9f@sorbs.net> <58DA896C-5312-47BC-8887-7680941A9AF2@sarenet.es> <cde21bb4-d741-3300-077f-745cfc343aa9@ingresso.co.uk> <C5403ADD-86C1-4184-BDA6-DA8C7426458E@sarenet.es> <62803130-9C40-4A98-B5A4-A2DFAC0FAD65@sorbs.net> <20190503125118.GA11226@neutralgood.org> <2A7B5457-371A-4014-8C1E-972BA2FD10DF@sorbs.net> From: Pete French <petefrench@ingresso.co.uk> Message-ID: <7b9ce013-e50c-7cfc-f5c1-c829855f8ee2@ingresso.co.uk> Date: Fri, 3 May 2019 14:30:09 +0100 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:67.0) Gecko/20100101 Thunderbird/67.0 MIME-Version: 1.0 In-Reply-To: <2A7B5457-371A-4014-8C1E-972BA2FD10DF@sorbs.net> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit X-Rspamd-Queue-Id: 0CE50715CE X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dmarc=pass (policy=none) header.from=ingresso.co.uk; spf=pass (mx1.freebsd.org: domain of petefrench@ingresso.co.uk designates 31.24.6.74 as permitted sender) smtp.mailfrom=petefrench@ingresso.co.uk X-Spamd-Result: default: False [-3.18 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; RCVD_COUNT_TWO(0.00)[2]; NEURAL_HAM_MEDIUM(-0.97)[-0.970,0]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:31.24.6.74]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MIME_GOOD(-0.10)[text/plain]; TO_DN_NONE(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; RCPT_COUNT_ONE(0.00)[1]; IP_SCORE(-0.36)[asn: 16082(-1.72), country: GB(-0.09)]; MX_GOOD(-0.01)[cached: us-smtp-inbound-1.mimecast.com]; DMARC_POLICY_ALLOW(-0.50)[ingresso.co.uk,none]; SUBJ_ALL_CAPS(0.45)[6]; NEURAL_HAM_SHORT(-0.49)[-0.486,0]; RECEIVED_SPAMHAUS_PBL(0.00)[30.240.47.82.zen.spamhaus.org : 127.0.0.11]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:16082, ipnet:31.24.0.0/21, country:GB]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_TLS_ALL(0.00)[]; FROM_EQ_ENVFROM(0.00)[] X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org> List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-stable>, <mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable/> List-Post: <mailto:freebsd-stable@freebsd.org> List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help> List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-stable>, <mailto:freebsd-stable-request@freebsd.org?subject=subscribe> X-List-Received-Date: Fri, 03 May 2019 13:30:13 -0000 On 03/05/2019 14:07, Michelle Sullivan wrote: > I don’t think it will do that in write through.. it will everytime in write back. Yes, it really shouldnt do that. My server is so old that the battery on the RAID has failed, which definitely makes it go into write though mode. However not an ideal solution ;-)