Date: Sat, 23 Feb 2019 20:14:50 +0200 From: Stefan Parvu <sparvu@kronometrix.org> To: ticso@cicely.de Cc: freebsd-arm@freebsd.org Subject: Re: RBPI3B+ FreeBSD 12 ZFS Message-ID: <8BD4B1FF-76C5-423F-9C32-F0D47FD0A604@kronometrix.org> In-Reply-To: <20190223141648.GR93368@cicely7.cicely.de> References: <E387BB48-540D-4F5C-BD4D-2BF410108219@kronometrix.org> <a0239ad1-5b98-1149-1d14-966ed8670e79@denninger.net> <5D976A97-9800-4A9F-A155-F3BD998AFB4C@kronometrix.org> <19ed5715-f1f1-6c5d-5dc6-e9c5225e5445@denninger.net> <1ED1A0A0-C569-433C-9341-30C40BC4CBF7@kronometrix.org> <20190223141648.GR93368@cicely7.cicely.de>
next in thread | previous in thread | raw e-mail | index | archive | help
>=20 > Exactly that's the reason why I'm using ZFS. > Especially with fragile cards. > It also is quite a bit faster on cards as it tends to write more = linear > to them and faster writes usually also mean that the cards won't wear > out as fast as with slow write patterns. Right. That was my first initial idea to see how ZFS will work using = Transcend, SanDisk=20 vs UFS.=20 How did you get started with ZFS/RBPi ? I suppose you started with = vanilla UFs image and then made that to use a zfs pool ? Is there anywhere documented how = one would=20 start using ZFS on RBPI3 because I think there are no ready images using = ZFS. Right ? Thanks, Stefan=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?8BD4B1FF-76C5-423F-9C32-F0D47FD0A604>