On Fri, Sep 25, 2015 at 01:20:25AM +0200, Marc Lehmann <schm...@schmorp.de> 
wrote:
> On Thu, Sep 24, 2015 at 11:28:36AM -0700, Jaegeuk Kim <jaeg...@kernel.org> 
> wrote:
> > > The log starts after only 20GB had been written. Here is the status output
> > > at 25GB:
> > > 
> > > http://ue.tst.eu/734f7883107ee4dabff77602db92310b.txt
> > 
> > It seems about 700MB were moved by background GC.

And before rebooting I did another sync, which took 130s, using 100% system
time. This is the status output afterward:

http://ue.tst.eu/6d0398c4184fdbef059e90a6bf454241.txt

Is it normal that f2fs takes this long for a sync? What happens when,
during shutdown, there is a timeout during umount and systemd shuts down
anyway, or the fs doesn't get unmounted, will there be data loss because
of rolling back?

I am a bit concerned, because the filesystem was sitting idle for hours,
and I expect a crash at that point to not lose any data due to reverting
to a checkpoint.

-- 
                The choice of a       Deliantra, the free code+content MORPG
      -----==-     _GNU_              http://www.deliantra.net
      ----==-- _       generation
      ---==---(_)__  __ ____  __      Marc Lehmann
      --==---/ / _ \/ // /\ \/ /      schm...@schmorp.de
      -=====/_/_//_/\_,_/ /_/\_\

------------------------------------------------------------------------------
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel

Reply via email to