From nobody Wed Sep 03 09:30:16 2025 X-Original-To: freebsd-current@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 4cGy594n1qz65pBF for ; Wed, 03 Sep 2025 09:30:21 +0000 (UTC) (envelope-from junchoon@dec.sakura.ne.jp) Received: from www121.sakura.ne.jp (www121.sakura.ne.jp [153.125.133.21]) (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 did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4cGy591wSRz3GTV for ; Wed, 03 Sep 2025 09:30:21 +0000 (UTC) (envelope-from junchoon@dec.sakura.ne.jp) Authentication-Results: mx1.freebsd.org; none Received: from kalamity.joker.local (124-18-6-240.area1c.commufa.jp [124.18.6.240]) (authenticated bits=0) by www121.sakura.ne.jp (8.18.1/8.17.1/[SAKURA-WEB]/20201212) with ESMTPA id 5839UGeB059675; Wed, 3 Sep 2025 18:30:17 +0900 (JST) (envelope-from junchoon@dec.sakura.ne.jp) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=dec.sakura.ne.jp; s=s2405; t=1756891817; bh=nGoZMXHK2u23vARqKuATXjlsPcT5rpWC5qQ9hVzd16c=; h=Date:From:To:Cc:Subject:In-Reply-To:References; b=Ofm2jZAoyovteZmRwijsk8DVwIpeZjFnQ0ShDbya0aSFOV3IQjlXd3IDLmNmosMxq Tm8i2OfeyI6lXImGDfCRE06U77tfXTzF1/BVo4bMG/1R2B2NGkWHhzNLmRrKxelENN 5SwdM7akenKcoaE0Mz2AjM4yjNJPEStwQty9T/mY= Date: Wed, 3 Sep 2025 18:30:16 +0900 From: Tomoaki AOKI To: Warner Losh Cc: Graham Perrin , FreeBSD-CURRENT Subject: Re: Using a recovery partition to repair a broken installation of FreeBSD Message-Id: <20250903183016.a608f97e10208e904a11a4ba@dec.sakura.ne.jp> In-Reply-To: References: <7b384ac0-9b24-43a4-bf63-012d745155a7@gmail.com> <18e1a7e9-07d8-43a2-96af-0acdab6c2920@gmail.com> <98890564-ad8f-411a-9c00-45326a9d6ff5@gmail.com> Organization: Junchoon corps X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.33; amd64-portbld-freebsd14.3) List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@FreeBSD.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:7684, ipnet:153.125.128.0/18, country:JP] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Rspamd-Queue-Id: 4cGy591wSRz3GTV On Tue, 2 Sep 2025 13:26:53 -0600 Warner Losh wrote: > On Tue, Sep 2, 2025 at 12:53 PM Graham Perrin > wrote: > > > On 01/09/2025 02:58, Graham Perrin wrote: > > > An enhancement to bsdinstall could, before creation of the partition > > > table, allow the user to specify an amount of space to be left free at > > > the end of a device … > > > > > > For now, short term, is the (simple) free space idea attractive? > > > > Longer term: I'm not averse to more complex enhancements around e.g. > > /rescue/, however I _do_ like the idea of free space. > > > > Freedom for the user to do whatever they want. They might, or might not, > > want to use the space for the content of > > FreeBSD-15.0-RELEASE-amd64-memstick.img … and so on. Maybe this overlaps > > with ZFS-specific bsdinstall report > > . > > > > Things are small enough, I'd rather just create it in the ESP directly. > Special reserved space on disks are nothing but a pain. > > Warner What I imagine with this specific use-case (example): 1. Create 250MB ESP as, i.e., nda0p1 2. Create freebsd-zfs for all remained amount after 3., as nda0p2 3. Create 64GB freebsd-swap as nda0-3 at the end of the drive In this case, I need to calculate the (aligned) size of 2. manually, which is a bit pain. Something like gpart add -a 1M -t freebsd-zfs -l zfsNVMe001 -i 2 -s fill nda0 then create -i 3 and later, and finally gpart commit actually create second and later partitions would be helpful. -- Tomoaki AOKI