[f2fs-dev] [PATCH v2] dump.f2fs: fix a wrong report for dump an {d, id, did}node

2018-03-06 Thread Yunlei He
fix a wrong report for dump an {d,id,did}node like this: [print_node_info: 283] Node ID [0x6820:26656] is direct node or indirect node. [0] [0x 16b6684 : 23815812] [1] [0x 16b6685 : 23815813] [2] [0x 16b6686 : 23815814] [3]

[f2fs-dev] [PATCH v5] f2fs: introduce mount option for fsync mode

2018-03-06 Thread Junling Zheng
Commit "0a007b97aad6"(f2fs: recover directory operations by fsync) fixed xfstest generic/342 case, but it also increased the written data and caused the performance degradation. In most cases, there's no need to do so heavy fsync actually. So we introduce new mount option "fsync_mode={posix,strict

Re: [f2fs-dev] [PATCH] dump.f2fs: fix a wrong report for dump an {d, id, did}node

2018-03-06 Thread Sheng Yong
On 2018/3/7 11:30, heyunlei wrote: -Original Message- From: shengyong (A) Sent: Wednesday, March 07, 2018 11:21 AM To: heyunlei; jaeg...@kernel.org; Yuchao (T); linux-f2fs-devel@lists.sourceforge.net Subject: Re: [f2fs-dev] [PATCH] dump.f2fs: fix a wrong report for dump an {d, id,

Re: [f2fs-dev] [PATCH] dump.f2fs: fix a wrong report for dump an {d, id, did}node

2018-03-06 Thread heyunlei
>-Original Message- >From: shengyong (A) >Sent: Wednesday, March 07, 2018 11:21 AM >To: heyunlei; jaeg...@kernel.org; Yuchao (T); >linux-f2fs-devel@lists.sourceforge.net >Subject: Re: [f2fs-dev] [PATCH] dump.f2fs: fix a wrong report for dump an {d, >id, did}node > >Hi, Yunlei, > >On 201

Re: [f2fs-dev] [PATCH] dump.f2fs: fix a wrong report for dump an {d, id, did}node

2018-03-06 Thread Sheng Yong
Hi, Yunlei, On 2018/3/7 10:41, Yunlei He wrote: fix a wrong report for dump an {d,id,did}node like this: [print_node_info: 283] Node ID [0x6820:26656] is direct node or indirect node. [0] [0x 16b6684 : 23815812] [1] [0x 16b6685 : 23815813] [2]

[f2fs-dev] [PATCH] dump.f2fs: fix a wrong report for dump an {d, id, did}node

2018-03-06 Thread Yunlei He
fix a wrong report for dump an {d,id,did}node like this: [print_node_info: 283] Node ID [0x6820:26656] is direct node or indirect node. [0] [0x 16b6684 : 23815812] [1] [0x 16b6685 : 23815813] [2] [0x 16b6686 : 23815814] [3]

Re: [f2fs-dev] [RFC PATCH v3] f2fs: introduce F2FS_FEATURE_LOST_FOUND feature

2018-03-06 Thread Sheng Yong
Hi, Eric On 2018/3/7 3:38, Eric Biggers wrote: [+Cc linux-fscrypt] Hi Sheng, On Tue, Mar 06, 2018 at 11:39:04AM +0800, Sheng Yong wrote: This patch introduces a new feature, F2FS_FEATURE_LOST_FOUND, which is set by mkfs. It creates a directory named lost+found, which saves unreachable files.

[f2fs-dev] 信誉开票

2018-03-06 Thread 扬小姐
你好!本公司可以代理全国各地区增值税专用发票,普通增值税发票,点数优惠,真实有效验证后付款,需要联系:13670062475杨云(经理)微信同号:13670062475 信誉开票 诚信开票 长期合作愉快 -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.lin

Re: [f2fs-dev] [RFC PATCH v3] f2fs: introduce F2FS_FEATURE_LOST_FOUND feature

2018-03-06 Thread Eric Biggers via Linux-f2fs-devel
[+Cc linux-fscrypt] Hi Sheng, On Tue, Mar 06, 2018 at 11:39:04AM +0800, Sheng Yong wrote: > This patch introduces a new feature, F2FS_FEATURE_LOST_FOUND, which > is set by mkfs. It creates a directory named lost+found, which saves > unreachable files. If fsck finds a file which has no parent, or