Hi,

2013. 7. 18. 오후 6:22에 "Al Viro" <[email protected]>님이 작성:
>
> On Thu, Jul 18, 2013 at 06:11:23PM +0900, Jaegeuk Kim wrote:
> > The error is reproducible by:
> >
> > After this, when we retrieve the inode->i_name of test2 by dump.f2fs,
we get
> > test1 instead of test2.
> > This is because f2fs didn't update the file name during the f2fs_rename.
>
> Er...  Correct me if I'm wrong, but f2fs appears to support link(2) and
> if rename(2) creates some problem for dump.f2fs, I would expect an
> equivalent link()+unlink() combination to do the same...

Right. I will check that too.
Thank you. :)

> --
> To unsubscribe from this list: send the line "unsubscribe linux-fsdevel"
in
> the body of a message to [email protected]
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
------------------------------------------------------------------------------
See everything from the browser to the database with AppDynamics
Get end-to-end visibility with application monitoring from AppDynamics
Isolate bottlenecks and diagnose root cause in seconds.
Start your free trial of AppDynamics Pro today!
http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
_______________________________________________
Linux-f2fs-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel

Reply via email to