Hello,
I was looking at the source code for f2fs with regard to how dentries are
created and I have a question about how the __le32 hash_code is
calculated. If I have a file like /etc/fstab, would the hash be
f2fs_dentry_hash(/etc/fstab, 10) or f2fs_dentry_hash(fstab, 5) or
something completely
From: Huajun Li huajun...@intel.com
Normally we expect an empty partition after formatting by
mkfs.f2fs. But in this case, when we format a dirty partition and mount
it again. The former file will be recovered and available again! and
kernel log shows a recovery procedure is evoked.
This patch
Hi,
2013-11-03 (일), 15:34 +0200, Konstantin Dorfman:
Hello,
I'm working on [subj].
Particularly porting mkfs.f2fs and fsck.f2fs to android build environment.
Do you know about similar effort?
So far, I couldn't have heard about that.
Well, someone who are working on android may be
Hi,
2013-11-03 (일), 02:47 -0500, Zachary:
Hello,
I was looking at the source code for f2fs with regard to how dentries
are created and I have a question about how the __le32 hash_code is
calculated. If I have a file like /etc/fstab, would the hash be
f2fs_dentry_hash(/etc/fstab, 10) or
2013-11-03 (일), 23:08 +0800, Huajun Li:
From: Huajun Li huajun...@intel.com
Normally we expect an empty partition after formatting by
mkfs.f2fs. But in this case, when we format a dirty partition and mount
it again. The former file will be recovered and available again! and
kernel log shows
In wait_on_node_pages_writeback we will test and clear error flag for all pages
in radix tree, but not necessary.
So we only do this for pages belong to the specified inode.
Signed-off-by: Chao Yu chao2...@samsung.com
---
fs/f2fs/node.c |7 ---
1 file changed, 4 insertions(+), 3