On Sat, Apr 30, 2022 at 10:33:34AM +0200, Thomas Schmitt wrote: > Hi, > > sp...@caiway.net wrote: > > how does one force to refresh this memory with a command? > > to...@tuxteam.de wrote: > > What do you mean by "refresh"? What's in the cache is always > > the "freshest" version: > > Indeed. With normal filesystem operations there should be no need to call > something like sync(2) in order to get a consistent representation of the > current filesystem state.
Exactly: what we "see", i.e. what we interact with via the operating system facilities is the cache's view. The disk's view will become consistent with that at some time in the future (at least we hope that). [...] > I understand that Vincent Lefevre suspects these discrepancies to be a bug > in the ext4 driver. I rather suspect that ext4 is ok and that we observe > the effects of some other glitch which caused the ext4 driver to create > the finally observed file again, 30 seconds later. It sure looks like a bug. But it would be a bug at a spot where one would expect that it should have bitten oodles of other people by now, so that feeling that we must be missing something is as understandable. Cheers -- t
signature.asc
Description: PGP signature
