When using zfs send/receive to do the conversion, the receive creates a new file system:
zfs snapshot zfs01/h...@before zfs send zfs01/h...@before | zfs receive afx01/home.sha256 Where do I get the chance to "zfs set checksum=sha256" on the new file system before all of the files are written ??? The new filesystem is created automatically by the receive command! Although it does not say so in the man page or zfs admin guide, it certainly seems reasonable that I don't get a chance - the idea is that send/receive recreates the file system exactly. This would still have an ambiguity as to whether the new blocks are created/copied with the checksum algorithm they had in the source filesystem (Which would not result in the conversion I am trying to accomplish), or are they created and checksumed with the algorithm specified by the checksum PROPERTY set in the source file system at the time of the send/receive (which WOULD do the conversion I am trying to accomplish)? Is there a way to use send/receive to duplicate a filesystem with a different checksum, or do I use cpio or tar? (I pick on cpio and tar because they are specifically called out in the zfs admin manual as saving and restoring zfs file attributes and ACLs). Thanks. --Ray -- This message posted from opensolaris.org _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
