On Thu, May 11, 2006 at 03:38:59PM +0100, Darren J Moffat wrote: > What would the output of zfs diffs be ?
My original conception was: - dnode # + changed blocks - + some naming hints so that one could quickly find changed dnodes in clones I talked about this with Bill Moore and he came up with something much better: a diffs filesystem, where one could traverse diffs between snapshots as though they were filesystems, with file diffs represented as holes (or something like that). 6370738 zfs diffs filesystems > How would you apply these diffs ? > How do you select which files to apply and which not to ? ZFS can't handle conflict resolution -- that's up to whoever uses this facility. > I fully support a zfs diffs concept but I don't understand why this is > in any way tide to clone promotion as a zfs command. Me either! > >A best practice would be to keep the application data and config/logging > >data separately. This would avoid the need for this feature. > > Agreed completely and with ZFS anything other than that is IMO poor > planning ZFS data sets are cheap! Same here. Nico -- _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
