Hi, We're having an issue with our BTRFS file system. Our systems are being shut down by cutting power. Sometimes, when the system gets powered on, the BTRFS partition fails to mount. System reports kernel bug fs/btrfs/extent-tree.c:1183. When that occurs, we're able to mount it using both ro and nologreplay flags, which suggests a problem replaying the log on startup. We were able to reproduce the problem by using a controlled power bar and doing automatic power cycle once every few minutes while writing data on the file system. The problem is very hard to reproduce but we've seen it 3 times on 3 different systems. Our BTRFS partition uses a single volume, however that volume is backed by a hardware RAID. You'll find attached the output of the dmesg command. Thank you for your assistance Simon
Output of various commands. Note that those were taken while the BTRFS
filesystem was mounted with ro and nologreplay
gvoc-81 [/]# uname -a
Linux gvoc-81 5.4.34-0-lts #1-Alpine SMP Wed, 22 Apr 2020 19:26:07 UTC x86_64
Linux
gvoc-81 [/]# btrfs --version
btrfs-progs v5.4
gvoc-81 [/]# btrfs fi show
Label: none uuid: a895f1da-4ccc-4d5a-b17e-158072ae54ef
Total devices 1 FS bytes used 68.60GiB
devid 1 size 883.98GiB used 82.07GiB path /dev/sda5
gvoc-81 [/]# btrfs fi df /data
Data, single: total=76.01GiB, used=67.12GiB
System, DUP: total=32.00MiB, used=16.00KiB
Metadata, DUP: total=3.00GiB, used=1.48GiB
GlobalReserve, single: total=202.97MiB, used=0.00B
**********************************************************************
DISCLAIMER:
Privileged and/or Confidential information may be contained in this message. If
you are not the addressee of this message, you may not copy, use or deliver
this message to anyone. In such event, you should destroy the message and
kindly notify the sender by reply e-mail. It is understood that opinions or
conclusions that do not relate to the official business of the company are
neither given nor endorsed by the company. Thank You.
dmesg.log
Description: dmesg.log
