On Sun, Jul 5, 2020 at 11:53 AM Qu Wenruo <quwenruo.btrfs@xxxxxxx> wrote: > How producible is this? I did some log analysis: The problem started showing up on two of three servers starting July 3rd, 2020. This coincides with an applied Ubuntu Linux kernel update to 4.15.0-109-generic whose changelog shows plenty of btrfs changes: https://launchpad.net/ubuntu/+source/linux/4.15.0-109.110 Server #2 (still online) shows 16 error messages in its log since 2020-07-03 whereas server #3 shows 310 error messages. On thing special about server #3 is that its btrfs file system has a huge metadata section (probably due to it hosting many [~ 50 Mio] small files), which doesn't seem too healthy: # btrfs filesystem usage /mnt Overall: Device size: 476.30GiB Device allocated: 372.02GiB Device unallocated: 104.28GiB Device missing: 0.00B Used: 272.16GiB Free (estimated): 194.49GiB (min: 194.49GiB) Data ratio: 1.00 Metadata ratio: 1.00 Global reserve: 512.00MiB (used: 0.00B) Data,single: Size:284.01GiB, Used:193.80GiB /dev/mapper/luks 284.01GiB Metadata,single: Size:88.01GiB, Used:78.36GiB /dev/mapper/luks 88.01GiB System,single: Size:4.00MiB, Used:80.00KiB /dev/mapper/luks 4.00MiB Unallocated: /dev/mapper/luks 104.28GiB > If it still shows the same symptom after verifying the RAM, would you > please apply this small debug diff on your kernel? I'll see what I can do. Thanks, Thilo
