Darren J Moffat wrote:
How would you apply these diffs ?
How do you select which files to apply and which not to ?
For example you want the log files to be "merged" some how but you
certainly don't want the binaries to be merged.
This would have to be a decision by the user when the sync takes place.
They would have to know the application.
For many applications you can't just blindly copy files around while
they are running - they don't like it and it leads to application layer
data corruption.
The assumption is that if you are promoting a filesystem then the
application would no longer be running. I don't believe that the
original proposal accounted for doing a live application promotion, right?
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.
Yes, having a the zfs diffs concept external to promote is a good
concept but having promote automatically take advantage of it is an ease
of use enhancement. That's what the suggestion was all about.
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!
This would be great but I'm not sure we can dictate this since
application vendors will install often in whatever hierarchy they chose.
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
