On Fri, 09 Sep 2022, Jeff Layton wrote: > > The machine crashes and comes back up, and we get a query for i_version > and it comes back as X. Fine, it's an old version. Now there is a write. > What do we do to ensure that the new value doesn't collide with X+1? (I missed this bit in my earlier reply..) How is it "Fine" to see an old version? The file could have changed without the version changing. And I thought one of the goals of the crash-count was to be able to provide a monotonic change id. NeilBrown
