index | | raw e-mail
That, I don't really know. One proposal I had for ZFS is that it shouldn't let the uberblock timestamps go backwards, or at least beyond a certain threshold -- if it tries to, we could just bump the timestamp by 1 from the recorded time so that our new uberblock is preferred and move on, knowing that inittodr() would likely prefer the notion of time we provide that was on disk. Any timestamps we try to pull from mountroot to ntpd/chrony/etc. would still be bogus, but a lot better than they are today for these systems. Having written that out, I think it's worth looking closer at that ub update and whether it gets persisted to disk. I'm specifically wondering if it's possible that we could needlessly lose writes as a consequence after an unclean shutdown even on systems with an RTC, since the clock isn't setup until after. Thanks, Kyle Evanshome | help