From nobody Tue Aug 23 12:51:30 2022 X-Original-To: freebsd-arm@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4MBpyW3RsWz4ZbPb for ; Tue, 23 Aug 2022 12:51:47 +0000 (UTC) (envelope-from sparvu@kronometrix.org) Received: from mail.kronometrix.org (mail.kronometrix.org [79.134.105.182]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "mail.kronometrix.org", Issuer "Sectigo RSA Domain Validation Secure Server CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4MBpyV42DSz43kg for ; Tue, 23 Aug 2022 12:51:46 +0000 (UTC) (envelope-from sparvu@kronometrix.org) Received: from smtpclient.apple (176-93-235-61.bb.dnainternet.fi [176.93.235.61]) (authenticated bits=0) by mail.kronometrix.org (8.17.1/8.16.1) with ESMTPSA id 27NCpaZO024934 (version=TLSv1.3 cipher=TLS_AES_128_GCM_SHA256 bits=128 verify=NO); Tue, 23 Aug 2022 12:51:37 GMT (envelope-from sparvu@kronometrix.org) X-Authentication-Warning: mail.kronometrix.org: Host 176-93-235-61.bb.dnainternet.fi [176.93.235.61] claimed to be smtpclient.apple Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable From: Stefan Parvu List-Id: Porting FreeBSD to ARM processors List-Archive: https://lists.freebsd.org/archives/freebsd-arm List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-arm@freebsd.org Mime-Version: 1.0 (1.0) Subject: Re: From UFS to ZFS as root on RBPI4 Date: Tue, 23 Aug 2022 15:51:30 +0300 Message-Id: References: Cc: freebsd-arm In-Reply-To: To: John Kennedy X-Mailer: iPhone Mail (19G82) X-Rspamd-Queue-Id: 4MBpyV42DSz43kg X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of sparvu@kronometrix.org designates 79.134.105.182 as permitted sender) smtp.mailfrom=sparvu@kronometrix.org X-Spamd-Result: default: False [-2.80 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-1.000]; MV_CASE(0.50)[]; R_SPF_ALLOW(-0.20)[+a]; MIME_GOOD(-0.10)[text/plain]; RCPT_COUNT_TWO(0.00)[2]; ASN(0.00)[asn:16302, ipnet:79.134.96.0/19, country:FI]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; FROM_EQ_ENVFROM(0.00)[]; MLMMJ_DEST(0.00)[freebsd-arm@freebsd.org]; RCVD_VIA_SMTP_AUTH(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_COUNT_TWO(0.00)[2]; MID_RHS_MATCH_FROM(0.00)[]; ARC_NA(0.00)[]; TO_DN_ALL(0.00)[]; FROM_HAS_DN(0.00)[]; DMARC_NA(0.00)[kronometrix.org]; HAS_XAW(0.00)[]; RCVD_TLS_ALL(0.00)[] X-ThisMailContainsUnwantedMimeParts: N Thanks for pointers.=20 Will start soon this and report back my progress. The idea would be to have a= ready freebsd microsd image with ZFS installed by default Best Regards, Stefan Parvu > On 21. Aug 2022, at 19.12, John Kennedy wrote: >=20 > =EF=BB=BFOn Fri, Aug 19, 2022 at 01:38:56PM +0300, Stefan Parvu wrote: >>> My RPI4 8GB runs on ZFS on a USB-disk. >> Would this work for another microSD card, as well, I bet. Right? =20 >> Boot from the microSD card and plug-in via USB another microSD card, repe= at the procedure and build sort of FreeBSD 13.1 with ZFS root on microSD. >> Are there any problems why ZFS wont work for a microSD card ? >=20 > I've done ZFS on SD and much smaller RAM sizes on older RPIs when it > was arguably way more painful. I'd probably recommend doing a > bsdinstall onto the USB-attached SDcard, but the RootOnZFS page is what > I used back when that was a new thing. >=20 > Two things I'd definitely do differently are: >=20 > 1: Having your swap be a real, proper swap partition (if you do hit > your swap hard, you really don't want disk buffering messing > up your performance, plus it's always nice to get kernel > dumps if you ever want to contribute that way). > 2: Break out /usr/obj/usr into it's own dataset/filesystem. If you > compile your own kernel+world, that is where the objects end up > and if you do things like boot-environments, that'll really blow > up the size for something you probably won't care about. >=20