On Fri, 14 Jul 2000, Brian Tao wrote:
This latest restore is still running, and I'm waiting to see ifthis avoids two problems with the rsh method: premature termination and symlink inode count bug. For reasons I have not yet discovered, ufsdump reports "DUMP: Broken pipe" after restore on the Netapp does the finishing "Setting CIFS names to original values" and "Verifying restore correctness" bit. Also, the bug where a restored symlink counts as two inodes in a quota tree is still there in 5.3.6R1. I can empty out the quota tree completely after the restore, and "quota report" still claims (in this case) that there are 9000+ inodes allocated to it.
Yep, both these problems with the local Netapp restore are avoided with Solaris ufsrestore over NFS. Both ufsdump and ufsrestore exit normally after completing the entire filesystem, and there is no double-counting of symlinks on the Netapp side. I'm pretty surprised by this result, since my expectation was that a "ufsdump | rsh restore" would have been the preferred method to restore a filesystem via the network. Instead, it seems to suffer from at least a couple of bugs, chews up more CPU, and offers no performance advantage!