Date: Sun, 31 Oct 2004 00:43:08 -0400 (EDT) From: Andre Guibert de Bruet <andy@siliconlandmark.com> To: Jens Rehsack <rehsack@liwing.de> Cc: current@freebsd.org Subject: Re: HEADSUP: Filesystem rototiling over Message-ID: <20041031003429.A82803@alpha.siliconlandmark.com> In-Reply-To: <4183BF18.3010509@liwing.de> References: <27734.1099147280@critter.freebsd.dk> <4183BF18.3010509@liwing.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, 30 Oct 2004, Jens Rehsack wrote: > Poul-Henning Kamp wrote: >>>>> Oh, that means for each update you have to stop all jails running >>>>> on those mounts? How useful could that be on production machines? >>>> >>>> I don't know, that depends on what you use jails for. >>> >>> Web-Service(s), Mail-Service(s), Name-Service, ... >>> >>> And on each update I had to stop the services, shutting down the jail, >>> unmount each ro-bunch, mount rw, update, unmount, remount ro-bunches, >>> starting jails & services. >> >> Then this is probably not a good thing for your installation. > > Maybe someone could point some usages where it's a good thing... It would be very useful for a re-imaging system on a shared-hosting host, with numerous jails. You could write scripts to have an end-userrestore a jail back to its original state through this mount. In this case, the filesystem wouldn't be terribly useful, except when re-imaging, so unmounting all mounts isn't that big of a deal. I do agree that it would be nice to be able to have one RW mount and a ton of RO mounts. I would even be willing to settle for having to mount the RW mount first and have this operating fail if the filesystem is already mounted RO somewhere. Andy | Andre Guibert de Bruet | Enterprise Software Consultant > | Silicon Landmark, LLC. | http://siliconlandmark.com/ >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20041031003429.A82803>