On Mon, Feb 18, 2019 at 2:19 PM Rudolf Kastl <che666@xxxxxxxxx> wrote: > > Any hints on how to recover is greatly appreciated. > > uname -a: > Linux localhost-live 4.18.16-300.fc29.x86_64 #1 SMP Sat Oct 20 > 23:24:08 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux > > btrfs --version: > btrfs-progs v4.17.1 > > dmesg: > [ 46.918149] BTRFS info (device sda2): disk space caching is enabled > [ 46.918151] BTRFS info (device sda2): has skinny extents > [ 147.509999] rfkill: input handler enabled > [ 150.657962] BTRFS warning (device sda2): failed to resume balance: -4 > [ 151.541975] BTRFS error (device sda2): open_ctree failed > [ 159.209490] rfkill: input handler disabled > [ 290.624978] BTRFS info (device sda2): disk space caching is enabled > [ 290.624981] BTRFS info (device sda2): has skinny extents > [ 294.350986] BTRFS info (device sda2): checking UUID tree > [ 294.350994] BTRFS info (device sda2): balance: resuming > [ 297.425043] BTRFS info (device sda2): relocating block group > 1075919716352 flags metadata|raid1 > [ 342.046679] IPv6: ADDRCONF(NETDEV_UP): wlp3s0: link is not ready > [ 429.588813] WARNING: CPU: 5 PID: 155 at fs/btrfs/extent-tree.c:1680 [snip] > [ 429.589101] BTRFS: error (device sda2) in > btrfs_run_delayed_refs:3057: errno=-5 IO failure This suggests an underlying block layer problem, IO error happened outside of Btrfs I think. Do you have the complete dmesg? Also useful: 'smartctl -x' for both drives 'smartctl -l sct erc' for both drives 'cat /sys/block/sdX/device/timeout' for both drives -- Chris Murphy
