From owner-freebsd-fs@freebsd.org Sun Aug 5 02:42:36 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 15F3D105F2DB for ; Sun, 5 Aug 2018 02:42:36 +0000 (UTC) (envelope-from info@createandlisting.tech) Received: from mail.createandlisting.tech (mail.createandlisting.tech [205.147.101.13]) by mx1.freebsd.org (Postfix) with ESMTP id 63CC3750A7 for ; Sun, 5 Aug 2018 02:42:35 +0000 (UTC) (envelope-from info@createandlisting.tech) Received: from [100.85.145.92] (unknown [27.97.8.58]) by mail.createandlisting.tech (Postfix) with ESMTPA id 9DAC94311E for ; Sun, 5 Aug 2018 08:12:24 +0530 (IST) Message-Id: <48QCPXYwpoIByJq4SO87ac5tdyqiY8941hH4rN9kiiTt@createandlisting.tech> Mime-Version: 1.0 From: Admin To: freebsd-fs@freebsd.org Subject: Re:Getting Hundreds of Clients Every Month from Your Website? Date: Sun, 5 Aug 2018 08:12:09 +0530 X-Bounce-Tracking-Info: Content-Type: text/plain; charset=iso-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.27 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 05 Aug 2018 02:42:36 -0000 Hello, Gentle Reminder! Awaiting Response Thanks, Regards, Melissa Bell, Online Business Advisor, ---------------------------------------------------------------------------= ----- From: info@createandlisting=2Etech [mailto:info@createandlisting=2Etech] Sent: Thursday, Aug 02, 2018 05:06 AM Subject: Getting Hundreds of Clients Every Month from Your Website? Hi I hope you are doing well=2E Do you want to see your Business website first page of the Google? Are you = looking for SEO service to rank your Website organically in Top 5 positions= of Google page 1? We provide guarantee to have more than 50% of the keywor= ds on Google page 1 within the projected Google page 1 time line, so let us= provide you the Google page 1 ranking=2E There will be no set up fee or any other hidden charge=2E So you just have = to pay your monthly SEO fee and no need to sign any contract=2E Please revert back to us if interested to know more information related to = price, past results & our proposal=2E I will look forward to your reply=2E Warm Regards, Melissa Bell SEO Consultant DISCLAIMER: This is an advertisement and a promotional email strictly on th= e guidelines of CAN-SPAM act of 2007=2E We have clearly mentioned the sourc= e mail-id of this` mail, also clearly mentioned the subject lines and they = are in no way misleading in any form=2E We have found your mail address thr= ough our own efforts on the web search and not through any illegal way= =2E If you find this mail unsolicited, please reply with" Unsubscribe" in t= he subject line and we will take care that you do not receive any further p= romotional mail From owner-freebsd-fs@freebsd.org Sun Aug 5 21:01:29 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 E7562105E19E for ; Sun, 5 Aug 2018 21:01:28 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 7D30B77D36 for ; Sun, 5 Aug 2018 21:01:28 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: by mailman.ysv.freebsd.org (Postfix) id 428C9105E19A; Sun, 5 Aug 2018 21:01:28 +0000 (UTC) Delivered-To: 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 20DF7105E199 for ; Sun, 5 Aug 2018 21:01:28 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id B5D5877D32 for ; Sun, 5 Aug 2018 21:01:27 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id 08B62A607 for ; Sun, 5 Aug 2018 21:01:27 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w75L1QGe068773 for ; Sun, 5 Aug 2018 21:01:26 GMT (envelope-from bugzilla-noreply@FreeBSD.org) Received: (from bugzilla@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w75L1Q1k068765 for fs@FreeBSD.org; Sun, 5 Aug 2018 21:01:26 GMT (envelope-from bugzilla-noreply@FreeBSD.org) Message-Id: <201808052101.w75L1Q1k068765@kenobi.freebsd.org> X-Authentication-Warning: kenobi.freebsd.org: bugzilla set sender to bugzilla-noreply@FreeBSD.org using -f From: bugzilla-noreply@FreeBSD.org To: fs@FreeBSD.org Subject: Problem reports for fs@FreeBSD.org that need special attention Date: Sun, 5 Aug 2018 21:01:26 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.27 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 05 Aug 2018 21:01:29 -0000 To view an individual PR, use: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id). The following is a listing of current problems submitted by FreeBSD users, which need special attention. These represent problem reports covering all versions including experimental development code and obsolete releases. Status | Bug Id | Description ------------+-----------+--------------------------------------------------- New | 203492 | mount_unionfs -o below causes panic New | 217062 | for file systems mounted with -o noexec, exec=off New | 221909 | [ZFS] Add a sysctl to toggle send_corrupt_data Open | 140068 | [smbfs] [patch] smbfs does not allow semicolon in Open | 144447 | [zfs] sharenfs fsunshare() & fsshare_main() non f Open | 211491 | System hangs after "Uptime" on reboot with ZFS 6 problems total for which you should take action. From owner-freebsd-fs@freebsd.org Fri Aug 10 08:31:15 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 0739C1061AD6 for ; Fri, 10 Aug 2018 08:31:15 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 97F0C7F59E for ; Fri, 10 Aug 2018 08:31:14 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 5CB121061AD5; Fri, 10 Aug 2018 08:31:14 +0000 (UTC) Delivered-To: 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 4B6251061AD4 for ; Fri, 10 Aug 2018 08:31:14 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id DF0707F599 for ; Fri, 10 Aug 2018 08:31:13 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id 49F2A22DEE for ; Fri, 10 Aug 2018 08:31:13 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w7A8VD8e026686 for ; Fri, 10 Aug 2018 08:31:13 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w7A8VDpl026685 for fs@FreeBSD.org; Fri, 10 Aug 2018 08:31:13 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: fs@FreeBSD.org Subject: [Bug 218101] [fuse] [request] support entry_timeout / attr_timeout Date: Fri, 10 Aug 2018 08:31:13 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: cem@freebsd.org X-Bugzilla-Status: Closed X-Bugzilla-Resolution: DUPLICATE X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: fs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: resolution bug_status Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Aug 2018 08:31:15 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D218101 Conrad Meyer changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |DUPLICATE Status|New |Closed --- Comment #2 from Conrad Meyer --- *** This bug has been marked as a duplicate of bug 230258 *** --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Fri Aug 10 08:38:18 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 B1D0F1061F3D for ; Fri, 10 Aug 2018 08:38:18 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 4E2147FA5A for ; Fri, 10 Aug 2018 08:38:18 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 0FF291061F38; Fri, 10 Aug 2018 08:38:18 +0000 (UTC) Delivered-To: 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 F2C261061F37 for ; Fri, 10 Aug 2018 08:38:17 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 940F37FA57 for ; Fri, 10 Aug 2018 08:38:17 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id C9B7822F41 for ; Fri, 10 Aug 2018 08:38:16 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w7A8cGMd038498 for ; Fri, 10 Aug 2018 08:38:16 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w7A8cGmk038497 for fs@FreeBSD.org; Fri, 10 Aug 2018 08:38:16 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: fs@FreeBSD.org Subject: [Bug 212318] sysutils/fusefs-libs: fails to unmount due to a uniq dev node Date: Fri, 10 Aug 2018 08:38:14 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Ports & Packages X-Bugzilla-Component: Individual Port(s) X-Bugzilla-Version: Latest X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: cem@freebsd.org X-Bugzilla-Status: Closed X-Bugzilla-Resolution: Overcome By Events X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: ports-bugs@FreeBSD.org X-Bugzilla-Flags: maintainer-feedback? X-Bugzilla-Changed-Fields: bug_status cc resolution Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Aug 2018 08:38:18 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D212318 Conrad Meyer changed: What |Removed |Added ---------------------------------------------------------------------------- Status|New |Closed CC| |cem@freebsd.org Resolution|--- |Overcome By Events --- Comment #14 from Conrad Meyer --- Either the compat22 routine was removed, or its use should be avoided, or if that absolutely fails maybe it can be patched not to be broken. Unclear if anything is still tripping over this broken path anymore. Sounds like encfs was fixed not to use it and fusefs-libs may have removed it too. --=20 You are receiving this mail because: You are on the CC list for the bug.= From owner-freebsd-fs@freebsd.org Fri Aug 10 14:28:22 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 E8932106C3E7 for ; Fri, 10 Aug 2018 14:28:21 +0000 (UTC) (envelope-from devgs@ukr.net) Received: from frv196.fwdcdn.com (frv196.fwdcdn.com [212.42.77.196]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.ukr.net", Issuer "Thawte RSA CA 2018" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 8A1378CF26 for ; Fri, 10 Aug 2018 14:28:21 +0000 (UTC) (envelope-from devgs@ukr.net) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=ukr.net; s=ffe; h=Content-Transfer-Encoding:Content-Type:MIME-Version:Message-Id:To: Subject:From:Date:Sender:Reply-To:Cc:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: In-Reply-To:References:List-Id:List-Help:List-Unsubscribe:List-Subscribe: List-Post:List-Owner:List-Archive; bh=a6hqf1hLPL3h9CE+o83d/D7Bpc63DOAfLps9cKgKLD0=; b=WHFed+HuDTjIgpQk/ialjcBTJw 0DGsaRI54pZiYXOWPUMMcioT8o5DUuoMG9K979FKdXyrU/T0LreGE7Bjuh7qgUVjBgmw7bt27U26E xeP20JxGGAwZxulB71qP42xW5Co2Yeu5jS52tJ3rHkBRWzcWdcY6oTT8cc3pW9kzbCiA=; Received: from [10.10.10.33] (helo=frv33.fwdcdn.com) by frv196.fwdcdn.com with smtp ID 1fo8Oh-000E2N-Hv for freebsd-fs@freebsd.org; Fri, 10 Aug 2018 17:28:11 +0300 Date: Fri, 10 Aug 2018 17:28:11 +0300 From: Paul Subject: Question regarding relevance of syncer(4) in the context of ZFS To: freebsd-fs@freebsd.org X-Mailer: mail.ukr.net 5.0 Message-Id: <1533910747.525373107.k9z2n7hj@frv33.fwdcdn.com> Received: from devgs@ukr.net by frv33.fwdcdn.com; Fri, 10 Aug 2018 17:28:11 +0300 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: binary X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Aug 2018 14:28:22 -0000 Hello team, If my understanding is correct then ZFS does not need to be pushed around and being told when to sync data to devices. It is perfectly capable of keeping data consistent and synchronized according to configured options. We even disable 'sync' option of file system that we use. But unfortunately we see a constant and periodical spikes of load on our servers that are directly related to wake-ups of 'syncer' kernel daemon. Is it safe to assume that 'syncer' is not necessary on configurations that only use ZFS, and no other file systems? And hence, is it safe to assume that setting all of 'kern.filedelay', 'kern.dirdelay' and 'kern.metadelay' to some large values will not compromise system's durability? Best regards, Paul From owner-freebsd-fs@freebsd.org Fri Aug 10 14:39:51 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 D027D106C8F6 for ; Fri, 10 Aug 2018 14:39:51 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from kib.kiev.ua (kib.kiev.ua [IPv6:2001:470:d5e7:1::1]) (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 35EC28D6B7 for ; Fri, 10 Aug 2018 14:39:51 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from tom.home (kib@localhost [127.0.0.1]) by kib.kiev.ua (8.15.2/8.15.2) with ESMTPS id w7AEdeCm041160 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Fri, 10 Aug 2018 17:39:43 +0300 (EEST) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.10.3 kib.kiev.ua w7AEdeCm041160 Received: (from kostik@localhost) by tom.home (8.15.2/8.15.2/Submit) id w7AEdeS5041159; Fri, 10 Aug 2018 17:39:40 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Fri, 10 Aug 2018 17:39:40 +0300 From: Konstantin Belousov To: Paul Cc: freebsd-fs@freebsd.org Subject: Re: Question regarding relevance of syncer(4) in the context of ZFS Message-ID: <20180810143940.GC2649@kib.kiev.ua> References: <1533910747.525373107.k9z2n7hj@frv33.fwdcdn.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1533910747.525373107.k9z2n7hj@frv33.fwdcdn.com> User-Agent: Mutt/1.10.1 (2018-07-13) X-Spam-Status: No, score=-2.0 required=5.0 tests=ALL_TRUSTED,BAYES_00, DKIM_ADSP_CUSTOM_MED,FREEMAIL_FROM,NML_ADSP_CUSTOM_MED autolearn=no autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on tom.home X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Aug 2018 14:39:52 -0000 On Fri, Aug 10, 2018 at 05:28:11PM +0300, Paul wrote: > Hello team, > > > If my understanding is correct then ZFS does not need to be pushed around and being told when to sync data to devices. > It is perfectly capable of keeping data consistent and synchronized according to configured options. > > We even disable 'sync' option of file system that we use. But unfortunately we see a constant and periodical spikes > of load on our servers that are directly related to wake-ups of 'syncer' kernel daemon. Is it safe to assume that > 'syncer' is not necessary on configurations that only use ZFS, and no other file systems? And hence, is it safe > to assume that setting all of 'kern.filedelay', 'kern.dirdelay' and 'kern.metadelay' to some large values will not > compromise system's durability? One of the job of the syncer is to convert dirty user-mapped pages into the filesystem-specific write requests. Without syncer touching the mount point, corresponding pages could linger forever, or at least until a memory pressure causes pagedaemon to clean them. From owner-freebsd-fs@freebsd.org Fri Aug 10 14:43:52 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 6BBD2106CD59 for ; Fri, 10 Aug 2018 14:43:52 +0000 (UTC) (envelope-from marck@rinet.ru) Received: from woozle.rinet.ru (woozle.rinet.ru [195.54.192.68]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id DEFD08DAC0; Fri, 10 Aug 2018 14:43:51 +0000 (UTC) (envelope-from marck@rinet.ru) Received: from localhost (localhost [127.0.0.1]) by woozle.rinet.ru (8.14.5/8.14.5) with ESMTP id w7AEgkjX049612; Fri, 10 Aug 2018 17:42:46 +0300 (MSK) (envelope-from marck@rinet.ru) Date: Fri, 10 Aug 2018 17:42:46 +0300 (MSK) From: Dmitry Morozovsky To: Gary Palmer cc: freebsd-fs@freebsd.org Subject: Re: ZFS backup Q: send/recv and mountpoint property In-Reply-To: <20180804220727.GA83288@in-addr.com> Message-ID: References: <20180804220727.GA83288@in-addr.com> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) X-NCC-RegID: ru.rinet X-OpenPGP-Key-ID: 6B691B03 MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (woozle.rinet.ru [0.0.0.0]); Fri, 10 Aug 2018 17:42:46 +0300 (MSK) X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Aug 2018 14:43:52 -0000 On Sat, 4 Aug 2018, Gary Palmer wrote: > On my backup server I have two pools, zfsroot and data. I think I set > things up, and then exported data so that it's not auto-imported at boot. > I then put this in /etc/rc.local > > zpool import -N -R /backups data > > It lets the pool import filesystems with paths like / or /home > without over-writing the paths on the local system. that would fit for "normal" case, but does not survive sudden reboot ;-) I'm switching to zxfer for now; not ideal, but fair and usable enough -- Sincerely, D.Marck [DM5020, MCK-RIPE, DM3-RIPN] [ FreeBSD committer: marck@FreeBSD.org ] ------------------------------------------------------------------------ *** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- marck@rinet.ru *** ------------------------------------------------------------------------ From owner-freebsd-fs@freebsd.org Fri Aug 10 14:48:06 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 EEDFE106CE9D for ; Fri, 10 Aug 2018 14:48:05 +0000 (UTC) (envelope-from gpalmer@freebsd.org) Received: from mail.in-addr.com (mail.in-addr.com [IPv6:2a01:4f8:191:61e8::2525:2525]) (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 8EC808DD28 for ; Fri, 10 Aug 2018 14:48:05 +0000 (UTC) (envelope-from gpalmer@freebsd.org) Received: from gjp by mail.in-addr.com with local (Exim 4.91 (FreeBSD)) (envelope-from ) id 1fo8hw-0002RW-82; Fri, 10 Aug 2018 15:48:04 +0100 Date: Fri, 10 Aug 2018 15:48:04 +0100 From: Gary Palmer To: Dmitry Morozovsky Cc: freebsd-fs@freebsd.org Subject: Re: ZFS backup Q: send/recv and mountpoint property Message-ID: <20180810144804.GA83321@in-addr.com> References: <20180804220727.GA83288@in-addr.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: gpalmer@freebsd.org X-SA-Exim-Scanned: No (on mail.in-addr.com); SAEximRunCond expanded to false X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Aug 2018 14:48:06 -0000 On Fri, Aug 10, 2018 at 05:42:46PM +0300, Dmitry Morozovsky wrote: > On Sat, 4 Aug 2018, Gary Palmer wrote: > > > On my backup server I have two pools, zfsroot and data. I think I set > > things up, and then exported data so that it's not auto-imported at boot. > > I then put this in /etc/rc.local > > > > zpool import -N -R /backups data > > > > It lets the pool import filesystems with paths like / or /home > > without over-writing the paths on the local system. > > that would fit for "normal" case, but does not survive sudden reboot ;-) > > I'm switching to zxfer for now; not ideal, but fair and usable enough Hi, I haven't tested reboot during sync, but I'm not sure why a sudden reboot would cause issues - the -R should move mounts outside critical areas. Could you elaborate please? Thanks, Gary From owner-freebsd-fs@freebsd.org Fri Aug 10 14:52:07 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 1738B106D18E for ; Fri, 10 Aug 2018 14:52:07 +0000 (UTC) (envelope-from marck@rinet.ru) Received: from woozle.rinet.ru (woozle.rinet.ru [195.54.192.68]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 8829F8E203; Fri, 10 Aug 2018 14:52:06 +0000 (UTC) (envelope-from marck@rinet.ru) Received: from localhost (localhost [127.0.0.1]) by woozle.rinet.ru (8.14.5/8.14.5) with ESMTP id w7AEq3JJ049717; Fri, 10 Aug 2018 17:52:03 +0300 (MSK) (envelope-from marck@rinet.ru) Date: Fri, 10 Aug 2018 17:52:03 +0300 (MSK) From: Dmitry Morozovsky To: Gary Palmer cc: freebsd-fs@freebsd.org Subject: Re: ZFS backup Q: send/recv and mountpoint property In-Reply-To: <20180810144804.GA83321@in-addr.com> Message-ID: References: <20180804220727.GA83288@in-addr.com> <20180810144804.GA83321@in-addr.com> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) X-NCC-RegID: ru.rinet X-OpenPGP-Key-ID: 6B691B03 MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (woozle.rinet.ru [0.0.0.0]); Fri, 10 Aug 2018 17:52:03 +0300 (MSK) X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Aug 2018 14:52:07 -0000 On Fri, 10 Aug 2018, Gary Palmer wrote: > > > On my backup server I have two pools, zfsroot and data. I think I set > > > things up, and then exported data so that it's not auto-imported at boot. > > > I then put this in /etc/rc.local > > > > > > zpool import -N -R /backups data > > > > > > It lets the pool import filesystems with paths like / or /home > > > without over-writing the paths on the local system. > > > > that would fit for "normal" case, but does not survive sudden reboot ;-) > > > > I'm switching to zxfer for now; not ideal, but fair and usable enough > > Hi, > > I haven't tested reboot during sync, but I'm not sure why a sudden > reboot would cause issues - the -R should move mounts outside > critical areas. Could you elaborate please? yes, that would be exactly the case I'm referring: reboot when your data pool is *not* exported -- Sincerely, D.Marck [DM5020, MCK-RIPE, DM3-RIPN] [ FreeBSD committer: marck@FreeBSD.org ] ------------------------------------------------------------------------ *** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- marck@rinet.ru *** ------------------------------------------------------------------------ From owner-freebsd-fs@freebsd.org Fri Aug 10 14:54:14 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 1D715106D2AF for ; Fri, 10 Aug 2018 14:54:14 +0000 (UTC) (envelope-from devgs@ukr.net) Received: from frv199.fwdcdn.com (frv199.fwdcdn.com [212.42.77.199]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.ukr.net", Issuer "Thawte RSA CA 2018" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id AF3558E496 for ; Fri, 10 Aug 2018 14:54:13 +0000 (UTC) (envelope-from devgs@ukr.net) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=ukr.net; s=ffe; h=Content-Transfer-Encoding:Content-Type:MIME-Version:References: In-Reply-To:Message-Id:Cc:To:Subject:From:Date:Sender:Reply-To:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:List-Id:List-Help:List-Unsubscribe:List-Subscribe: List-Post:List-Owner:List-Archive; bh=L7hqS2GHlyGm4BXR7rjnF03dtxM5bEa2LXAsKb1uImE=; b=UKp07mgJ1319InaKmxVr/RHeqx VCeb/9+OQW0M9qACXYXHfyJiSmoI3QhcEYGK+oVaeRH2iy9/kQQCDZIOKIDLo78FQzTYQMk0ToZOL ThdyhFFCRSWBiXskthvUMkWcAPiv3JCfT+1NCtnh1k05PRf8ZNFDLIfQeTl16+r2zrXY=; Received: from [10.10.10.33] (helo=frv33.fwdcdn.com) by frv199.fwdcdn.com with smtp ID 1fo8nk-000JLg-4x for freebsd-fs@freebsd.org; Fri, 10 Aug 2018 17:54:04 +0300 Date: Fri, 10 Aug 2018 17:54:03 +0300 From: Paul Subject: Re[2]: Question regarding relevance of syncer(4) in the context of ZFS To: Konstantin Belousov Cc: freebsd-fs@freebsd.org X-Mailer: mail.ukr.net 5.0 Message-Id: <1533912779.505892598.lhqtiahk@frv33.fwdcdn.com> In-Reply-To: <20180810143940.GC2649@kib.kiev.ua> References: <1533910747.525373107.k9z2n7hj@frv33.fwdcdn.com> <20180810143940.GC2649@kib.kiev.ua> X-Reply-Action: reply Received: from devgs@ukr.net by frv33.fwdcdn.com; Fri, 10 Aug 2018 17:54:04 +0300 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: binary X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Aug 2018 14:54:14 -0000 10 August 2018, 17:39:52, by "Konstantin Belousov" : > On Fri, Aug 10, 2018 at 05:28:11PM +0300, Paul wrote: > > Hello team, > > > > > > If my understanding is correct then ZFS does not need to be pushed around and being told when to sync data to devices. > > It is perfectly capable of keeping data consistent and synchronized according to configured options. > > > > We even disable 'sync' option of file system that we use. But unfortunately we see a constant and periodical spikes > > of load on our servers that are directly related to wake-ups of 'syncer' kernel daemon. Is it safe to assume that > > 'syncer' is not necessary on configurations that only use ZFS, and no other file systems? And hence, is it safe > > to assume that setting all of 'kern.filedelay', 'kern.dirdelay' and 'kern.metadelay' to some large values will not > > compromise system's durability? > > One of the job of the syncer is to convert dirty user-mapped pages into > the filesystem-specific write requests. Without syncer touching the mount > point, corresponding pages could linger forever, or at least until a memory > pressure causes pagedaemon to clean them. Thanks a lot for clarification! I didn't think about dirty user-mapped pages... Best regards, Paul From owner-freebsd-fs@freebsd.org Fri Aug 10 14:55:22 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 6FA8D106D32B for ; Fri, 10 Aug 2018 14:55:22 +0000 (UTC) (envelope-from gpalmer@freebsd.org) Received: from mail.in-addr.com (mail.in-addr.com [IPv6:2a01:4f8:191:61e8::2525:2525]) (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 091328E5EB for ; Fri, 10 Aug 2018 14:55:22 +0000 (UTC) (envelope-from gpalmer@freebsd.org) Received: from gjp by mail.in-addr.com with local (Exim 4.91 (FreeBSD)) (envelope-from ) id 1fo8oz-0002T9-2n; Fri, 10 Aug 2018 15:55:21 +0100 Date: Fri, 10 Aug 2018 15:55:21 +0100 From: Gary Palmer To: Dmitry Morozovsky Cc: freebsd-fs@freebsd.org Subject: Re: ZFS backup Q: send/recv and mountpoint property Message-ID: <20180810145521.GB83321@in-addr.com> References: <20180804220727.GA83288@in-addr.com> <20180810144804.GA83321@in-addr.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: gpalmer@freebsd.org X-SA-Exim-Scanned: No (on mail.in-addr.com); SAEximRunCond expanded to false X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Aug 2018 14:55:22 -0000 On Fri, Aug 10, 2018 at 05:52:03PM +0300, Dmitry Morozovsky wrote: > On Fri, 10 Aug 2018, Gary Palmer wrote: > > > > > On my backup server I have two pools, zfsroot and data. I think I set > > > > things up, and then exported data so that it's not auto-imported at boot. > > > > I then put this in /etc/rc.local > > > > > > > > zpool import -N -R /backups data > > > > > > > > It lets the pool import filesystems with paths like / or /home > > > > without over-writing the paths on the local system. > > > > > > that would fit for "normal" case, but does not survive sudden reboot ;-) > > > > > > I'm switching to zxfer for now; not ideal, but fair and usable enough > > > > Hi, > > > > I haven't tested reboot during sync, but I'm not sure why a sudden > > reboot would cause issues - the -R should move mounts outside > > critical areas. Could you elaborate please? > > yes, that would be exactly the case I'm referring: reboot when your data pool > is *not* exported Hi Dmitry, I don't think that's a problem. I don't export the pool before rebooting, I just shut down the box and boot it the next time I need to do a backup The -R flag prevents the pool from being written to the cache file which should stop import on boot. Note that I'm running FreebSD 10.4-p currently. Need to upgrade to 11.2 and see if that still works. Regards, Gary From owner-freebsd-fs@freebsd.org Fri Aug 10 22:49:46 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 5BCAE107756A for ; Fri, 10 Aug 2018 22:49:46 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id EAC8B7EA50 for ; Fri, 10 Aug 2018 22:49:45 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id B03BF1077564; Fri, 10 Aug 2018 22:49:45 +0000 (UTC) Delivered-To: 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 9F39A1077563 for ; Fri, 10 Aug 2018 22:49:45 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 3E1927EA46 for ; Fri, 10 Aug 2018 22:49:45 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id 8D0E1A61D for ; Fri, 10 Aug 2018 22:49:44 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w7AMni97031707 for ; Fri, 10 Aug 2018 22:49:44 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w7AMni4b031705 for fs@FreeBSD.org; Fri, 10 Aug 2018 22:49:44 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: fs@FreeBSD.org Subject: [Bug 230260] [FUSE] [PERFORMANCE]: Performance issue (I/O block size) Date: Fri, 10 Aug 2018 22:49:43 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 11.1-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: linimon@FreeBSD.org X-Bugzilla-Status: In Progress X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: fs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: assigned_to Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Aug 2018 22:49:46 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D230260 Mark Linimon changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|bugs@FreeBSD.org |fs@FreeBSD.org --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Sat Aug 11 17:17:51 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 16E1810746DC for ; Sat, 11 Aug 2018 17:17:51 +0000 (UTC) (envelope-from gpalmer@freebsd.org) Received: from mail.in-addr.com (mail.in-addr.com [IPv6:2a01:4f8:191:61e8::2525:2525]) (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 A0DAF89F97 for ; Sat, 11 Aug 2018 17:17:50 +0000 (UTC) (envelope-from gpalmer@freebsd.org) Received: from gjp by mail.in-addr.com with local (Exim 4.91 (FreeBSD)) (envelope-from ) id 1foXWO-0008fG-RI; Sat, 11 Aug 2018 18:17:48 +0100 Date: Sat, 11 Aug 2018 18:17:48 +0100 From: Gary Palmer To: Dmitry Morozovsky Cc: freebsd-fs@freebsd.org Subject: Re: ZFS backup Q: send/recv and mountpoint property Message-ID: <20180811171748.GC83321@in-addr.com> References: <20180804220727.GA83288@in-addr.com> <20180810144804.GA83321@in-addr.com> <20180810145521.GB83321@in-addr.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180810145521.GB83321@in-addr.com> X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: gpalmer@freebsd.org X-SA-Exim-Scanned: No (on mail.in-addr.com); SAEximRunCond expanded to false X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 11 Aug 2018 17:17:51 -0000 On Fri, Aug 10, 2018 at 03:55:21PM +0100, Gary Palmer wrote: > On Fri, Aug 10, 2018 at 05:52:03PM +0300, Dmitry Morozovsky wrote: > > On Fri, 10 Aug 2018, Gary Palmer wrote: > > > > > > > On my backup server I have two pools, zfsroot and data. I think I set > > > > > things up, and then exported data so that it's not auto-imported at boot. > > > > > I then put this in /etc/rc.local > > > > > > > > > > zpool import -N -R /backups data > > > > > > > > > > It lets the pool import filesystems with paths like / or /home > > > > > without over-writing the paths on the local system. > > > > > > > > that would fit for "normal" case, but does not survive sudden reboot ;-) > > > > > > > > I'm switching to zxfer for now; not ideal, but fair and usable enough > > > > > > Hi, > > > > > > I haven't tested reboot during sync, but I'm not sure why a sudden > > > reboot would cause issues - the -R should move mounts outside > > > critical areas. Could you elaborate please? > > > > yes, that would be exactly the case I'm referring: reboot when your data pool > > is *not* exported > > Hi Dmitry, > > I don't think that's a problem. I don't export the pool before rebooting, > I just shut down the box and boot it the next time I need to do a backup > The -R flag prevents the pool from being written to the cache file which > should stop import on boot. Note that I'm running FreebSD 10.4-p > currently. Need to upgrade to 11.2 and see if that still works. Just upgraded to 11.2 and no obvious issues so far with the above scheme Regards, Gary