Excellent information. Thanks again all On Fri, Aug 3, 2012 at 9:06 AM, Jan Owoc <[email protected]> wrote:
> On Fri, Aug 3, 2012 at 6:43 AM, Kees Nuyt <[email protected]> wrote: > > On Thu, 2 Aug 2012 14:59:13 -0600, you wrote: > >>Having said that, I believe they need to be mounted in empty > >>directories, so you'd have to do: > >># mv datastore/vmimages/server1 datastore/vmimages/server1.bak > >># zfs create -o [options here] datastore/vmimages/server1 > >># cp -a datastore/vmimages/server1.bak/* datastore/vmimages/server1 > >># rm -r datastore/vmimages/server1.bak > > > > Another procedure would be to > > - take all VM's down > > - zfs rename datastore/vmimages to datastore/oldimages > > - zfs create datastore/vmimages > > - zfs create datastore/vmimages/server1 > > - mv /datastore/oldimages/server1/* /datastore/vmimages/server1/ > > - zfs create datastore/vmimages/server2 > > - mv /datastore/oldimages/server2/* /datastore/vmimages/server2/ > > Actually, Kees' procedure is better. I didn't remember off the top of > my head whether one can do an "mv" command between different > filesystems (some OSes don't like it; OI seems to handle it ok, and > does it even across pools). > > While you're recreating the filesystems anyway, I suggest you do a > quick read through the possible options for creating a new filesystem > - some can only be specified on creation. Ones I like to set include > atime (off), casesensitivity (mixed, for SMB sharing), nbmand (on), > utf8only (on), normalization (formD, for cross-OS compatibility), > checksum (sha256), snapdir (visible - I like to see the .zfs). > > Jan > > _______________________________________________ > OpenIndiana-discuss mailing list > [email protected] > http://openindiana.org/mailman/listinfo/openindiana-discuss > -- Mark _______________________________________________ OpenIndiana-discuss mailing list [email protected] http://openindiana.org/mailman/listinfo/openindiana-discuss
