Re: [RFC PATCH] btrfs: correct inode's outstanding_extents computation

hello, On 05/19/2016 07:01 PM, Filipe Manana wrote: On Thu, May 19, 2016 at 11:49 AM, Wang Xiaoguang wrote: This issue was revealed by modifing BTRFS_MAX_EXTENT_SIZE(128MB) to 64KB, When modifing BTRFS_MAX_EXTENT_SIZE(128MB) to 64KB, fsstress test often gets these warnings from btrfs_destroy_i

[PATCH] btrfs-progs: utils: use better wrappered random generator

Btrfs was using normal srand()/rand() pseudo-random number generator functions. Although it's mostly fine, but it's quite easy to forget to initialize the seed. This patch will introduce new random number generator wrappers: rand_int(), rand_u8/16/32/64(), and use uniformly distributed pseudo-ran

Re: [PATCH 0/4] Add support to clear v1 free space cache for btrfs check

Ivan P wrote on 2016/05/22 19:44 +0200: Sorry for the delay, I just got home today. Here is the output after running --clearcache: === ./btrfsck --readonly /dev/sda Checking filesystem on /dev/sda UUID: 013cda95-8aab-4cb2-acdd-2f0f78036e02 checking extents c

Re: [PATCH 0/4] Add support to clear v1 free space cache for btrfs check

Sorry for the delay, I just got home today. Here is the output after running --clearcache: === ./btrfsck --readonly /dev/sda Checking filesystem on /dev/sda UUID: 013cda95-8aab-4cb2-acdd-2f0f78036e02 checking extents checking free space cache cache and super gen