inline_data after file shrink
Hi Chao,
[snip]
We can see that file still uses 16 Blocks
How do we deal with such situation?
Now, f2fs does not convert non-inline inode to inline one for these
potential
inodes with small size. So, once inline inode is converted
Hi Yunlei,
-Original Message-
From: He YunLei [mailto:heyun...@huawei.com]
Sent: Friday, May 29, 2015 1:05 PM
To: jaeg...@kernel.org
Cc: linux-fsde...@vger.kernel.org; linux-f2fs-devel@lists.sourceforge.net
Subject: [f2fs-dev] Not use inline_data after file shrink
Hi Jaegeuk
Hi Chao,
[snip]
We can see that file still uses 16 Blocks
How do we deal with such situation?
Now, f2fs does not convert non-inline inode to inline one for these potential
inodes with small size. So, once inline inode is converted, there is no
procedure to revert it.
it's
Hi Jaegeuk,
I found that when files(size MAX_INLINE_DATA) shrink(size MAX_INLINE_DATA),
inline_data option is not used in the file after narrow
I mount f2fs with inline_data as follow:
/dev/block/mmcblk0p40 /data f2fs
rw,nosuid,nodev,noatime,background_gc=on,discard,