Responding to p...@paularcher.org's sep 30 2009 9:21 post: For the entire file system, I have chosen zfs send/receive, per thread "Best way to convert checksums". I has concerns, they have been answered.
Do my immediate need is answered. The question remains as to how to copy portions of trees, which zfs send/receive do not do. that is, just copy stuff around normally. cp, tar, cpio, rsync are all great. If one digs in, there are various issues with various implementations, none of which are documented. Witness the warnings I have gotten that sun tar does not support sparse files. Is this true? Was it true, has it been fixed? There is another thread that says something to the effect that if you tell sun tar to not copy acls that it creates an empty acl with every file, where there was no acl at all in the source! Every implementation of every utility has what read like credible, carefully documented rocks thrown at them. My conclusion is to not use any system features that cannot be verified with a simply file-contents comparison. This will check the file contents, the filename, and the pathname. I can see the file owner, group, and dates. Sparseness, acls, and extended attributes I will simply not use. I will have to use non-solaris utilities for the compare or build my own in scripts because I have "large files" and diff does not support them and cmp does not recurse. Thank you all for you insights and suggestions. I consider this to be done, but given the unsatisfying result, I would still welcome any new remarks. -- This message posted from opensolaris.org _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
