"Udo Grabowski (IMK)" <udo.grabow...@kit.edu> writes: > From 7 years of experience with zfs I absolutely recommend to > go the other way, create filesystems below /rmh/... for each > host. The simple reason is that you can easily snapshot each > host, transport it, or even promote it to be the root on a real > physical machine. And you can easily destroy a machine filesystem. > It's all much easier and faster than doing a tar, rm, rsync > or whatever. With ZFS there's no reason not to have filesystems > for everything. We usually have more than hundred on a single > 96 TB fileserver, no problems, but great savings in manageability.
Thanks for the input. I wondered how it works with something like a 4 level set of zfs fs. /rmh/host1/someproj/Acollection /rmh/host2/someproj/Acollection Seven filesystems in all assuming a .zfs at each level. Now, if you wanted to send receive the whole works you would not be able to send/receive a snapshot from /rmh/, right? So you'd need to send/receive all seven then, eh? Or is there something like the -p operator to 'zfs create -p [...]' that can be invoked to allow you to send/receive the whole batch in one go? _______________________________________________ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
