Bart Smaalders <[email protected]> writes: [...]
Harry wrote: >> So.. it can't be a clone... isn't a clone supposed to be a duplicate >> in every detail? Like in science fiction stories where a human is >> cloned but some tiny dna difference leads to a monster who isn't a >> clone anymore. hehe >> Bart responded: > But this is a ZFS clone - which does copy on write - so until you change > something, there's no disk space overhead ;-). > >> Put another way, do I need that capability to be able to completely >> roll back to a known good state? > > Create a clone of the current environment and never touch it. Thanks for that reference to `copy on write (COW)'. This is my first brush with those concepts which I am finding good discussion of with google. I'll admit I don't fully understand it yet. But correct me if I have this wrong. The miss-named `clone', is not stand alone (Something one would expect from a `clone'). That is, it relies still on the parent if called into duty. Is that right? Could you move(mv) the clone to a new disc and boot it up? Or does the COW kick in during mv... I'm not clear what happens. Similar with the `snapshot'. It sounds like an OS frozen in time when the shutter snapped. But can you move it to a new disc and boot up? _______________________________________________ indiana-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
