Lao Tsao; It is not my intention to do a concurrent mount.
Instead one system will relinquish the zone and pool gracefully and the other system will import it. Only upon a primary system failure, will the second system do a force import. (it's a form of poor man cluster). Warmest Regards Steven Sim Principal Systems Pte Ltd (Singapore) On Mon, May 2, 2011 at 5:44 PM, LaoTsao <laot...@gmail.com> wrote: > It should work, but keep in mind > Zfs is not build for shared by two host, but with zpool controlled by host1 > one can force imported to host2 resulting in corrupted zpool > > > Sent from my iPad > Hung-Sheng Tsao ( LaoTsao) Ph.D > > On May 2, 2011, at 1:09 AM, Steven Sim <unixan...@gmail.com> wrote: > > Hello All; > > I have been asked to create a zone on a shared LUN which will enable us to > detach and attach the zone onto another system (exactly same hardware > architecture). > > So I have create a ZFS Pool and specified the zonepath to be on root > filesystem of that pool > > e.g. > > zfs create -m /zones/webzone webpool <san_disk> > > The above creates a ZFS pool called "webpool" and mounts to /zones/webzone. > > I have then in zonecfg specified the following > > zonecfg:webzone> # zonecfg -z > webzone > > webzone: No such zone > configured > > Use 'create' to begin configuring a new > zone. > > zonecfg:webzone> > create > > zonecfg:webzone> set > zonepath=/zones/webpool > > zonecfg:webzone> set ip-type=exclusive > . > . > . > > Upon a need to detach, I will shutdown the zone and detach as follows .. > > # zoneadm -z appzone detach > > And then deport the ZFS Pool webpool > > #zpool deport webpool > > On the other system, I would then > > #zpool import webpool > > And start the Zone (assuming of course the zone XML file has already been > imported and created on the 2nd node). > > Is the above the best way to do things? > > Warmest Regards > Steven Sim > > _______________________________________________ > zones-discuss mailing list > zones-discuss@opensolaris.org > >
_______________________________________________ zones-discuss mailing list zones-discuss@opensolaris.org
