Date: Mon, 13 Jan 2014 16:33:39 -0800 From: Marcel Moolenaar <marcel@xcllnt.net> To: Mark Felder <feld@FreeBSD.org> Cc: freebsd-geom@freebsd.org Subject: Re: "deep" gpart backup? Message-ID: <F0F3FBB0-348F-4F20-AE06-449A9A7B7E5E@xcllnt.net> In-Reply-To: <1389461267.16576.69479689.0A3D893A@webmail.messagingengine.com> References: <1023566295.20140105015301@serebryakov.spb.ru> <1389461267.16576.69479689.0A3D893A@webmail.messagingengine.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Jan 11, 2014, at 9:27 AM, Mark Felder <feld@FreeBSD.org> wrote: > On Sat, Jan 4, 2014, at 15:53, Lev Serebryakov wrote: >> Hello, Freebsd-geom. >> >> Is here any way to make "deep" "gpart backup | gpart restore"? Now, when >> I >> have disk with MBR, with two slices, each of which has BSD label, I need >> three calls of backup / restore commands with proper arguments. It looks >> just stupid :) >> > > If gpart can see and manipulate all of these elements it really should > be able to backup and restore them all atomically. This statement is close to being ridiculous. Being able to operate on all components is absolutely not a sufficient condition for doing atomic operations across a multitude of them. Atomicity is a very particular requirement. Note also that gpart (in its most vague definition) cannot actually manipulate on *all* elements at the same time. Nested partitioning schemes are not seen by the gpart invocation that works on the outer-most container. Only when running gpart on a partition will it (= gpart) be able to work on the nested partitions. As such, no single gpart invocation sees all levels of nesting. gpart is an inherently low-level utility and what you want is intended (i.e. by design) to be handled at an application layer above gpart. FYI, -- Marcel Moolenaar marcel@xcllnt.net
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?F0F3FBB0-348F-4F20-AE06-449A9A7B7E5E>