Allow deduplication of the eof block when it is safe to do so
Subsystems (2)
cover Allow deduplication of the eof block when it is safe to do so
From: Filipe Manana <[email protected]>
Hi,
This short series allows deduplication of the last block of a file when the eof is not aligned to the sector size, as long as the range's end offset matches the eof of the destination file.
This is a safe case unlike the case where we attempt to clone the block in the middle of a file (which results in a corruption I found last year and affected both btrfs and xfs).
This is motivated by btrfs users reporting lower deduplication scores starting with kernel 5.0, which was the kernel release where btrfs was changed to use the generic VFS helper generic_remap_file_range_prep(). Users observed that the last block was no longer deduplicated when a file's size is not block size aligned. For btrfs this is specially important because references are kept per extent and not per block, so not having the last block deduplicated means the entire extent is kept allocated, making the deduplication not effective and often pointless in many cases.
Thanks.
Filipe Manana (2):
fs: allow deduplication of eof block into the end of the destination
file
Btrfs: make deduplication with range including the last block work
fs/btrfs/ioctl.c | 3 ++- fs/read_write.c | 10 ++++------ 2 files changed, 6 insertions(+), 7 deletions(-)
Signature · 1 line
2.11.0
PATCH 1/2 fs: allow deduplication of eof block into the end of the destination file
From: Filipe Manana <[email protected]>
We always round down, to a multiple of the filesystem's block size, the length to deduplicate at generic_remap_check_len(). However this is only needed if an attempt to deduplicate the last block into the middle of the destination file is requested, since that leads into a corruption if the length of the source file is not block size aligned. When an attempt to deduplicate the last block into the end of the destination file is requested, we should allow it because it is safe to do it - there's no stale data exposure and we are prepared to compare the data ranges for a length not aligned to the block (or page) size - in fact we even do the data compare before adjusting the deduplication length.
After btrfs was updated to use the generic helpers from VFS (by commit 34a28e3d77535e ("Btrfs: use generic_remap_file_range_prep() for cloning and deduplication")) we started to have user reports of deduplication not reflinking the last block anymore, and whence users getting lower deduplication scores. The main use case is deduplication of entire files that have a size not aligned to the block size of the filesystem.
We already allow cloning the last block to the end (and beyond) of the destination file, so allow for deduplication as well.
--- fs/read_write.c | 10 ++++------ 1 file changed, 4 insertions(+), 6 deletions(-)
fs/read_write.c +4 -6
@@ -1777,10 +1777,9 @@ static int remap_verify_area(struct file *file, loff_t pos, loff_t len,* else. Assume that the offsets have already been checked for block * alignment. * -* For deduplication we always scale down to the previous block because we -* can't meaningfully compare post-EOF contents. -* -* For clone we only link a partial EOF block above the destination file's EOF. +* For clone we only link a partial EOF block above or at the destination file's +* EOF. For deduplication we accept a partial EOF block only if it ends at the +* destination file's EOF (can not link it into the middle of a file). * * Shorten the request if possible. */
@@ -1796,8 +1795,7 @@ static int generic_remap_check_len(struct inode *inode_in,if ((*len & blkmask) ==0 )return 0 ; -if ((remap_flags &REMAP_FILE_DEDUP ) || - pos_out + *len <i_size_read (inode_out)) +if (pos_out + *len <i_size_read (inode_out)) new_len &= ~blkmask;if (new_len == *len)
Signature · 1 line
2.11.0
Re: [PATCH 1/2] fs: allow deduplication of eof block into the end of the destination file
Quoted 20 lines · On 12/16/19 1:26 PM, [email protected] wrote:
From: Filipe Manana <[email protected]>
We always round down, to a multiple of the filesystem's block size, the length to deduplicate at
generic_remap_check_len(). However this is only needed if an attempt to deduplicate the last block into the middle of the destination file is requested, since that leads into a corruption if the length of the source file is not block size aligned. When an attempt to deduplicate the last block into the end of the destination file is requested, we should allow it because it is safe to do it - there's no stale data exposure and we are prepared to compare the data ranges for a length not aligned to the block (or page) size - in fact we even do the data compare before adjusting the deduplication length.After btrfs was updated to use the generic helpers from VFS (by commit
34a28e3d77535e("Btrfs: usegeneric_remap_file_range_prep()for cloning and deduplication")) we started to have user reports of deduplication not reflinking the last block anymore, and whence users getting lower deduplication scores. The main use case is deduplication of entire files that have a size not aligned to the block size of the filesystem.
Quoted 5 lines
We already allow cloning the last block to the end (and beyond) of the destination file, so allow for deduplication as well.
Thanks,
Josef
Re: [PATCH 1/2] fs: allow deduplication of eof block into the end of the destination file
In reply to [email protected]Quoted 21 lines · On Mon, Dec 16, 2019 at 6:28 PM <[email protected]> wrote:
From: Filipe Manana <[email protected]>
We always round down, to a multiple of the filesystem's block size, the length to deduplicate at
generic_remap_check_len(). However this is only needed if an attempt to deduplicate the last block into the middle of the destination file is requested, since that leads into a corruption if the length of the source file is not block size aligned. When an attempt to deduplicate the last block into the end of the destination file is requested, we should allow it because it is safe to do it - there's no stale data exposure and we are prepared to compare the data ranges for a length not aligned to the block (or page) size - in fact we even do the data compare before adjusting the deduplication length.After btrfs was updated to use the generic helpers from VFS (by commit
34a28e3d77535e("Btrfs: usegeneric_remap_file_range_prep()for cloning and deduplication")) we started to have user reports of deduplication not reflinking the last block anymore, and whence users getting lower deduplication scores. The main use case is deduplication of entire files that have a size not aligned to the block size of the filesystem.
Quoted 5 lines
We already allow cloning the last block to the end (and beyond) of the destination file, so allow for deduplication as well.
Darrick, Al, any feedback?
Thanks.
Quoted 35 lines
--- fs/read_write.c | 10 ++++------ 1 file changed, 4 insertions(+), 6 deletions(-)fs/read_write.c +4
-7@@ -1777,10 +1777,9 @@ static int remap_verify_area(struct file *file, loff_t pos, loff_t len,* else. Assume that the offsets have already been checked for block * alignment. * -* For deduplication we always scale down to the previous block because we -* can't meaningfully compare post-EOF contents. -* -* For clone we only link a partial EOF block above the destination file's EOF. +* For clone we only link a partial EOF block above or at the destination file's +* EOF. For deduplication we accept a partial EOF block only if it ends at the +* destination file's EOF (can not link it into the middle of a file). * * Shorten the request if possible. */ @@ -1796,8 +1795,7 @@ static int generic_remap_check_len(struct inode *inode_in,if ((*len & blkmask) ==0 )return 0 ; -if ((remap_flags &REMAP_FILE_DEDUP ) || - pos_out + *len <i_size_read (inode_out)) +if (pos_out + *len <i_size_read (inode_out)) new_len &= ~blkmask;if (new_len == *len) --2.11.0
Re: [PATCH 1/2] fs: allow deduplication of eof block into the end of the destination file
Quoted 22 lines · Filipe Manana
Quoted 21 lines · On Mon, Dec 16, 2019 at 6:28 PM <[email protected]> wrote:
From: Filipe Manana <[email protected]>
We always round down, to a multiple of the filesystem's block size, the length to deduplicate at
generic_remap_check_len(). However this is only needed if an attempt to deduplicate the last block into the middle of the destination file is requested, since that leads into a corruption if the length of the source file is not block size aligned. When an attempt to deduplicate the last block into the end of the destination file is requested, we should allow it because it is safe to do it - there's no stale data exposure and we are prepared to compare the data ranges for a length not aligned to the block (or page) size - in fact we even do the data compare before adjusting the deduplication length.After btrfs was updated to use the generic helpers from VFS (by commit
34a28e3d77535e("Btrfs: usegeneric_remap_file_range_prep()for cloning and deduplication")) we started to have user reports of deduplication not reflinking the last block anymore, and whence users getting lower deduplication scores. The main use case is deduplication of entire files that have a size not aligned to the block size of the filesystem.
Quoted 7 lines
Quoted 5 lines
We already allow cloning the last block to the end (and beyond) of the destination file, so allow for deduplication as well.
Darrick, Al, any feedback?
Is there a fstest to check for correct operation of dedupe at or beyond source and destfile EOF? Particularly if one range is /not/ at EOF? And that an mmap read of the EOF block will see zeroes past EOF before and after the dedupe operation?
If I fallocate a 16k file, write 'X' into the first 5000 bytes, write 'X' into the first 66,440 bytes (60k + 5000) of a second file, and then try to dedupe (first file, 0-8k) with (second file, 60k-68k), should that work?
I'm convinced that we could support dedupe to EOF when the ranges of the two files both end at the respective file's EOF, but it's the weirder corner cases that I worry about...
--D
Quoted 37 lines
Thanks.
Quoted 35 lines
--- fs/read_write.c | 10 ++++------ 1 file changed, 4 insertions(+), 6 deletions(-)fs/read_write.c +4
-7@@ -1777,10 +1777,9 @@ static int remap_verify_area(struct file *file, loff_t pos, loff_t len,* else. Assume that the offsets have already been checked for block * alignment. * -* For deduplication we always scale down to the previous block because we -* can't meaningfully compare post-EOF contents. -* -* For clone we only link a partial EOF block above the destination file's EOF. +* For clone we only link a partial EOF block above or at the destination file's +* EOF. For deduplication we accept a partial EOF block only if it ends at the +* destination file's EOF (can not link it into the middle of a file). * * Shorten the request if possible. */ @@ -1796,8 +1795,7 @@ static int generic_remap_check_len(struct inode *inode_in,if ((*len & blkmask) ==0 )return 0 ; -if ((remap_flags &REMAP_FILE_DEDUP ) || - pos_out + *len <i_size_read (inode_out)) +if (pos_out + *len <i_size_read (inode_out)) new_len &= ~blkmask;if (new_len == *len) --2.11.0
Re: [PATCH 1/2] fs: allow deduplication of eof block into the end of the destination file
Quoted 27 lines · Darrick J. Wong
Quoted 25 lines · Filipe Manana
Quoted 24 lines · On Mon, Dec 16, 2019 at 6:28 PM <[email protected]> wrote:
From: Filipe Manana <[email protected]>
We always round down, to a multiple of the filesystem's block size, the length to deduplicate at
generic_remap_check_len(). However this is only needed if an attempt to deduplicate the last block into the middle of the destination file is requested, since that leads into a corruption if the length of the source file is not block size aligned. When an attempt to deduplicate the last block into the end of the destination file is requested, we should allow it because it is safe to do it - there's no stale data exposure and we are prepared to compare the data ranges for a length not aligned to the block (or page) size - in fact we even do the data compare before adjusting the deduplication length.After btrfs was updated to use the generic helpers from VFS (by commit
34a28e3d77535e("Btrfs: usegeneric_remap_file_range_prep()for cloning and deduplication")) we started to have user reports of deduplication not reflinking the last block anymore, and whence users getting lower deduplication scores. The main use case is deduplication of entire files that have a size not aligned to the block size of the filesystem.We already allow cloning the last block to the end (and beyond) of the destination file, so allow for deduplication as well.
Quoted 7 lines
Quoted 4 lines
Quoted 2 lines
Darrick, Al, any feedback?
Is there a fstest to check for correct operation of dedupe at or beyond source and destfile EOF? Particularly if one range is /not/ at EOF?
Such as what generic/158 does already?
Quoted 2 lines
And that an mmap read of the EOF block will see zeroes past EOF before and after the dedupe operation?
Can you elaborate a bit more? Why an mmap read and not a buffered or a direct IO read before and after deduplication?
Is there anything special for the mmap reads on xfs, is that your concern? Or is the idea to deduplicate while the file is mmap'ed?
Quoted 5 lines
If I fallocate a 16k file, write 'X' into the first 5000 bytes, write 'X' into the first 66,440 bytes (60k + 5000) of a second file, and then try to dedupe (first file, 0-8k) with (second file, 60k-68k), should that work?
You haven't mentioned the size of the second file, nor if the first file has a size of 16K which I assume (instead of fallocate with the keep size flag).
Anyway, I assume you actually meant to dedupe the range 0 - 5000 from the first file into the range 60k - 60k + 5000 of the second file, and that the second file has a size of 60k + 5000.
If so, that fails with -EINVAL because the source range is not block size aligned, and we already have generic fstests that test attempt to duplication and clone non-aligned ranges that don't end at eof. This patch doesn't change that behaviour, it only aims to allow deduplication of the eof block of the source file into the eof of the destination file.
Quoted 4 lines
I'm convinced that we could support dedupe to EOF when the ranges of the two files both end at the respective file's EOF, but it's the weirder corner cases that I worry about...
Well, we used to do that in btrfs before migrating to the generic code. Since I discovered the corruption due to deduplication of the eof block into the middle of a file in 2018's summer, the btrfs fix allowed deduplication of the eof block only if the destination end offset matched the eof of the destination file:
Since then no issues were found nor users reported any problems so far.
Any other specific test you would like to see?
Thanks.
Quoted 40 lines
--D
Quoted 37 lines
Thanks.
Quoted 35 lines
--- fs/read_write.c | 10 ++++------ 1 file changed, 4 insertions(+), 6 deletions(-)fs/read_write.c +4
-7@@ -1777,10 +1777,9 @@ static int remap_verify_area(struct file *file, loff_t pos, loff_t len,* else. Assume that the offsets have already been checked for block * alignment. * -* For deduplication we always scale down to the previous block because we -* can't meaningfully compare post-EOF contents. -* -* For clone we only link a partial EOF block above the destination file's EOF. +* For clone we only link a partial EOF block above or at the destination file's +* EOF. For deduplication we accept a partial EOF block only if it ends at the +* destination file's EOF (can not link it into the middle of a file). * * Shorten the request if possible. */ @@ -1796,8 +1795,7 @@ static int generic_remap_check_len(struct inode *inode_in,if ((*len & blkmask) ==0 )return 0 ; -if ((remap_flags &REMAP_FILE_DEDUP ) || - pos_out + *len <i_size_read (inode_out)) +if (pos_out + *len <i_size_read (inode_out)) new_len &= ~blkmask;if (new_len == *len) --2.11.0
Re: [PATCH 1/2] fs: allow deduplication of eof block into the end of the destination file
Quoted 31 lines · Filipe Manana
Quoted 30 lines · Darrick J. Wong
Quoted 28 lines · Filipe Manana
Quoted 26 lines · On Mon, Dec 16, 2019 at 6:28 PM <[email protected]> wrote:
From: Filipe Manana <[email protected]>
We always round down, to a multiple of the filesystem's block size, the length to deduplicate at
generic_remap_check_len(). However this is only needed if an attempt to deduplicate the last block into the middle of the destination file is requested, since that leads into a corruption if the length of the source file is not block size aligned. When an attempt to deduplicate the last block into the end of the destination file is requested, we should allow it because it is safe to do it - there's no stale data exposure and we are prepared to compare the data ranges for a length not aligned to the block (or page) size - in fact we even do the data compare before adjusting the deduplication length.After btrfs was updated to use the generic helpers from VFS (by commit
34a28e3d77535e("Btrfs: usegeneric_remap_file_range_prep()for cloning and deduplication")) we started to have user reports of deduplication not reflinking the last block anymore, and whence users getting lower deduplication scores. The main use case is deduplication of entire files that have a size not aligned to the block size of the filesystem.We already allow cloning the last block to the end (and beyond) of the destination file, so allow for deduplication as well.
Quoted 6 lines
Quoted 4 lines
Quoted 1 line
Darrick, Al, any feedback?
Is there a fstest to check for correct operation of dedupe at or beyond source and destfile EOF? Particularly if one range is /not/ at EOF?
Such as what generic/158 does already?
Urk, heh. :)
Quoted 7 lines
Quoted 2 lines
And that an mmap read of the EOF block will see zeroes past EOF before and after the dedupe operation?
Can you elaborate a bit more? Why an mmap read and not a buffered or a direct IO read before and after deduplication?
Is there anything special for the mmap reads on xfs, is that your concern? Or is the idea to deduplicate while the file is mmap'ed?
I cite mmap reads past EOF specifically because unlike buffered/direct reads where the VFS will stop reading exactly at EOF, a memory mapping maps in an entire memory page, and the fs is supposed to ensure that the bytes past EOF are zeroed.
Hm now that I look at g/158 it doesn't actually verify mmap reads. I looked around and can't really see anything that checks mmap reads before and after a dedupe operation at EOF.
Quoted 8 lines
Quoted 4 lines
If I fallocate a 16k file, write 'X' into the first 5000 bytes, write 'X' into the first 66,440 bytes (60k + 5000) of a second file, and then try to dedupe (first file, 0-8k) with (second file, 60k-68k), should that work?
You haven't mentioned the size of the second file, nor if the first file has a size of 16K which I assume (instead of fallocate with the keep size flag).
Er, sorry, yes. The first file is 16,384 bytes long; the second file is 66,440 bytes.
Quoted 3 lines
Anyway, I assume you actually meant to dedupe the range 0 - 5000 from the first file into the range 60k - 60k + 5000 of the second file, and that the second file has a size of 60k + 5000.
Nope, I meant to say to dedupe the range (offset: 0, length: 8192) from the first file into the second file (offset: 61440, length: 8192). The source range is entirely below EOF, and the dest range ends right at EOF in the second file.
Quoted 19 lines
If so, that fails with
-EINVALbecause the source range is not block size aligned, and we already have generic fstests that test attempt to duplication and clone non-aligned ranges that don't end at eof. This patch doesn't change that behaviour, it only aims to allow deduplication of the eof block of the source file into the eof of the destination file.Quoted 4 lines
I'm convinced that we could support dedupe to EOF when the ranges of the two files both end at the respective file's EOF, but it's the weirder corner cases that I worry about...
Well, we used to do that in btrfs before migrating to the generic code. Since I discovered the corruption due to deduplication of the eof block into the middle of a file in 2018's summer, the btrfs fix allowed deduplication of the eof block only if the destination end offset matched the eof of the destination file:
Quoted 3 lines
Since then no issues were found nor users reported any problems so far.
<nod> I'm ok with that one scenario, it's the "one range ends at eof, the other doesn't" case that I'm picking on. :)
(Another way to shut me up would be to run generic/52[12] with TIME_FACTOR=1000 (i.e. 1 billion fsx ops) and see what comes exploding out. :))
Quoted 1 line
Any other specific test you would like to see?
No, just that. And mmap reads. :)
--D
Quoted 42 lines
Thanks.
Quoted 40 lines
--D
Quoted 37 lines
Thanks.
Quoted 35 lines
--- fs/read_write.c | 10 ++++------ 1 file changed, 4 insertions(+), 6 deletions(-)fs/read_write.c +4
-7@@ -1777,10 +1777,9 @@ static int remap_verify_area(struct file *file, loff_t pos, loff_t len,* else. Assume that the offsets have already been checked for block * alignment. * -* For deduplication we always scale down to the previous block because we -* can't meaningfully compare post-EOF contents. -* -* For clone we only link a partial EOF block above the destination file's EOF. +* For clone we only link a partial EOF block above or at the destination file's +* EOF. For deduplication we accept a partial EOF block only if it ends at the +* destination file's EOF (can not link it into the middle of a file). * * Shorten the request if possible. */ @@ -1796,8 +1795,7 @@ static int generic_remap_check_len(struct inode *inode_in,if ((*len & blkmask) ==0 )return 0 ; -if ((remap_flags &REMAP_FILE_DEDUP ) || - pos_out + *len <i_size_read (inode_out)) +if (pos_out + *len <i_size_read (inode_out)) new_len &= ~blkmask;if (new_len == *len) --2.11.0
Re: [PATCH 1/2] fs: allow deduplication of eof block into the end of the destination file
Quoted 50 lines · Darrick J. Wong
Quoted 31 lines · Filipe Manana
Quoted 30 lines · Darrick J. Wong
Quoted 28 lines · Filipe Manana
Quoted 26 lines · On Mon, Dec 16, 2019 at 6:28 PM <[email protected]> wrote:
From: Filipe Manana <[email protected]>
We always round down, to a multiple of the filesystem's block size, the length to deduplicate at
generic_remap_check_len(). However this is only needed if an attempt to deduplicate the last block into the middle of the destination file is requested, since that leads into a corruption if the length of the source file is not block size aligned. When an attempt to deduplicate the last block into the end of the destination file is requested, we should allow it because it is safe to do it - there's no stale data exposure and we are prepared to compare the data ranges for a length not aligned to the block (or page) size - in fact we even do the data compare before adjusting the deduplication length.After btrfs was updated to use the generic helpers from VFS (by commit
34a28e3d77535e("Btrfs: usegeneric_remap_file_range_prep()for cloning and deduplication")) we started to have user reports of deduplication not reflinking the last block anymore, and whence users getting lower deduplication scores. The main use case is deduplication of entire files that have a size not aligned to the block size of the filesystem.We already allow cloning the last block to the end (and beyond) of the destination file, so allow for deduplication as well.
Quoted 6 lines
Quoted 4 lines
Quoted 1 line
Darrick, Al, any feedback?
Is there a fstest to check for correct operation of dedupe at or beyond source and destfile EOF? Particularly if one range is /not/ at EOF?
Such as what generic/158 does already?
Urk, heh. :)
Quoted 7 lines
Quoted 2 lines
And that an mmap read of the EOF block will see zeroes past EOF before and after the dedupe operation?
Can you elaborate a bit more? Why an mmap read and not a buffered or a direct IO read before and after deduplication?
Is there anything special for the mmap reads on xfs, is that your concern? Or is the idea to deduplicate while the file is mmap'ed?
Quoted 4 lines
I cite mmap reads past EOF specifically because unlike buffered/direct reads where the VFS will stop reading exactly at EOF, a memory mapping maps in an entire memory page, and the fs is supposed to ensure that the bytes past EOF are zeroed.
Ok, on btrfs we zero out the rest of the page both in for all reads.
So, it's not problem:
$ file_size=$((64 * 1024 + 500)) $ xfs_io -f -c "pwrite -S 0xba 0 $file_size" foo $ xfs_io -f -c "pwrite -S 0xba 0 $file_size" bar $ sync
$ xfs_io -c "mmap 0 68K" -c "mread -v 0 68K" -c "dedupe bar 0 0 $file_size" -c "mread -v 0 68K" foo
Both mreads returns exactly the same, eof is still the same and all bytes after it have a value of 0.
This is the same as it is for cloning.
Quoted 17 lines
Hm now that I look at g/158 it doesn't actually verify mmap reads. I looked around and can't really see anything that checks mmap reads before and after a dedupe operation at EOF.
Quoted 8 lines
Quoted 4 lines
If I fallocate a 16k file, write 'X' into the first 5000 bytes, write 'X' into the first 66,440 bytes (60k + 5000) of a second file, and then try to dedupe (first file, 0-8k) with (second file, 60k-68k), should that work?
You haven't mentioned the size of the second file, nor if the first file has a size of 16K which I assume (instead of fallocate with the keep size flag).
Er, sorry, yes. The first file is 16,384 bytes long; the second file is 66,440 bytes.
Quoted 8 lines
Quoted 3 lines
Anyway, I assume you actually meant to dedupe the range 0 - 5000 from the first file into the range 60k - 60k + 5000 of the second file, and that the second file has a size of 60k + 5000.
Nope, I meant to say to dedupe the range (offset: 0, length: 8192) from the first file into the second file (offset: 61440, length: 8192). The source range is entirely below EOF, and the dest range ends right at EOF in the second file.
The dedupe operations fails with -EINVAL, both before and after this patch, since the whenever one of ranges crosses eof, we must fail dedupe with -EINVAL. This happens at generic_remap_checks(), which called before generic_remap_check_len().
This is no different from the other existing tests in fstests, which cover this case already.
Quoted 22 lines
Quoted 22 lines
If so, that fails with
-EINVALbecause the source range is not block size aligned, and we already have generic fstests that test attempt to duplication and clone non-aligned ranges that don't end at eof. This patch doesn't change that behaviour, it only aims to allow deduplication of the eof block of the source file into the eof of the destination file.Quoted 4 lines
I'm convinced that we could support dedupe to EOF when the ranges of the two files both end at the respective file's EOF, but it's the weirder corner cases that I worry about...
Well, we used to do that in btrfs before migrating to the generic code. Since I discovered the corruption due to deduplication of the eof block into the middle of a file in 2018's summer, the btrfs fix allowed deduplication of the eof block only if the destination end offset matched the eof of the destination file:
Quoted 8 lines
Quoted 1 line
Since then no issues were found nor users reported any problems so far.
<nod> I'm ok with that one scenario, it's the "one range ends at eof, the other doesn't" case that I'm picking on. :)
(Another way to shut me up would be to run generic/52[12] with TIME_FACTOR=1000 (i.e. 1 billion fsx ops) and see what comes exploding out. :))
Well, it will take nearly 2 weeks to get those tests to complete with 1 billion ops, taking into
account each takes around 500 seconds to run here (on xfs) with 1 million operations...
Quoted 4 lines
Quoted 2 lines
Any other specific test you would like to see?
No, just that. And mmap reads. :)
Given that we allow cloning of eof into eof already (and that doesn't cause any known problems),
I don't see why you are so concerned with allowing dedupe to behave the same.
The only thing I can see it could be a problem would be comparing the contents of the last page beyond the eof position,
but as stated on the changelog, it's not a problem since we call vfs_dedupe_file_range_compare() before we
round down the length at generic_remap_check_len() - the data compare function already has the correct behaviour.
Thanks.
Quoted 45 lines
--D
Quoted 42 lines
Thanks.
Quoted 40 lines
--D
Quoted 37 lines
Thanks.
Quoted 35 lines
--- fs/read_write.c | 10 ++++------ 1 file changed, 4 insertions(+), 6 deletions(-)fs/read_write.c +4
-7@@ -1777,10 +1777,9 @@ static int remap_verify_area(struct file *file, loff_t pos, loff_t len,* else. Assume that the offsets have already been checked for block * alignment. * -* For deduplication we always scale down to the previous block because we -* can't meaningfully compare post-EOF contents. -* -* For clone we only link a partial EOF block above the destination file's EOF. +* For clone we only link a partial EOF block above or at the destination file's +* EOF. For deduplication we accept a partial EOF block only if it ends at the +* destination file's EOF (can not link it into the middle of a file). * * Shorten the request if possible. */ @@ -1796,8 +1795,7 @@ static int generic_remap_check_len(struct inode *inode_in,if ((*len & blkmask) ==0 )return 0 ; -if ((remap_flags &REMAP_FILE_DEDUP ) || - pos_out + *len <i_size_read (inode_out)) +if (pos_out + *len <i_size_read (inode_out)) new_len &= ~blkmask;if (new_len == *len) --2.11.0
Re: [PATCH 1/2] fs: allow deduplication of eof block into the end of the destination file
Quoted 65 lines · Filipe Manana
Quoted 50 lines · Darrick J. Wong
Quoted 31 lines · Filipe Manana
Quoted 30 lines · Darrick J. Wong
Quoted 28 lines · Filipe Manana
Quoted 26 lines · On Mon, Dec 16, 2019 at 6:28 PM <[email protected]> wrote:
From: Filipe Manana <[email protected]>
We always round down, to a multiple of the filesystem's block size, the length to deduplicate at
generic_remap_check_len(). However this is only needed if an attempt to deduplicate the last block into the middle of the destination file is requested, since that leads into a corruption if the length of the source file is not block size aligned. When an attempt to deduplicate the last block into the end of the destination file is requested, we should allow it because it is safe to do it - there's no stale data exposure and we are prepared to compare the data ranges for a length not aligned to the block (or page) size - in fact we even do the data compare before adjusting the deduplication length.After btrfs was updated to use the generic helpers from VFS (by commit
34a28e3d77535e("Btrfs: usegeneric_remap_file_range_prep()for cloning and deduplication")) we started to have user reports of deduplication not reflinking the last block anymore, and whence users getting lower deduplication scores. The main use case is deduplication of entire files that have a size not aligned to the block size of the filesystem.We already allow cloning the last block to the end (and beyond) of the destination file, so allow for deduplication as well.
Quoted 6 lines
Quoted 4 lines
Quoted 1 line
Darrick, Al, any feedback?
Is there a fstest to check for correct operation of dedupe at or beyond source and destfile EOF? Particularly if one range is /not/ at EOF?
Such as what generic/158 does already?
Urk, heh. :)
Quoted 7 lines
Quoted 2 lines
And that an mmap read of the EOF block will see zeroes past EOF before and after the dedupe operation?
Can you elaborate a bit more? Why an mmap read and not a buffered or a direct IO read before and after deduplication?
Is there anything special for the mmap reads on xfs, is that your concern? Or is the idea to deduplicate while the file is mmap'ed?Quoted 4 lines
I cite mmap reads past EOF specifically because unlike buffered/direct reads where the VFS will stop reading exactly at EOF, a memory mapping maps in an entire memory page, and the fs is supposed to ensure that the bytes past EOF are zeroed.
Ok, on btrfs we zero out the rest of the page both in for all reads.
So, it's not problem:
$ file_size=$((64 * 1024 + 500)) $ xfs_io -f -c "pwrite -S 0xba 0 $file_size" foo $ xfs_io -f -c "pwrite -S 0xba 0 $file_size" bar $ sync
Quoted 7 lines
$ xfs_io -c "mmap 0 68K" -c "mread -v 0 68K" -c "dedupe bar 0 0 $file_size" -c "mread -v 0 68K" fooBoth mreads returns exactly the same, eof is still the same and all bytes after it have a value of 0.
This is the same as it is for cloning.
Oh good. :)
Quoted 26 lines
Quoted 17 lines
Hm now that I look at g/158 it doesn't actually verify mmap reads. I looked around and can't really see anything that checks mmap reads before and after a dedupe operation at EOF.
Quoted 8 lines
Quoted 4 lines
If I fallocate a 16k file, write 'X' into the first 5000 bytes, write 'X' into the first 66,440 bytes (60k + 5000) of a second file, and then try to dedupe (first file, 0-8k) with (second file, 60k-68k), should that work?
You haven't mentioned the size of the second file, nor if the first file has a size of 16K which I assume (instead of fallocate with the keep size flag).
Er, sorry, yes. The first file is 16,384 bytes long; the second file is 66,440 bytes.
Quoted 8 lines
Quoted 3 lines
Anyway, I assume you actually meant to dedupe the range 0 - 5000 from the first file into the range 60k - 60k + 5000 of the second file, and that the second file has a size of 60k + 5000.
Nope, I meant to say to dedupe the range (offset: 0, length: 8192) from the first file into the second file (offset: 61440, length: 8192). The source range is entirely below EOF, and the dest range ends right at EOF in the second file.
Quoted 7 lines
The dedupe operations fails with
-EINVAL, both before and after this patch, since the whenever one of ranges crosses eof, we must fail dedupe with-EINVAL. This happens atgeneric_remap_checks(), which called beforegeneric_remap_check_len().This is no different from the other existing tests in fstests, which cover this case already.
Ah, ok.
Quoted 26 lines
Quoted 26 lines
Quoted 19 lines
If so, that fails with
-EINVALbecause the source range is not block size aligned, and we already have generic fstests that test attempt to duplication and clone non-aligned ranges that don't end at eof. This patch doesn't change that behaviour, it only aims to allow deduplication of the eof block of the source file into the eof of the destination file.Quoted 4 lines
I'm convinced that we could support dedupe to EOF when the ranges of the two files both end at the respective file's EOF, but it's the weirder corner cases that I worry about...
Well, we used to do that in btrfs before migrating to the generic code. Since I discovered the corruption due to deduplication of the eof block into the middle of a file in 2018's summer, the btrfs fix allowed deduplication of the eof block only if the destination end offset matched the eof of the destination file:
Quoted 3 lines
Since then no issues were found nor users reported any problems so far.
<nod> I'm ok with that one scenario, it's the "one range ends at eof, the other doesn't" case that I'm picking on. :)
Quoted 8 lines
Quoted 3 lines
(Another way to shut me up would be to run generic/52[12] with TIME_FACTOR=1000 (i.e. 1 billion fsx ops) and see what comes exploding out. :))
Well, it will take nearly 2 weeks to get those tests to complete with 1 billion ops, taking into
account each takes around 500 seconds to run here (on xfs) with 1 million operations...
I know. I probably should have clarified: every month or two I build a kernel from tip, throw it in a VM, and let it run for however long it goes until it dies, fixing whatever problems as I find them.
*So far* no billionaire plutocrats have complained about the huge compute bills that are probably racking up. ;)
(FWIW I also tossed your patch onto another one of these VMs and it hasn't died yet, so that's probably an ok sign)
Quoted 9 lines
Quoted 4 lines
Quoted 2 lines
Any other specific test you would like to see?
No, just that. And mmap reads. :)
Given that we allow cloning of eof into eof already (and that doesn't cause any known problems),
I don't see why you are so concerned with allowing dedupe to behave the same.
Quoted 6 lines
The only thing I can see it could be a problem would be comparing the contents of the last page beyond the eof position,
but as stated on the changelog, it's not a problem since we callvfs_dedupe_file_range_compare()before we
round down the length atgeneric_remap_check_len()- the data compare function already has the correct behaviour.
<nod>
--D
Quoted 47 lines
Thanks.
Quoted 45 lines
--D
Quoted 42 lines
Thanks.
Quoted 40 lines
--D
Quoted 37 lines
Thanks.
Quoted 35 lines
--- fs/read_write.c | 10 ++++------ 1 file changed, 4 insertions(+), 6 deletions(-)fs/read_write.c +4
-7@@ -1777,10 +1777,9 @@ static int remap_verify_area(struct file *file, loff_t pos, loff_t len,* else. Assume that the offsets have already been checked for block * alignment. * -* For deduplication we always scale down to the previous block because we -* can't meaningfully compare post-EOF contents. -* -* For clone we only link a partial EOF block above the destination file's EOF. +* For clone we only link a partial EOF block above or at the destination file's +* EOF. For deduplication we accept a partial EOF block only if it ends at the +* destination file's EOF (can not link it into the middle of a file). * * Shorten the request if possible. */ @@ -1796,8 +1795,7 @@ static int generic_remap_check_len(struct inode *inode_in,if ((*len & blkmask) ==0 )return 0 ; -if ((remap_flags &REMAP_FILE_DEDUP ) || - pos_out + *len <i_size_read (inode_out)) +if (pos_out + *len <i_size_read (inode_out)) new_len &= ~blkmask;if (new_len == *len) --2.11.0
Re: [PATCH 1/2] fs: allow deduplication of eof block into the end of the destination file
Quoted 152 lines · Darrick J. Wong
Quoted 65 lines · Filipe Manana
Quoted 50 lines · Darrick J. Wong
Quoted 31 lines · Filipe Manana
Quoted 30 lines · Darrick J. Wong
Quoted 28 lines · Filipe Manana
Quoted 26 lines · On Mon, Dec 16, 2019 at 6:28 PM <[email protected]> wrote:
From: Filipe Manana <[email protected]>
We always round down, to a multiple of the filesystem's block size, the length to deduplicate at
generic_remap_check_len(). However this is only needed if an attempt to deduplicate the last block into the middle of the destination file is requested, since that leads into a corruption if the length of the source file is not block size aligned. When an attempt to deduplicate the last block into the end of the destination file is requested, we should allow it because it is safe to do it - there's no stale data exposure and we are prepared to compare the data ranges for a length not aligned to the block (or page) size - in fact we even do the data compare before adjusting the deduplication length.After btrfs was updated to use the generic helpers from VFS (by commit
34a28e3d77535e("Btrfs: usegeneric_remap_file_range_prep()for cloning and deduplication")) we started to have user reports of deduplication not reflinking the last block anymore, and whence users getting lower deduplication scores. The main use case is deduplication of entire files that have a size not aligned to the block size of the filesystem.We already allow cloning the last block to the end (and beyond) of the destination file, so allow for deduplication as well.
Quoted 6 lines
Quoted 4 lines
Quoted 1 line
Darrick, Al, any feedback?
Is there a fstest to check for correct operation of dedupe at or beyond source and destfile EOF? Particularly if one range is /not/ at EOF?
Such as what generic/158 does already?
Urk, heh. :)
Quoted 7 lines
Quoted 2 lines
And that an mmap read of the EOF block will see zeroes past EOF before and after the dedupe operation?
Can you elaborate a bit more? Why an mmap read and not a buffered or a direct IO read before and after deduplication?
Is there anything special for the mmap reads on xfs, is that your concern? Or is the idea to deduplicate while the file is mmap'ed?Quoted 4 lines
I cite mmap reads past EOF specifically because unlike buffered/direct reads where the VFS will stop reading exactly at EOF, a memory mapping maps in an entire memory page, and the fs is supposed to ensure that the bytes past EOF are zeroed.
Ok, on btrfs we zero out the rest of the page both in for all reads.
So, it's not problem:
$ file_size=$((64 * 1024 + 500)) $ xfs_io -f -c "pwrite -S 0xba 0 $file_size" foo $ xfs_io -f -c "pwrite -S 0xba 0 $file_size" bar $ syncQuoted 7 lines
$ xfs_io -c "mmap 0 68K" -c "mread -v 0 68K" -c "dedupe bar 0 0 $file_size" -c "mread -v 0 68K" fooBoth mreads returns exactly the same, eof is still the same and all bytes after it have a value of 0.
This is the same as it is for cloning.
Oh good. :)
Quoted 26 lines
Quoted 17 lines
Hm now that I look at g/158 it doesn't actually verify mmap reads. I looked around and can't really see anything that checks mmap reads before and after a dedupe operation at EOF.
Quoted 8 lines
Quoted 4 lines
If I fallocate a 16k file, write 'X' into the first 5000 bytes, write 'X' into the first 66,440 bytes (60k + 5000) of a second file, and then try to dedupe (first file, 0-8k) with (second file, 60k-68k), should that work?
You haven't mentioned the size of the second file, nor if the first file has a size of 16K which I assume (instead of fallocate with the keep size flag).
Er, sorry, yes. The first file is 16,384 bytes long; the second file is 66,440 bytes.
Quoted 8 lines
Quoted 3 lines
Anyway, I assume you actually meant to dedupe the range 0 - 5000 from the first file into the range 60k - 60k + 5000 of the second file, and that the second file has a size of 60k + 5000.
Nope, I meant to say to dedupe the range (offset: 0, length: 8192) from the first file into the second file (offset: 61440, length: 8192). The source range is entirely below EOF, and the dest range ends right at EOF in the second file.
Quoted 7 lines
The dedupe operations fails with
-EINVAL, both before and after this patch, since the whenever one of ranges crosses eof, we must fail dedupe with-EINVAL. This happens atgeneric_remap_checks(), which called beforegeneric_remap_check_len().This is no different from the other existing tests in fstests, which cover this case already.
Ah, ok.
Quoted 26 lines
Quoted 26 lines
Quoted 19 lines
If so, that fails with
-EINVALbecause the source range is not block size aligned, and we already have generic fstests that test attempt to duplication and clone non-aligned ranges that don't end at eof. This patch doesn't change that behaviour, it only aims to allow deduplication of the eof block of the source file into the eof of the destination file.Quoted 4 lines
I'm convinced that we could support dedupe to EOF when the ranges of the two files both end at the respective file's EOF, but it's the weirder corner cases that I worry about...
Well, we used to do that in btrfs before migrating to the generic code. Since I discovered the corruption due to deduplication of the eof block into the middle of a file in 2018's summer, the btrfs fix allowed deduplication of the eof block only if the destination end offset matched the eof of the destination file:
Quoted 3 lines
Since then no issues were found nor users reported any problems so far.
<nod> I'm ok with that one scenario, it's the "one range ends at eof, the other doesn't" case that I'm picking on. :)
Quoted 8 lines
Quoted 3 lines
(Another way to shut me up would be to run generic/52[12] with TIME_FACTOR=1000 (i.e. 1 billion fsx ops) and see what comes exploding out. :))
Well, it will take nearly 2 weeks to get those tests to complete with 1 billion ops, taking into
account each takes around 500 seconds to run here (on xfs) with 1 million operations...I know. I probably should have clarified: every month or two I build a kernel from tip, throw it in a VM, and let it run for however long it goes until it dies, fixing whatever problems as I find them.
Quoted 5 lines
*So far* no billionaire plutocrats have complained about the huge compute bills that are probably racking up. ;)
(FWIW I also tossed your patch onto another one of these VMs and it hasn't died yet, so that's probably an ok sign)
For 100 million ops, on 5.5-rc5 kernel with this patchset and on xfs:
$ TIME_FACTOR=100 MKFS_OPTIONS="-m reflink=1,rmapbt=1" ./check generic/521 generic/522 FSTYP -- xfs (debug) PLATFORM -- Linux/x86_64 debian5 5.5.0-rc5-btrfs-next-67 #1 SMP PREEMPT Thu Jan 9 13:48:07 WET 2020 MKFS_OPTIONS -- -f -m reflink=1,rmapbt=1 /dev/sdc MOUNT_OPTIONS -- /dev/sdc /home/fdmanana/btrfs-tests/scratch_1
generic/521 482s ... 48961s
generic/522 536s ... 54432s
Ran: generic/521 generic/522
Passed all 2 tests
Similar for btrfs, no problems found (yet at least).
Thanks.
Quoted 68 lines
Quoted 10 lines
Quoted 5 lines
Quoted 3 lines
Any other specific test you would like to see?
No, just that. And mmap reads. :)
Given that we allow cloning of eof into eof already (and that doesn't cause any known problems),
I don't see why you are so concerned with allowing dedupe to behave the same.Quoted 6 lines
The only thing I can see it could be a problem would be comparing the contents of the last page beyond the eof position,
but as stated on the changelog, it's not a problem since we callvfs_dedupe_file_range_compare()before we
round down the length atgeneric_remap_check_len()- the data compare function already has the correct behaviour.<nod>
--D
Quoted 47 lines
Thanks.
Quoted 45 lines
--D
Quoted 42 lines
Thanks.
Quoted 40 lines
--D
Quoted 37 lines
Thanks.
Quoted 35 lines
--- fs/read_write.c | 10 ++++------ 1 file changed, 4 insertions(+), 6 deletions(-)fs/read_write.c +4
-7@@ -1777,10 +1777,9 @@ static int remap_verify_area(struct file *file, loff_t pos, loff_t len,* else. Assume that the offsets have already been checked for block * alignment. * -* For deduplication we always scale down to the previous block because we -* can't meaningfully compare post-EOF contents. -* -* For clone we only link a partial EOF block above the destination file's EOF. +* For clone we only link a partial EOF block above or at the destination file's +* EOF. For deduplication we accept a partial EOF block only if it ends at the +* destination file's EOF (can not link it into the middle of a file). * * Shorten the request if possible. */ @@ -1796,8 +1795,7 @@ static int generic_remap_check_len(struct inode *inode_in,if ((*len & blkmask) ==0 )return 0 ; -if ((remap_flags &REMAP_FILE_DEDUP ) || - pos_out + *len <i_size_read (inode_out)) +if (pos_out + *len <i_size_read (inode_out)) new_len &= ~blkmask;if (new_len == *len) --2.11.0
Darrick J. Wong
Reviewed-byRe: [PATCH 1/2] fs: allow deduplication of eof block into the end of the destination file
Quoted 169 lines · Filipe Manana
Quoted 152 lines · Darrick J. Wong
Quoted 65 lines · Filipe Manana
Quoted 50 lines · Darrick J. Wong
Quoted 31 lines · Filipe Manana
Quoted 30 lines · Darrick J. Wong
Quoted 28 lines · Filipe Manana
Quoted 26 lines · On Mon, Dec 16, 2019 at 6:28 PM <[email protected]> wrote:
From: Filipe Manana <[email protected]>
We always round down, to a multiple of the filesystem's block size, the length to deduplicate at
generic_remap_check_len(). However this is only needed if an attempt to deduplicate the last block into the middle of the destination file is requested, since that leads into a corruption if the length of the source file is not block size aligned. When an attempt to deduplicate the last block into the end of the destination file is requested, we should allow it because it is safe to do it - there's no stale data exposure and we are prepared to compare the data ranges for a length not aligned to the block (or page) size - in fact we even do the data compare before adjusting the deduplication length.After btrfs was updated to use the generic helpers from VFS (by commit
34a28e3d77535e("Btrfs: usegeneric_remap_file_range_prep()for cloning and deduplication")) we started to have user reports of deduplication not reflinking the last block anymore, and whence users getting lower deduplication scores. The main use case is deduplication of entire files that have a size not aligned to the block size of the filesystem.We already allow cloning the last block to the end (and beyond) of the destination file, so allow for deduplication as well.
Quoted 6 lines
Quoted 4 lines
Quoted 1 line
Darrick, Al, any feedback?
Is there a fstest to check for correct operation of dedupe at or beyond source and destfile EOF? Particularly if one range is /not/ at EOF?
Such as what generic/158 does already?
Urk, heh. :)
Quoted 7 lines
Quoted 2 lines
And that an mmap read of the EOF block will see zeroes past EOF before and after the dedupe operation?
Can you elaborate a bit more? Why an mmap read and not a buffered or a direct IO read before and after deduplication?
Is there anything special for the mmap reads on xfs, is that your concern? Or is the idea to deduplicate while the file is mmap'ed?Quoted 4 lines
I cite mmap reads past EOF specifically because unlike buffered/direct reads where the VFS will stop reading exactly at EOF, a memory mapping maps in an entire memory page, and the fs is supposed to ensure that the bytes past EOF are zeroed.
Ok, on btrfs we zero out the rest of the page both in for all reads.
So, it's not problem:
$ file_size=$((64 * 1024 + 500)) $ xfs_io -f -c "pwrite -S 0xba 0 $file_size" foo $ xfs_io -f -c "pwrite -S 0xba 0 $file_size" bar $ syncQuoted 7 lines
$ xfs_io -c "mmap 0 68K" -c "mread -v 0 68K" -c "dedupe bar 0 0 $file_size" -c "mread -v 0 68K" fooBoth mreads returns exactly the same, eof is still the same and all bytes after it have a value of 0.
This is the same as it is for cloning.
Oh good. :)
Quoted 26 lines
Quoted 17 lines
Hm now that I look at g/158 it doesn't actually verify mmap reads. I looked around and can't really see anything that checks mmap reads before and after a dedupe operation at EOF.
Quoted 8 lines
Quoted 4 lines
If I fallocate a 16k file, write 'X' into the first 5000 bytes, write 'X' into the first 66,440 bytes (60k + 5000) of a second file, and then try to dedupe (first file, 0-8k) with (second file, 60k-68k), should that work?
You haven't mentioned the size of the second file, nor if the first file has a size of 16K which I assume (instead of fallocate with the keep size flag).
Er, sorry, yes. The first file is 16,384 bytes long; the second file is 66,440 bytes.
Quoted 8 lines
Quoted 3 lines
Anyway, I assume you actually meant to dedupe the range 0 - 5000 from the first file into the range 60k - 60k + 5000 of the second file, and that the second file has a size of 60k + 5000.
Nope, I meant to say to dedupe the range (offset: 0, length: 8192) from the first file into the second file (offset: 61440, length: 8192). The source range is entirely below EOF, and the dest range ends right at EOF in the second file.
Quoted 7 lines
The dedupe operations fails with
-EINVAL, both before and after this patch, since the whenever one of ranges crosses eof, we must fail dedupe with-EINVAL. This happens atgeneric_remap_checks(), which called beforegeneric_remap_check_len().This is no different from the other existing tests in fstests, which cover this case already.
Ah, ok.
Quoted 26 lines
Quoted 26 lines
Quoted 19 lines
If so, that fails with
-EINVALbecause the source range is not block size aligned, and we already have generic fstests that test attempt to duplication and clone non-aligned ranges that don't end at eof. This patch doesn't change that behaviour, it only aims to allow deduplication of the eof block of the source file into the eof of the destination file.Quoted 4 lines
I'm convinced that we could support dedupe to EOF when the ranges of the two files both end at the respective file's EOF, but it's the weirder corner cases that I worry about...
Well, we used to do that in btrfs before migrating to the generic code. Since I discovered the corruption due to deduplication of the eof block into the middle of a file in 2018's summer, the btrfs fix allowed deduplication of the eof block only if the destination end offset matched the eof of the destination file:
Quoted 3 lines
Since then no issues were found nor users reported any problems so far.
<nod> I'm ok with that one scenario, it's the "one range ends at eof, the other doesn't" case that I'm picking on. :)
Quoted 8 lines
Quoted 3 lines
(Another way to shut me up would be to run generic/52[12] with TIME_FACTOR=1000 (i.e. 1 billion fsx ops) and see what comes exploding out. :))
Well, it will take nearly 2 weeks to get those tests to complete with 1 billion ops, taking into
account each takes around 500 seconds to run here (on xfs) with 1 million operations...I know. I probably should have clarified: every month or two I build a kernel from tip, throw it in a VM, and let it run for however long it goes until it dies, fixing whatever problems as I find them.
Quoted 5 lines
*So far* no billionaire plutocrats have complained about the huge compute bills that are probably racking up. ;)
(FWIW I also tossed your patch onto another one of these VMs and it hasn't died yet, so that's probably an ok sign)
For 100 million ops, on 5.5-rc5 kernel with this patchset and on xfs:
$ TIME_FACTOR=100 MKFS_OPTIONS="-m reflink=1,rmapbt=1" ./check generic/521 generic/522 FSTYP -- xfs (debug) PLATFORM -- Linux/x86_64 debian5 5.5.0-rc5-btrfs-next-67 #1 SMP PREEMPT Thu Jan 9 13:48:07 WET 2020 MKFS_OPTIONS -- -f -m reflink=1,rmapbt=1 /dev/sdc MOUNT_OPTIONS -- /dev/sdc /home/fdmanana/btrfs-tests/scratch_1
Quoted 9 lines
generic/521 482s ... 48961s
generic/522 536s ... 54432s
Ran: generic/521 generic/522
Passed all 2 testsSimilar for btrfs, no problems found (yet at least).
Thanks.
Urk, I never reviewed this, did I...
--D
Quoted 68 lines
Quoted 68 lines
Quoted 10 lines
Quoted 5 lines
Quoted 3 lines
Any other specific test you would like to see?
No, just that. And mmap reads. :)
Given that we allow cloning of eof into eof already (and that doesn't cause any known problems),
I don't see why you are so concerned with allowing dedupe to behave the same.Quoted 6 lines
The only thing I can see it could be a problem would be comparing the contents of the last page beyond the eof position,
but as stated on the changelog, it's not a problem since we callvfs_dedupe_file_range_compare()before we
round down the length atgeneric_remap_check_len()- the data compare function already has the correct behaviour.<nod>
--D
Quoted 47 lines
Thanks.
Quoted 45 lines
--D
Quoted 42 lines
Thanks.
Quoted 40 lines
--D
Quoted 37 lines
Thanks.
Quoted 35 lines
--- fs/read_write.c | 10 ++++------ 1 file changed, 4 insertions(+), 6 deletions(-)fs/read_write.c +4
-7@@ -1777,10 +1777,9 @@ static int remap_verify_area(struct file *file, loff_t pos, loff_t len,* else. Assume that the offsets have already been checked for block * alignment. * -* For deduplication we always scale down to the previous block because we -* can't meaningfully compare post-EOF contents. -* -* For clone we only link a partial EOF block above the destination file's EOF. +* For clone we only link a partial EOF block above or at the destination file's +* EOF. For deduplication we accept a partial EOF block only if it ends at the +* destination file's EOF (can not link it into the middle of a file). * * Shorten the request if possible. */ @@ -1796,8 +1795,7 @@ static int generic_remap_check_len(struct inode *inode_in,if ((*len & blkmask) ==0 )return 0 ; -if ((remap_flags &REMAP_FILE_DEDUP ) || - pos_out + *len <i_size_read (inode_out)) +if (pos_out + *len <i_size_read (inode_out)) new_len &= ~blkmask;if (new_len == *len) --2.11.0
Re: [PATCH 1/2] fs: allow deduplication of eof block into the end of the destination file
Quoted 3 lines · Darrick J. Wong
Urk, I never reviewed this, did I...
Reviewed-by Darrick J. Wong <[email protected]>
Thanks, so with this we can proceed with merging, the question is how. This is in generic fs/ code but not plain VFS and affecting only btrfs and xfs. I suggest the following:
I'll take the patches to a branch separate from other btrfs patches, add rev-by and stable tags and send an extra pull request to Linus.
Before that the branch can spend some time in btrfs' for-next among other topic branches so there's linux-next exposure.
I don't mean to sidestep VFS maintainers, but previous remap changes don't have Al Viro's signed-off either, so I hope that when at least Darrick is fine with the proposed way then let's do it. If not, please let me know.
PATCH 2/2 Btrfs: make deduplication with range including the last block work
In reply to [email protected]From: Filipe Manana <[email protected]>
Since btrfs was migrated to use the generic VFS helpers for clone and deduplication, it stopped allowing for the last block of a file to be deduplicated when the source file size is not sector size aligned (when eof is somewhere in the middle of the last block). There are two reasons for that:
1) The generic code always rounds down, to a multiple of the block size, the range's length for deduplications. This means we end up never deduplicating the last block when the eof is not block size aligned, even for the safe case where the destination range's end offset matches the destination file's size. That rounding down operation is done at generic_remap_check_len();
2) Because of that, the btrfs specific code does not expect anymore any non-aligned range length's for deduplication and therefore does not work if such nona-aligned length is given.
This patch addresses that second part, and it depends on a patch that fixes generic_remap_check_len(), in the VFS, which was submitted ealier and has the following subject:
"fs: allow deduplication of eof block into the end of the destination file"
These two patches address reports from users that started seeing lower deduplication rates due to the last block never being deduplicated when the file size is not aligned to the filesystem's block size.
--- fs/btrfs/ioctl.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-)
fs/btrfs/ioctl.c +2 -1
@@ -3237,6 +3237,7 @@ static void btrfs_double_extent_lock(struct inode *inode1, u64 loff1,static int btrfs_extent_same_range (struct inode *src,u64 loff,u64 len,struct inode *dst,u64 dst_loff) { +const u64 bs =BTRFS_I (src)->root->fs_info->sb->s_blocksize;int ret;/*
@@ -3244,7 +3245,7 @@ static int btrfs_extent_same_range(struct inode *src, u64 loff, u64 len,* source range to serialize with relocation. */ btrfs_double_extent_lock (src, loff, dst, dst_loff, len); - ret =btrfs_clone (src, dst, loff, len, len, dst_loff,1 ); + ret =btrfs_clone (src, dst, loff, len,ALIGN (len, bs), dst_loff,1 );btrfs_double_extent_unlock (src, loff, dst, dst_loff, len);return ret;
Signature · 1 line
2.11.0
Re: [PATCH 2/2] Btrfs: make deduplication with range including the last block work
Quoted 15 lines · On 12/16/19 1:26 PM, [email protected] wrote:
From: Filipe Manana <[email protected]>
Since btrfs was migrated to use the generic VFS helpers for clone and deduplication, it stopped allowing for the last block of a file to be deduplicated when the source file size is not sector size aligned (when eof is somewhere in the middle of the last block). There are two reasons for that:
1) The generic code always rounds down, to a multiple of the block size, the range's length for deduplications. This means we end up never deduplicating the last block when the eof is not block size aligned, even for the safe case where the destination range's end offset matches the destination file's size. That rounding down operation is done at
generic_remap_check_len();
Quoted 4 lines
2) Because of that, the btrfs specific code does not expect anymore any non-aligned range length's for deduplication and therefore does not work if such nona-aligned length is given.
Does anybody else rely on this behavior that needs a change like this for their fs?
Quoted 4 lines
This patch addresses that second part, and it depends on a patch that fixes
generic_remap_check_len(), in the VFS, which was submitted ealier and has the following subject:
Quoted 8 lines
"fs: allow deduplication of eof block into the end of the destination file"
These two patches address reports from users that started seeing lower deduplication rates due to the last block never being deduplicated when the file size is not aligned to the filesystem's block size.
Thanks,
Josef
Re: [PATCH 2/2] Btrfs: make deduplication with range including the last block work
In reply to [email protected]Quoted 23 lines · On Mon, Dec 16, 2019 at 06:26:56PM +0000, [email protected] wrote:
From: Filipe Manana <[email protected]>
Since btrfs was migrated to use the generic VFS helpers for clone and deduplication, it stopped allowing for the last block of a file to be deduplicated when the source file size is not sector size aligned (when eof is somewhere in the middle of the last block). There are two reasons for that:
1) The generic code always rounds down, to a multiple of the block size, the range's length for deduplications. This means we end up never deduplicating the last block when the eof is not block size aligned, even for the safe case where the destination range's end offset matches the destination file's size. That rounding down operation is done at
generic_remap_check_len();2) Because of that, the btrfs specific code does not expect anymore any non-aligned range length's for deduplication and therefore does not work if such nona-aligned length is given.
This patch addresses that second part, and it depends on a patch that fixes
generic_remap_check_len(), in the VFS, which was submitted ealier and has the following subject:
Quoted 8 lines
"fs: allow deduplication of eof block into the end of the destination file"
These two patches address reports from users that started seeing lower deduplication rates due to the last block never being deduplicated when the file size is not aligned to the filesystem's block size.
Should these patches be marked for stable (5.0+, but see below for caveats about 5.0)? The bug affects 5.3 and 5.4 which are still active, and dedupe is an important feature for some users.
Quoted 17 lines
--- fs/btrfs/ioctl.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-)fs/btrfs/ioctl.c +1
-0@@ -3237,6 +3237,7 @@ static void btrfs_double_extent_lock(struct inode *inode1, u64 loff1,static int btrfs_extent_same_range (struct inode *src,u64 loff,u64 len,struct inode *dst,u64 dst_loff) { +const u64 bs =BTRFS_I (src)->root->fs_info->sb->s_blocksize;int ret;/*
fs/btrfs/ioctl.c static int btrfs_extent_same_range(struct inode *src, u64 loff, u64 len, · line 3248
Quoted 5 lines
fs/btrfs/ioctl.c +1
-1@@ -3244,7 +3245,7 @@ static int btrfs_extent_same_range(struct inode *src, u64 loff, u64 len,* source range to serialize with relocation. */ btrfs_double_extent_lock (src, loff, dst, dst_loff, len); - ret =btrfs_clone (src, dst, loff, len, len, dst_loff,1 ); + ret =btrfs_clone (src, dst, loff, len,ALIGN (len, bs), dst_loff,1 );
A heads-up for anyone backporting this to 5.0: this patch depends on
57a50e2506df Btrfs: remove no longer needed range length checks for deduplication
Simply resolving the git conflict without including 57a50e2506df produces a kernel where dedupe rounds the size of the dst file up to the next block boundary. This is because 57a50e2506df changes the value of "len". Before 57a50e2506df, "len" is equivalent to "ALIGN(len, bs)" at the btrfs_clone line; after 57a50e2506df, "len" is the unaligned dedupe request length passed to the btrfs_extent_same_range function. This changes the semantics of the btrfs_clone line significantly.
57a50e2506df is in 5.1, so 5.1+ kernels do not require any additional patches.
4.20 and earlier don't have the bug, so don't need a fix.
Quoted 6 lines
fs/btrfs/ioctl.c +0
-0btrfs_double_extent_unlock (src, loff, dst, dst_loff, len);return ret;Signature · 1 line
2.11.0
Re: [PATCH 2/2] Btrfs: make deduplication with range including the last block work
Quoted 31 lines · Zygo Blaxell
Quoted 29 lines · On Mon, Dec 16, 2019 at 06:26:56PM +0000, [email protected] wrote:
From: Filipe Manana <[email protected]>
Since btrfs was migrated to use the generic VFS helpers for clone and deduplication, it stopped allowing for the last block of a file to be deduplicated when the source file size is not sector size aligned (when eof is somewhere in the middle of the last block). There are two reasons for that:
1) The generic code always rounds down, to a multiple of the block size, the range's length for deduplications. This means we end up never deduplicating the last block when the eof is not block size aligned, even for the safe case where the destination range's end offset matches the destination file's size. That rounding down operation is done at
generic_remap_check_len();2) Because of that, the btrfs specific code does not expect anymore any non-aligned range length's for deduplication and therefore does not work if such nona-aligned length is given.
This patch addresses that second part, and it depends on a patch that fixes
generic_remap_check_len(), in the VFS, which was submitted ealier and has the following subject:"fs: allow deduplication of eof block into the end of the destination file"
These two patches address reports from users that started seeing lower deduplication rates due to the last block never being deduplicated when the file size is not aligned to the filesystem's block size.
Quoted 6 lines
Quoted 2 lines
Should these patches be marked for stable (5.0+, but see below for caveats about 5.0)? The bug affects 5.3 and 5.4 which are still active, and dedupe is an important feature for some users.
Usually I only mark things for stable that are critical: corruptions, crashes and memory leaks for example.
I don't think this is a critical issue, since none of those things happen. It's certainly inconvenient to not have
an extent fully deduplicated, but it's just that.
If a maintainer wants to add it for stable, I'm fine with it.
Quoted 26 lines
Quoted 18 lines
--- fs/btrfs/ioctl.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-)fs/btrfs/ioctl.c +1
-0@@ -3237,6 +3237,7 @@ static void btrfs_double_extent_lock(struct inode *inode1, u64 loff1,static int btrfs_extent_same_range (struct inode *src,u64 loff,u64 len,struct inode *dst,u64 dst_loff) { +const u64 bs =BTRFS_I (src)->root->fs_info->sb->s_blocksize;int ret;/* fs/btrfs/ioctl.c static int btrfs_extent_same_range(struct inode *src, u64 loff, u64 len, · line 3248
Quoted 5 lines
fs/btrfs/ioctl.c +1
-1@@ -3244,7 +3245,7 @@ static int btrfs_extent_same_range(struct inode *src, u64 loff, u64 len,* source range to serialize with relocation. */ btrfs_double_extent_lock (src, loff, dst, dst_loff, len); - ret =btrfs_clone (src, dst, loff, len, len, dst_loff,1 ); + ret =btrfs_clone (src, dst, loff, len,ALIGN (len, bs), dst_loff,1 );A heads-up for anyone backporting this to 5.0: this patch depends on
Quoted 1 line
57a50e2506dfBtrfs: remove no longer needed range length checks for deduplication
For any kernel without that cleanup patch, backporting the first patch in the series (the one touching only fs/read_write.c) is enough. For any kernel with that cleanup patch, then both patches in the series are needed.
Thanks.
Quoted 20 lines
Simply resolving the git conflict without including
57a50e2506dfproduces a kernel where dedupe rounds the size of the dst file up to the next block boundary. This is because57a50e2506dfchanges the value of "len". Before57a50e2506df, "len" is equivalent to "ALIGN(len, bs)" at thebtrfs_cloneline; after57a50e2506df, "len" is the unaligned dedupe request length passed to thebtrfs_extent_same_rangefunction. This changes the semantics of thebtrfs_cloneline significantly.
57a50e2506dfis in 5.1, so 5.1+ kernels do not require any additional patches.4.20 and earlier don't have the bug, so don't need a fix.
Quoted 6 lines
fs/btrfs/ioctl.c +0
-1btrfs_double_extent_unlock (src, loff, dst, dst_loff, len);return ret; --2.11.0
Re: [PATCH 2/2] Btrfs: make deduplication with range including the last block work
Quoted 40 lines · Filipe Manana
Quoted 31 lines · Zygo Blaxell
Quoted 29 lines · On Mon, Dec 16, 2019 at 06:26:56PM +0000, [email protected] wrote:
From: Filipe Manana <[email protected]>
Since btrfs was migrated to use the generic VFS helpers for clone and deduplication, it stopped allowing for the last block of a file to be deduplicated when the source file size is not sector size aligned (when eof is somewhere in the middle of the last block). There are two reasons for that:
1) The generic code always rounds down, to a multiple of the block size, the range's length for deduplications. This means we end up never deduplicating the last block when the eof is not block size aligned, even for the safe case where the destination range's end offset matches the destination file's size. That rounding down operation is done at
generic_remap_check_len();2) Because of that, the btrfs specific code does not expect anymore any non-aligned range length's for deduplication and therefore does not work if such nona-aligned length is given.
This patch addresses that second part, and it depends on a patch that fixes
generic_remap_check_len(), in the VFS, which was submitted ealier and has the following subject:"fs: allow deduplication of eof block into the end of the destination file"
These two patches address reports from users that started seeing lower deduplication rates due to the last block never being deduplicated when the file size is not aligned to the filesystem's block size.
Quoted 6 lines
Quoted 2 lines
Should these patches be marked for stable (5.0+, but see below for caveats about 5.0)? The bug affects 5.3 and 5.4 which are still active, and dedupe is an important feature for some users.
Quoted 5 lines
Usually I only mark things for stable that are critical: corruptions, crashes and memory leaks for example.
I don't think this is a critical issue, since none of those things happen. It's certainly inconvenient to not have
an extent fully deduplicated, but it's just that.
In btrfs the reference counting is done by extent and extents are immutable, so extents are either fully deduplicated, or not deduplicated at all. We have to dedupe every part of an extent, and if we fail to do so, no data space is saved while metadata usage increases for the new partial extent reference.
This bug means the dedupe feature is not usable _at all_ for single-extent files with non-aligned EOF, and that is a significant problem for users that rely on dedupe to manage space usage on btrfs (e.g. for build servers where there are millions of duplicate odd-sized small files, and the space savings from working dedupe can be 90% or more). Doubling or tripling space usage for the same data is beyond inconvenience.
It is possible to work around the bug in userspace and recover the space with clone, but there is no way to do it safely on live data without a working dedupe-range ioctl.
Quoted 1 line
If a maintainer wants to add it for stable, I'm fine with it.
At this point it would only affect 5.4--all the other short-term kernels are closed, and none of the LTS kernels need the patch--but it would be nice if 5.4 had working dedupe.
Quoted 56 lines
Quoted 26 lines
Quoted 18 lines
--- fs/btrfs/ioctl.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-)fs/btrfs/ioctl.c +1
-0@@ -3237,6 +3237,7 @@ static void btrfs_double_extent_lock(struct inode *inode1, u64 loff1,static int btrfs_extent_same_range (struct inode *src,u64 loff,u64 len,struct inode *dst,u64 dst_loff) { +const u64 bs =BTRFS_I (src)->root->fs_info->sb->s_blocksize;int ret;/* fs/btrfs/ioctl.c static int btrfs_extent_same_range(struct inode *src, u64 loff, u64 len, · line 3248
Quoted 5 lines
fs/btrfs/ioctl.c +1
-1@@ -3244,7 +3245,7 @@ static int btrfs_extent_same_range(struct inode *src, u64 loff, u64 len,* source range to serialize with relocation. */ btrfs_double_extent_lock (src, loff, dst, dst_loff, len); - ret =btrfs_clone (src, dst, loff, len, len, dst_loff,1 ); + ret =btrfs_clone (src, dst, loff, len,ALIGN (len, bs), dst_loff,1 );A heads-up for anyone backporting this to 5.0: this patch depends on
Quoted 1 line
57a50e2506dfBtrfs: remove no longer needed range length checks for deduplicationFor any kernel without that cleanup patch, backporting the first patch in the series (the one touching only
fs/read_write.c) is enough. For any kernel with that cleanup patch, then both patches in the series are needed.Thanks.
Quoted 20 lines
Simply resolving the git conflict without including
57a50e2506dfproduces a kernel where dedupe rounds the size of the dst file up to the next block boundary. This is because57a50e2506dfchanges the value of "len". Before57a50e2506df, "len" is equivalent to "ALIGN(len, bs)" at thebtrfs_cloneline; after57a50e2506df, "len" is the unaligned dedupe request length passed to thebtrfs_extent_same_rangefunction. This changes the semantics of thebtrfs_cloneline significantly.
57a50e2506dfis in 5.1, so 5.1+ kernels do not require any additional patches.4.20 and earlier don't have the bug, so don't need a fix.
Quoted 6 lines
fs/btrfs/ioctl.c +0
-1btrfs_double_extent_unlock (src, loff, dst, dst_loff, len);return ret; --2.11.0
Re: [PATCH 2/2] Btrfs: make deduplication with range including the last block work
Quoted 48 lines · Zygo Blaxell
Quoted 40 lines · Filipe Manana
Quoted 31 lines · Zygo Blaxell
Quoted 29 lines · On Mon, Dec 16, 2019 at 06:26:56PM +0000, [email protected] wrote:
From: Filipe Manana <[email protected]>
Since btrfs was migrated to use the generic VFS helpers for clone and deduplication, it stopped allowing for the last block of a file to be deduplicated when the source file size is not sector size aligned (when eof is somewhere in the middle of the last block). There are two reasons for that:
1) The generic code always rounds down, to a multiple of the block size, the range's length for deduplications. This means we end up never deduplicating the last block when the eof is not block size aligned, even for the safe case where the destination range's end offset matches the destination file's size. That rounding down operation is done at
generic_remap_check_len();2) Because of that, the btrfs specific code does not expect anymore any non-aligned range length's for deduplication and therefore does not work if such nona-aligned length is given.
This patch addresses that second part, and it depends on a patch that fixes
generic_remap_check_len(), in the VFS, which was submitted ealier and has the following subject:"fs: allow deduplication of eof block into the end of the destination file"
These two patches address reports from users that started seeing lower deduplication rates due to the last block never being deduplicated when the file size is not aligned to the filesystem's block size.
Quoted 6 lines
Quoted 2 lines
Should these patches be marked for stable (5.0+, but see below for caveats about 5.0)? The bug affects 5.3 and 5.4 which are still active, and dedupe is an important feature for some users.
Quoted 5 lines
Usually I only mark things for stable that are critical: corruptions, crashes and memory leaks for example.
I don't think this is a critical issue, since none of those things happen. It's certainly inconvenient to not have
an extent fully deduplicated, but it's just that.
Quoted 5 lines
In btrfs the reference counting is done by extent and extents are immutable, so extents are either fully deduplicated, or not deduplicated at all. We have to dedupe every part of an extent, and if we fail to do so, no data space is saved while metadata usage increases for the new partial extent reference.
Yes, I know. That was explained in the cover letter, why allowing deduplication of the eof block is more important for btrfs than it is for xfs for example.
Quoted 7 lines
This bug means the dedupe feature is not usable
_atall_for single-extent files with non-aligned EOF, and that is a significant problem for users that rely on dedupe to manage space usage on btrfs (e.g. for build servers where there are millions of duplicate odd-sized small files, and the space savings from working dedupe can be 90% or more). Doubling or tripling space usage for the same data is beyond inconvenience.
Sure, I understand that, I know how btrfs manages extents and I'm well familiar with its cloning/deduplication implementation.
Still, it's not something I consider critical enough to get to stable, as there's no corruption, data loss or a crash.
That doesn't mean the patches aren't going to stable branches, that depends on the maintainers of each subsystem (vfs, btrfs).
Thanks.
Quoted 67 lines
It is possible to work around the bug in userspace and recover the space with clone, but there is no way to do it safely on live data without a working dedupe-range ioctl.
Quoted 1 line
If a maintainer wants to add it for stable, I'm fine with it.
At this point it would only affect 5.4--all the other short-term kernels are closed, and none of the LTS kernels need the patch--but it would be nice if 5.4 had working dedupe.
Quoted 56 lines
Quoted 26 lines
Quoted 18 lines
--- fs/btrfs/ioctl.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-)fs/btrfs/ioctl.c +1
-0@@ -3237,6 +3237,7 @@ static void btrfs_double_extent_lock(struct inode *inode1, u64 loff1,static int btrfs_extent_same_range (struct inode *src,u64 loff,u64 len,struct inode *dst,u64 dst_loff) { +const u64 bs =BTRFS_I (src)->root->fs_info->sb->s_blocksize;int ret;/* fs/btrfs/ioctl.c static int btrfs_extent_same_range(struct inode *src, u64 loff, u64 len, · line 3248
Quoted 5 lines
fs/btrfs/ioctl.c +1
-1@@ -3244,7 +3245,7 @@ static int btrfs_extent_same_range(struct inode *src, u64 loff, u64 len,* source range to serialize with relocation. */ btrfs_double_extent_lock (src, loff, dst, dst_loff, len); - ret =btrfs_clone (src, dst, loff, len, len, dst_loff,1 ); + ret =btrfs_clone (src, dst, loff, len,ALIGN (len, bs), dst_loff,1 );A heads-up for anyone backporting this to 5.0: this patch depends on
Quoted 1 line
57a50e2506dfBtrfs: remove no longer needed range length checks for deduplicationFor any kernel without that cleanup patch, backporting the first patch in the series (the one touching only
fs/read_write.c) is enough. For any kernel with that cleanup patch, then both patches in the series are needed.Thanks.
Quoted 20 lines
Simply resolving the git conflict without including
57a50e2506dfproduces a kernel where dedupe rounds the size of the dst file up to the next block boundary. This is because57a50e2506dfchanges the value of "len". Before57a50e2506df, "len" is equivalent to "ALIGN(len, bs)" at thebtrfs_cloneline; after57a50e2506df, "len" is the unaligned dedupe request length passed to thebtrfs_extent_same_rangefunction. This changes the semantics of thebtrfs_cloneline significantly.
57a50e2506dfis in 5.1, so 5.1+ kernels do not require any additional patches.4.20 and earlier don't have the bug, so don't need a fix.
Quoted 6 lines
fs/btrfs/ioctl.c +0
-1btrfs_double_extent_unlock (src, loff, dst, dst_loff, len);return ret; --2.11.0
Re: [PATCH 2/2] Btrfs: make deduplication with range including the last block work
Quoted 28 lines · Filipe Manana
Quoted 10 lines
Quoted 9 lines
Quoted 3 lines
Should these patches be marked for stable (5.0+, but see below for caveats about 5.0)? The bug affects 5.3 and 5.4 which are still active, and dedupe is an important feature for some users.
Usually I only mark things for stable that are critical: corruptions, crashes and memory leaks for example.
I don't think this is a critical issue, since none of those things happen. It's certainly inconvenient to not have
an extent fully deduplicated, but it's just that.Quoted 5 lines
In btrfs the reference counting is done by extent and extents are immutable, so extents are either fully deduplicated, or not deduplicated at all. We have to dedupe every part of an extent, and if we fail to do so, no data space is saved while metadata usage increases for the new partial extent reference.
Yes, I know. That was explained in the cover letter, why allowing deduplication of the eof block is more important for btrfs than it is for xfs for example.
Quoted 7 lines
This bug means the dedupe feature is not usable
_atall_for single-extent files with non-aligned EOF, and that is a significant problem for users that rely on dedupe to manage space usage on btrfs (e.g. for build servers where there are millions of duplicate odd-sized small files, and the space savings from working dedupe can be 90% or more). Doubling or tripling space usage for the same data is beyond inconvenience.
Quoted 7 lines
Sure, I understand that, I know how btrfs manages extents and I'm well familiar with its cloning/deduplication implementation.
Still, it's not something I consider critical enough to get to stable, as there's no corruption, data loss or a crash.
That doesn't mean the patches aren't going to stable branches, that depends on the maintainers of each subsystem (vfs, btrfs).
To me this looks like a usability bug and regression so I'm all for adding it to stable. Less serious fixes than corruption, data loss and crash land in stable kernels anyway, so if this fixes behaviour and usecases then it qualifies.
I evaluate each patch for stable inclusion so the CC: stable is not required to be in the patch itself when posted, and late requests for inclusion to stable have been working well so we have the process in place.
Quoted 22 lines · On Mon, Dec 16, 2019 at 06:26:54PM +0000, [email protected] wrote:
From: Filipe Manana <[email protected]>
Hi,
This short series allows deduplication of the last block of a file when the eof is not aligned to the sector size, as long as the range's end offset matches the eof of the destination file.
This is a safe case unlike the case where we attempt to clone the block in the middle of a file (which results in a corruption I found last year and affected both btrfs and xfs).
This is motivated by btrfs users reporting lower deduplication scores starting with kernel 5.0, which was the kernel release where btrfs was changed to use the generic VFS helper
generic_remap_file_range_prep(). Users observed that the last block was no longer deduplicated when a file's size is not block size aligned. For btrfs this is specially important because references are kept per extent and not per block, so not having the last block deduplicated means the entire extent is kept allocated, making the deduplication not effective and often pointless in many cases.
Quoted 6 lines
Thanks.
Filipe Manana (2):
fs: allow deduplication of eof block into the end of the destination
file
Btrfs: make deduplication with range including the last block work
I'm going to send pull request with these two patches once the merge window opens.
git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git fs-dedupe-last-block