Curious -- how does your system handle hardlinks? I have a ZFS system which does a ZFS "roll forward": --roll-forward=<ROLL_FORWARD> traditionally 'zfs ro

Curious -- how does your system handle hardlinks? I have a ZFS system which does a ZFS "roll forward": --roll-forward=<ROLL_FORWARD> traditionally 'zfs rollback' is a destructive operation, whereas httm roll-forward is non-destructive. httm will copy only files and their attributes that have changed since a specified snapshot, from that snapshot, to its live dataset... One of more difficult problems I had to deal with was hardlink resolution. Basically I still have to scan the whole dataset, and create a map of hardlinks before any run.