From owner-freebsd-fs@freebsd.org Mon May 21 07:05:33 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 E754DEE5AD0 for ; Mon, 21 May 2018 07:05:32 +0000 (UTC) (envelope-from borjam@sarenet.es) Received: from cu01176b.smtpx.saremail.com (cu01176b.smtpx.saremail.com [195.16.151.151]) (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 84BFC70414 for ; Mon, 21 May 2018 07:05:32 +0000 (UTC) (envelope-from borjam@sarenet.es) Received: from [172.16.8.141] (unknown [192.148.167.11]) by proxypop01.sare.net (Postfix) with ESMTPA id 0EC9C9DC77F; Mon, 21 May 2018 08:58:47 +0200 (CEST) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 11.3 \(3445.6.18\)) Subject: Re: Can one remove a specific file from all snapshots? From: Borja Marcos In-Reply-To: <4b59e335-9140-5d29-4177-00bc33d65980@sorbs.net> Date: Mon, 21 May 2018 08:58:47 +0200 Cc: Alex Aminoff , freebsd-fs@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: <4EA8DFA5-734E-4BBA-A267-F6C76FE44765@sarenet.es> References: <38792b3b-04db-0c7f-c9a4-3f55b908a427@nber.org> <4b59e335-9140-5d29-4177-00bc33d65980@sorbs.net> To: Michelle Sullivan X-Mailer: Apple Mail (2.3445.6.18) X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 May 2018 07:05:33 -0000 > On 21 May 2018, at 04:36, Michelle Sullivan = wrote: >=20 > Of course if it's making use of an appliance/existing hardware that = uses ZFS by default/design you could always do something smart like = creating a zvol for said data and formatting it with an FS type that = doesn't do copy-on-write and doesn't have that type of snapshops etc... = perhaps with a software mirror zvol if it's redundancy you're after... = perhaps as a 'this is your secure/non snapshotted' drive export tag = etc... 100's of solutions depending on the client needs. Beware, the zvol will still do copy on write, you can do snapshots of a = zvol, etc :)=20 The key in most cases is to exploit the flexibility of ZFS better. You = can do as Michelle says, or just increase your dataset granularity.=20 Do you have data that needs more snapshots with a longer retention = period? That must go to a separate dataset. Conversely, data that needs a shorter retention period? Separate = datasets. Data that might require a rollback without affecting others? (Example, a = user=E2=80=99s home directory in a file server in case of a ransomware = incident) Separate dataset And so on. I guess some still treat datasets like disk partition in the = old times, with a limited number per disk.=20 Cheers, Borja.