Date: Mon, 23 Aug 2021 20:54:41 +0300 From: Lev Serebryakov <lev@FreeBSD.org> To: Alan Somers <asomers@freebsd.org>, George Michaelson <ggm@algebras.org> Cc: Ben RUBSON <ben.rubson@gmx.com>, freebsd-fs <freebsd-fs@freebsd.org> Subject: Re: ZFS on high-latency devices Message-ID: <90ec9734-c4d8-b164-aec1-f95fcfda913b@FreeBSD.org> In-Reply-To: <CAOtMX2hRuh_9ZOOoQufNT2QG3Ui0S3rJq%2BL-ox2kxsq1oJMSMA@mail.gmail.com> References: <YR4mY%2Bb6o7fBJqEN@server.rulingia.com> <023225AD-2A97-47C5-9FE4-3ABF1BFD66F1@gmx.com> <CAKr6gn0r8xG9HNGOFh1A_usU4tPAYezeZv1chOG_bBMqy_HtXw@mail.gmail.com> <CAOtMX2hRuh_9ZOOoQufNT2QG3Ui0S3rJq%2BL-ox2kxsq1oJMSMA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 23.08.2021 2:48, Alan Somers wrote: > mbuffer is not going to help the OP. He's trying to create a pool on top > of a networked block device. And if I understand correctly, he's > connecting over a WAN, not a LAN. ZFS will never achieve decent > performance in such a setup. It's designed as a local file system, and > assumes it can quickly read metadata off of the disks at any time. The > OP's best option is to go with "a": encrypt each dataset and send them with > "zfs send --raw". I don't know why he thinks that it would be "very > difficult". It's quite easy, if he doesn't care about old snapshots. Just: > > $ zfs create <crypto options> pool/new_dataset > $ cp -a pool/old_dataset/* pool/new_dataset/ Twice the space? And, realistically, triple the space to have enough free space before destroying pool/old_dataset, as ZFS feels bad on near-full pools. Sometimes it is "just", sometimes it is impossible! -- // Lev Serebryakov
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?90ec9734-c4d8-b164-aec1-f95fcfda913b>