On Sat, Feb 8, 2020 at 5:43 PM Zygo Blaxell <ce3g8jdj@xxxxxxxxxxxxxxxxxxxxx> wrote: > > Upon reboot, the filesystem reverts to its state at the last completed > transaction 4441796 at #2, which is 5 hours earlier. Everything seems to > be intact, but there is no trace of any update to the filesystem after > the transaction 4441796. The last 'fi usage' logged before the crash > and the first 'fi usage' after show 40GB of data and 25GB of metadata > block groups freed in between. Is this behavior affected by flushoncommit mount option? i.e. do you see a difference using flushoncommit vs noflushoncommit? My suspicion is the problem doesn't happen with noflushoncommit, but then you get another consequence that maybe your use case can't tolerate? -- Chris Murphy
