* Why does e2fsck stop on system clock differences?
@ 2012-02-28 16:22 Eric Sandeen
0 siblings, 0 replies; only message in thread
From: Eric Sandeen @ 2012-02-28 16:22 UTC (permalink / raw)
To: ext4 development
I've got Fedora users concerned (again) about clock problems stopping their boot in e2fsck.
I know about the +/- 24h slop, and the broken_system_clock e2fsck.conf setting, which we might just set to do away with this issue.
But I wonder if I can get a little historical perspective from the extN elders on why e2fsck is so clock-obsessed. (I think this has been discussed in other threads, but I'm not finding them now)
What are the actual risks if we just ignore time differences at fsck time, can we get this stated on the record (hopefully in a somewhat google-able $SUBJECT?)
Thanks,
-Eric
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2012-02-28 16:22 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2012-02-28 16:22 Why does e2fsck stop on system clock differences? Eric Sandeen
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).