[PATCH] btrfs-progs: Cleanup BTRFS_COMPAT_EXTENT_TREE_V0

BTRFS_COMPAT_EXTENT_TREE_V0 is introduced for a short time in kernel, and it's over 10 years ago. Nowadays there should be no user for that feature, and kernel has remove this support in Jun, 2018. There is no need for btrfs-progs to support it. This patch will remove EXTENT_TREE_V0 related code

Re: [PATCH] btrfs-progs: Cleanup BTRFS_COMPAT_EXTENT_TREE_V0

On 29.05.19 г. 10:27 ч., Qu Wenruo wrote: > BTRFS_COMPAT_EXTENT_TREE_V0 is introduced for a short time in kernel, > and it's over 10 years ago. > > Nowadays there should be no user for that feature, and kernel has remove > this support in Jun, 2018. There is no need for btrfs-progs to support >

kernel BUG at fs/btrfs/relocation.c:2595! on 5.1.4

I got the stack trace when I did "sudo btrfs device remove 4 ." from a RAID1 file system. The device 4 is bad. There are many "BTRFS error (device sdb): bdev /dev/sdc errs: wr 19368749, rd 91, flush 10138, corrupt 0, gen 0" in kernel log. (/dev/sdc is device 4) There is no power loss. The stack tr

Re: kernel BUG at fs/btrfs/relocation.c:2595! on 5.1.4

I upgraded the kernel to 5.1.5. Got the same error with the command "btrfs device remove 4 ." again.

Re: kernel BUG at fs/btrfs/relocation.c:2595! on 5.1.4

On 2019/5/29 下午9:23, Wèi Cōngruì wrote: > I upgraded the kernel to 5.1.5. > Got the same error with the command "btrfs device remove 4 ." again. > It a known bug and is going to be fixed by this patch: https://patchwork.kernel.org/patch/10955321/ The backport will happen soon, but I'm afraid it

Re: [PATCH 04/18] dax: Introduce IOMAP_DAX_COW to CoW edges during writes

On Wed 29-05-19 14:46:58, Dave Chinner wrote: > On Tue, May 28, 2019 at 09:07:19PM -0700, Darrick J. Wong wrote: > > On Wed, May 29, 2019 at 12:02:40PM +0800, Shiyang Ruan wrote: > > > On 5/29/19 10:47 AM, Dave Chinner wrote: > > > > On Wed, May 29, 2019 at 10:01:58AM +0800, Shiyang Ruan wrote: > >

Re: Patch "Btrfs: do not start a transaction during fiemap"

Hey David. Regarding your patch "Btrfs: do not start a transaction during fiemap"... I assume since the blockdevice had to be set read-only in order for the bug to happen... all these aborted transactions, etc. couldn't cause any corruptions/etc. upon the fs,... so there's nothing further one wou

Let me know

I have a profitable business in our office,Can you stand as next of kin to unclaimed fund of ($18.4 million) in our financial firm so that both of us can go into business once you receive the funds on your side?let me know if you are interested for more details.

Re: [PATCH v3 11/13] btrfs: directly call into crypto framework for checsumming

Hi Johannes! > On 22.05.2019, at 10:19, Johannes Thumshirn wrote: > > Currently btrfs_csum_data() relied on the crc32c() wrapper around the crypto > framework for calculating the CRCs. > > As we have our own crypto_shash structure in the fs_info now, we can > directly call into the crypto frame

Re: [PATCH 04/18] dax: Introduce IOMAP_DAX_COW to CoW edges during writes

On Wed, May 29, 2019 at 03:46:29PM +0200, Jan Kara wrote: > On Wed 29-05-19 14:46:58, Dave Chinner wrote: > > iomap_apply() > > > > ->iomap_begin() > > map old data extent that we copy from > > > > allocate new data extent we copy to in data fork, > > imme

sub-file dedup

I'm experimenting with the rsync algorithm for btrfs deduplication. Every other deduplication tool I've seen works against whole files. I'm concerned about deduping chunks under 4k and about files with scattered extents. Are there best practices for deduplication on btrfs?