You're right, it would make no sense to copy that file/folder, but I just wanted to check in case I was missing something. It seems that fseventsd somehow got corrupted on the new disk and recreating it fixed the problem. Had nothing to do with SuperDuper, thanks for confirming that.
I have been doing clones and backups for years in case of the event that a disk failed. So far, I have only used these clones to restore an occasional file that was accidentally deleted. So a disaster finally happened and the restoration of the SuperDuper clone on the new replacement hard drive was simple and fast.
|