From: Daeho Jeong
In a case writing without fallocate(), we can't guarantee it's allocated
in the conventional area for zoned stroage. To make it consistent across
storage devices, we disallow it regardless of storage device types.
Signed-off-by: Daeho Jeong
---
v2: covered the direct io case
On 2024/3/29 14:55, Wu Bo wrote:
Consider of a f2fs system with 2 devices:
Info: Device[0] : /dev/block/dm-46 blkaddr = 0--3f
Info: Device[1] : /dev/block/dm-47 blkaddr = 40--67f
f2fs_map_blocks will return logical addr of fs when doing buffered io:
f2fs_map_blocks: dev = (254,46),
This patch adds unset subcommand for pinfile command.
Usage: f2fs_io pinfile unset [target_file]
Signed-off-by: Chao Yu
---
man/f2fs_io.8 | 2 +-
tools/f2fs_io/f2fs_io.c | 11 +--
2 files changed, 10 insertions(+), 3 deletions(-)
diff --git a/man/f2fs_io.8 b/man/f2fs_io.8
Consider of a f2fs system with 2 devices:
Info: Device[0] : /dev/block/dm-46 blkaddr = 0--3f
Info: Device[1] : /dev/block/dm-47 blkaddr = 40--67f
f2fs_map_blocks will return logical addr of fs when doing buffered io:
f2fs_map_blocks: dev = (254,46), ino = 40020, file offset = 462865,
On 2024/3/27 4:31, Daeho Jeong wrote:
From: Daeho Jeong
In a case writing without fallocate(), we can't guarantee it's allocated
in the conventional area for zoned stroage. To make it consistent across
storage devices, we disallow it regardless of storage device types.
Signed-off-by: Daeho
On 2024/3/27 16:53, Zhiguo Niu wrote:
A length that exceeds the real size of the inode may be
specified from user, although these out-of-range areas
are not mapped, but they still need to be check in
while loop, which is unnecessary.
Signed-off-by: Zhiguo Niu
Reviewed-by: Chao Yu
Thanks,
