Looks like XFS v5 and ext4 checksums include fs UUID throughout the filesystem metadata. For XFS changing the UUID has been disabled in xfs_admin whereas tune2fs supports changing it (which I'd think could take quite a while). Btrfs supports it via seed device + device add + removing seed which also can take quite a while.
Anyway, three file systems are (or are about to be) affected by this so a general purpose solution seems in order. http://oss.sgi.com/archives/xfs/2015-04/msg00023.html http://comments.gmane.org/gmane.comp.file-systems.ext4/44464 https://ext4.wiki.kernel.org/index.php/Ext4_Disk_Layout#Checksums Chris Murphy -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html