[dnanian]

While we are going to correct this in the next release, the report is a bit misleading because the "problem" isn't just minor, it's of no consequence whatsoever to most users.. and doesn't involve metadata at all. Your files, and your metadata, are being copied correctly.

Basically the "flaw" is that SuperDuper! doesn't copy "FIFOs" or local device files. This was actualy by design, because -- in a standard OSX install -- device files are automatically created at startup time. And FIFOs are kind of 'queues' for communication between programs (rarely used) -- that are created at startup, typically in /tmp.

In fact, neither one of these types of 'files' (which are really special directory entries with no contents) can be copied at all -- they must be recreated on the backup, kind of as placeholders, because they don't really have much meaning across a restart.

We had decided long ago to not copy them (because we determined it didn't really make sense to do so), but since a tool is out that tests against this case, and because people might misinterpret the 'failure' to pass that particular test as something important, we've reversed that decision and will "copy" them in the future.

Note that, in general, we feel it's far more important to be able to faithfully copy actual file structures such as hard linked folders (something that Time Machine uses, but isn't exclusive to Time Machine, and that does have meaning across a restart), real data files, metadata (EAs, forks, ACLs), etc -- some of which the test tools don't actually check.

Hope that helps to clarify the issue.