Hi Chao, On Thu, Aug 15, 2019 at 3:49 PM Chao Yu <[email protected]> wrote: > I doubt that before triggering urgent GC, system has dirty datas in memory, > then > when you trigger `sync`, GCed data and dirty data were flushed to devices > together, if we write dirty data with out-place-update model, it may make > fragment. > > So we can try > - sync > - trigger urgent GC > - sync > - cat /sys/kernel/debug/f2fs/status to check 'Dirty' field, the value should > close to zero
It's actually not zero. Before triggering gc_urgent: 601 After gc_urgent ends and doing a `sync`: 400 And after another 2nd gc_urgent run, it finally becomes 0. So I'm guessing this wasn't intentional? :P Thanks, _______________________________________________ Linux-f2fs-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
