Date: Wed, 19 Feb 2014 21:13:54 +0100 From: vermaden <vermaden@interia.pl> To: Andrew Hotlab <andrew.hotlab@hotmail.com> Cc: "ports@freebsd.org" <ports@freebsd.org>, Bryan Drewery <bdrewery@freebsd.org> Subject: RE: [patch] sysutils/beadm Message-ID: <homjjwiodaxygmhvosyy@ljzk> In-Reply-To: <DUB118-W42DC9396D0C4C8966546F4F69B0@phx.gbl> References: <DUB129-W68936A08892FE3CE358447F69D0@phx.gbl> <DUB118-W42DC9396D0C4C8966546F4F69B0@phx.gbl>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi, I will try to test that patch then, I will reply when I'm done with info ab= out issues or info about commit ;) Regards, vermaden Od: "Andrew Hotlab" <andrew.hotlab@hotmail.com> Do: "Bryan Drewery" <bdrewery@freebsd.org>;=20 Wys=C5=82ane: 17:18 =C5=9Aroda 2014-02-19 Temat: RE: [patch] sysutils/beadm > ---------------------------------------- > > Date: Wed, 19 Feb 2014 07:27:45 -0600 > > From: bdrewery@FreeBSD.org > > To: andrew.hotlab@hotmail.com > > CC: ports@freebsd.org; vermaden@interia.pl > > Subject: Re: [patch] sysutils/beadm > > > > On 2/13/2014 4:19 PM, Andrew Hotlab wrote: > >> First of all, thank you very much for the good work with this port. I'= m sure it's changing the life of a lot FreeBSD system administrators! > >> > >> In my setup I have the following layout (several datasets for /usr, /v= ar, etc.): > >> > >> NAME USED AVAIL REFER MOUNTPOINT > >> sys 1.55G 18.0G 31K none > >> sys/ROOT 532M 18.0G 31K none > >> sys/ROOT/default 114K 18.0G 250M / > >> sys/ROOT/default/tmp 22K 18.0G 38K /tmp > >> sys/ROOT/default/usr 1K 18.0G 245M /usr > >> sys/ROOT/default/var 48.5K 18.0G 36.4M /var > >> sys/swap 1.03G 19.0G 16K - > >> > >> At this moment the utility does not seems to be able to manage this sc= heme, since it sets the mountpoint property as "legacy" for all datasets un= der the root, thus preventing to automatically mount any subdirectory at bo= ot. > >> I've tested this simple solution (to let do the job to the canmount pr= operty), and it seems to solve the problem without affecting the behavior w= hen all system folders are located under a single root dataset (please see = the patch below). I'd be glad if you'll include it in the next port revisio= n. > >> > > > > ACK on this. CC'ing upstream maintainer too. > > > > I run the same setup but I specifically set /usr /var and /tmp mntpoint= s > > to /usr,/var/,/tmp to avoid this issue. I am not sure if mntpoint=3D/ i= s > > proper. I recall there being an issue with it. I would much prefer your > > patch though if it is safe. > > > > Does beadm mount still work with this to mount a new BE into /tmp? > > > > Ie, > > > > beadm create newbe > > beadm mount newbe > > > > Does it go and remount / or only touch /tmp? > > >=20 > It seems to behave correctly, as you can see in the attached transcript. >=20 > > How about activating? Does it blow away / right away or wait until rebo= ot? >=20 > Since beadm changes only the "canmount" ZFS property to set the active en= vironment for the next reboot, there is no implications for the running env= ironment. >=20 > Regards >=20 > Andrew =20 =
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?homjjwiodaxygmhvosyy>