On Tue, Dec 04, 2012 at 01:56:39AM +0800, yangsheng wrote: > Relatime should update the inode atime if it is more than a day in the > future. The original problem seen was a tarball that had a bad atime, > but could also happen if someone fat-fingers a "touch". The future > atime will never be fixed. Before the relatime patch, the future atime > would be updated back to the current time on the next access. So if someone accidentally changes time back a few days, access times go backwards for everything? That doesn't sound right to me - it's going to seriously screw up backups and other scanners that use atime to determine "newly accessed files".... IMO, if you fat-finger a manual atime update or use atimes direct from tarballs, then that's your problem as a user and not the responsibility of the kernel to magically fix for you.... Cheers, Dave. -- Dave Chinner david@xxxxxxxxxxxxx -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
