search for: compress_file_range

...BTRFS_DEFAULT_MAX_COMPR_EXTENTS; /* readahead state */ INIT_RADIX_TREE(&fs_info->reada_tree, GFP_NOFS & ~__GFP_WAIT); diff --git a/fs/btrfs/inode.c b/fs/btrfs/inode.c index 148abeb..78fc6eb 100644 --- a/fs/btrfs/inode.c +++ b/fs/btrfs/inode.c @@ -346,8 +346,8 @@ static noinline int compress_file_range(struct inode *inode, unsigned long nr_pages_ret = 0; unsigned long total_compressed = 0; unsigned long total_in = 0; - unsigned long max_compressed = 128 * 1024; - unsigned long max_uncompressed = 128 * 1024; + unsigned long max_compressed = root->fs_info->max_compressed_extent_kb * 102...

...entry onto the work queue to write the uncompressed bytes. This * makes sure that both compressed inodes and uncompressed inodes - * are written in the same order that pdflush sent them down. + * are written in the same order that the flusher thread sent them + * down. */ static noinline int compress_file_range(struct inode *inode, struct page *locked_page, diff --git a/fs/btrfs/ordered-data.c b/fs/btrfs/ordered-data.c index 643335a..051c7fe 100644 --- a/fs/btrfs/ordered-data.c +++ b/fs/btrfs/ordered-data.c @@ -596,7 +596,7 @@ void btrfs_start_ordered_extent(struct inode *inode, /* * pages in t...

...0000000000000fb2 00000000000008f7 00000000000002da ffff880303a0bcb0 ffffffffa00c5bb0 0000002e00000001 0000000000000000 Call Trace: [<ffffffffa00c5bb0>] insert_inline_extent+0x330/0x350 [btrfs] [<ffffffffa00c5cf6>] cow_file_range_inline+0x126/0x160 [btrfs] [<ffffffffa00c68f0>] compress_file_range+0x3b0/0x580 [btrfs] [<ffffffffa00c6af5>] async_cow_start+0x35/0x50 [btrfs] [<ffffffffa00eac0c>] worker_loop+0xac/0x260 [btrfs] [<ffffffffa00eab60>] ? worker_loop+0x0/0x260 [btrfs] [<ffffffff81086317>] kthread+0x97/0xa0 [<ffffffff8100ce24>] kernel_thread_helper+0x4...

...>] ? deflate_fast+0x24e/0x2e0 [12812.333446] [<ffffffff803bb6a2>] ? zlib_deflate+0x112/0x330 [12812.333446] [<ffffffff80365078>] ? btrfs_zlib_compress_pages+0x158/0x3b0 [12812.333446] [<ffffffff802b6d42>] ? __slab_free+0x212/0x360 [12812.333446] [<ffffffff80341445>] ? compress_file_range+0x405/0x500 [12812.333446] [<ffffffff80252a79>] ? autoremove_wake_function+0x9/0x30 [12812.333446] [<ffffffff8034156e>] ? async_cow_start+0x2e/0x50 [12812.333446] [<ffffffff8035b9f1>] ? worker_loop+0x61/0x160 [12812.333446] [<ffffffff8035b990>] ? worker_loop+0x0/0x160 [1...

For quite a while, I''ve experienced oddities with snapshotted Firefox _CACHE_00?_ files, whose checksums (and contents) would change after the btrfs snapshot was taken, and would even change depending on how the file was brought to memory (e.g., rsyncing it to backup storage vs checking its md5sum before or after the rsync). This only affected these cache files, so I didn''t give