Many of us have encountered the infamous "Synthetic time is being issues on partition XYZ". Synthetic time occurs when the modification timestamp (MTS) on at least one object in the partition is set to a time that is in the future. We know the general fix is to declare a new time epoch -- even DSRepair tells you that in its log file when it detects objects with future MTSs. However, what is less commonly known is the side-effect of such an action.
Peter Kuo shares a couple of nifty ways to address synthetic time problems, depending on how far in the future the Modification Time Stamp is (years versus hours).
Check out this Novell Cool Solution