Date: Mon, 22 Aug 2011 08:13:54 -0500 (CDT) From: Nathan Whitehorn <nwhitehorn@freebsd.org> To: "Andrey V. Elsukov" <bu7cher@yandex.ru> Cc: Garrett Cooper <yanegomi@gmail.com>, freebsd-current@freebsd.org, Marcel Moolenaar <marcel@xcllnt.net> Subject: Re: Well, there goes Windows! Message-ID: <alpine.BSF.2.00.1108220813300.87003@banshee.munuc.org> In-Reply-To: <4E51E019.4060206@yandex.ru> References: <CAGH67wRFP9nFQLr0Gh-h4rKWrndZSy=6Q%2BKLC_U5Fg4RD%2BJMCw@mail.gmail.com> <4E4DB9A7.4040404@freebsd.org> <CAGH67wQoXOju3=OTh%2B6JoKLxkp7Vzqu8vg%2BO9X=DPXB5EkBJtQ@mail.gmail.com> <4E517978.2020705@freebsd.org> <64622705-80AB-4FEF-91E9-8F3041818B4E@xcllnt.net> <4E519C13.4060700@freebsd.org> <4E51E019.4060206@yandex.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 22 Aug 2011, Andrey V. Elsukov wrote: > On 22.08.2011 4:00, Nathan Whitehorn wrote: >> The larger problem is that this behavior means that destroying gparts sometimes doesn't work at >> all. For instance, if you have nested partitioning like MBR+BSD (or EBR) it is not possible to >> destroy the underlying MBR geom without committing the destruction of the BSD geom. This is >> because the MBR geom cannot be destroyed, even without committing, while it continues to have >> children, which it does due to the ghost geom for the BSD slice. > > Actually you can destroy underlying MBR geom without committing, just use "force" flag. > But there is another problem, the metadata of nested scheme will not deleted and it might > appear again when you create new MBR and new partition in the same place. This isn't true for nested partitioning, at least in my experience. -Nathan > -- > WBR, Andrey V. Elsukov > >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.00.1108220813300.87003>