Re: [f2fs-dev] sync/umount hang on 3.18.21, 1.4TB gone after crash

On Sat, Sep 26, 2015 at 05:08:33AM +0200, Marc Lehmann wrote: > On Fri, Sep 25, 2015 at 11:42:02AM -0700, Jaegeuk Kim > wrote: > > AFAIK, there-in *commit* means syncing metadata, not userdata. Doesn't it? > > In general, no, they commit userdata, even if not necessarily at

Re: [f2fs-dev] sync/umount hang on 3.18.21, 1.4TB gone after crash

Hi Chao, [snip] > > It seems there was no fsync after sync at all. That's why f2fs recovered > > back to > > the latest checkpoint. Anyway, I'm thinking that it's worth to add a kind of > > periodic checkpoints. > > Agree, I have that in my mind for long time, since Yunlei said that they > may

Re: [f2fs-dev] sync/umount hang on 3.18.21, 1.4TB gone after crash

On Fri, Sep 25, 2015 at 08:00:19AM +0200, Marc Lehmann wrote: > On Thu, Sep 24, 2015 at 11:50:23AM -0700, Jaegeuk Kim > wrote: > > > When I came back after ~10 hours, I found a number of hung task messages > > > in syslog, and when I entered sync, sync was consuming 100%

Re: [f2fs-dev] sync/umount hang on 3.18.21, 1.4TB gone after crash

On Thu, Sep 24, 2015 at 11:50:23AM -0700, Jaegeuk Kim wrote: > > When I came back after ~10 hours, I found a number of hung task messages > > in syslog, and when I entered sync, sync was consuming 100% system time. > > Hmm, at this time, it would be good to check what

Re: [f2fs-dev] sync/umount hang on 3.18.21, 1.4TB gone after crash

On Fri, Sep 25, 2015 at 08:00:19AM +0200, Marc Lehmann wrote: > On Thu, Sep 24, 2015 at 11:50:23AM -0700, Jaegeuk Kim > wrote: > > > When I came back after ~10 hours, I found a number of hung task messages > > > in syslog, and when I entered sync, sync

Re: [f2fs-dev] sync/umount hang on 3.18.21, 1.4TB gone after crash

On Wed, Sep 23, 2015 at 11:58:51PM +0200, Marc Lehmann wrote: > Hi! > > I moved one of the SMR disks to another box with a 3.18.21 kernel. > > I formatted and mounted like this: > >/opt/f2fs-tools/sbin/mkfs.f2fs -lTEST -s90 -t0 -a0 /dev/vg_test/test >mount -t f2fs