From owner-freebsd-fs@freebsd.org Sun Jul 8 23:34:12 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 018DB104400E for ; Sun, 8 Jul 2018 23:34:12 +0000 (UTC) (envelope-from jude.obscure@yandex.com) Received: from forward100j.mail.yandex.net (forward100j.mail.yandex.net [IPv6:2a02:6b8:0:801:2::100]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "forwards.mail.yandex.net", Issuer "Yandex CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 7D32D73098; Sun, 8 Jul 2018 23:34:11 +0000 (UTC) (envelope-from jude.obscure@yandex.com) Received: from mxback2j.mail.yandex.net (mxback2j.mail.yandex.net [IPv6:2a02:6b8:0:1619::10b]) by forward100j.mail.yandex.net (Yandex) with ESMTP id 714445D82AB8; Mon, 9 Jul 2018 02:34:08 +0300 (MSK) Received: from smtp4o.mail.yandex.net (smtp4o.mail.yandex.net [2a02:6b8:0:1a2d::28]) by mxback2j.mail.yandex.net (nwsmtp/Yandex) with ESMTP id pPWh9I7fcT-Y84eG1r5; Mon, 09 Jul 2018 02:34:08 +0300 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.com; s=mail; t=1531092848; bh=h5G3JykqdWSbO/1z7pbTLTdsGt3vD8tiPu9PGIDyBdo=; h=Subject:To:Cc:References:From:Message-ID:Date:In-Reply-To; b=DPPuOJVxFe/yfNy4Ei9DJw4Mdvg+P1byHrMNUvjSrvzCzUnym1pTYrSGEiK2h9C4u 7CNHtBJ2CvXWk44YIk2dnBgU06hK4lizUlQpKEhH/DmLDlWpgphIDLyL/eTpUGnCom 6RbN0M48fOnL1tJgVnJLwu7sbtv4WNBh3fuHOd2M= Received: by smtp4o.mail.yandex.net (nwsmtp/Yandex) with ESMTPSA id 6XYPSudFLI-Y6xmVvnT; Mon, 09 Jul 2018 02:34:07 +0300 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client certificate not present) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.com; s=mail; t=1531092847; bh=h5G3JykqdWSbO/1z7pbTLTdsGt3vD8tiPu9PGIDyBdo=; h=Subject:To:Cc:References:From:Message-ID:Date:In-Reply-To; b=AVwhdVSSXnNN6K0SGJ/R6qQnJZPzYvykmf7Pw5c3k7aqVPMJKhTRFR8iQ3Sad7HCM 6N6S15dPpfHaNGO6VMUuJHJFJjMdw3KWHolMUN4qh85qLgaURz7qhkJ8Filp+QulwN 5SOcNWw5X4r06HtW15hghsv1L+fuTT9g8X1PcYrc= Authentication-Results: smtp4o.mail.yandex.net; dkim=pass header.i=@yandex.com Subject: Re: A request for unnested UFS implementation in MBR To: Gary Palmer Cc: Ronald Klop , freebsd-fs@freebsd.org References: <98201d37-2d65-34c6-969e-c9649f1a3ab1@yandex.com> <20180708230442.GB47960@in-addr.com> From: Manish Jain Message-ID: <651087d5-00ab-7fd4-bc05-b25941c9099d@yandex.com> Date: Mon, 9 Jul 2018 05:02:03 +0530 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.8.0 MIME-Version: 1.0 In-Reply-To: <20180708230442.GB47960@in-addr.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 08 Jul 2018 23:34:12 -0000 On 07/09/18 04:34, Gary Palmer wrote: > I do not understand why you need to create the BSD label. Nothing > in the GEOM framework is forcing you to do that > > Is this for a bootable disk or just storage? Perhaps my understanding of the situation was incomplete. Following up on your reply, I see that creating UFS directly on the freebsd slice does seem to work well: /root <<: gpart destroy -F da0 da0 destroyed /root <<: ls /dev/da* /dev/da0 /root <<: gpart create -s MBR da0 da0 created /root <<: gpart add -t freebsd da0 da0s1 added /root <<: newfs /dev/da0s1 1) Is that a standard, acceptable way of working with UFS ? I have always thought the only way to use UFS under MBR was to first a BSD nest. 2) And also, I think cannot get that behaviour during FreeBSD installation with MBR + UFS, which stills leads to creation of the unnecessary 'a' device when a user installs FreeBSD on a single, primary partition. Your answer - and my interpretation thereof - means possibly things are just fine the way they are : - ) Thanks for replying. Manish Jain