On 4/22/2010 12:04 PM, Theodore Ts'o wrote: > I've essentially despaired at this point that we can get people to care > about setting time and time zones correctly with Linux. :-( > > In fact, Scott has basically argued successfully that we need a "clock > totally broken" option to e2fsck. :-( :-( :-(
Yes, I've seen some of that. If the clock really is totally broken then a sane recovery from this situation may not be possible. As long as the clock at least is never set to a value < the fs creation time, it should not be a problem though. Maybe these systems with broken clocks could at least set them to the creation time of the root fs when mounting? If they do that, then any inodes created since the fs would at least have a ctime after the fs creation timestamp, and therefore you could identify inodes left over from before mkfs and ignore them. -- lazy_itable_init not on by default https://bugs.launchpad.net/bugs/556621 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
