On Sun, 2022-09-11 at 08:13 +1000, NeilBrown wrote: > 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. > "Fine" in the sense that we expect that to happen in this situation. It's not fine for the clients obviously, which is why we're discussing mitigation techniques. -- Jeff Layton <jlayton@xxxxxxxxxx>
