On Sun, Jun 10, 2018 at 12:42 PM, Vote 539 <[email protected]> wrote: > I have a btrfs filesystem that I use as a target for send/receive incremental > snapshots. I use btrbk to perform hourly backups. > > The target filesystem was offline for a few days. When I mounted it today, > the filesystem was read-only, with dmesg errors: > > … > [ 167.004684] BTRFS error (device sda2): unable to find ref byte nr > 40366194688 parent 0 root 6894 owner 1 offset 0 > [ 167.004722] ------------[ cut here ]------------ > [ 167.004735] WARNING: CPU: 0 PID: 1273 at > /build/linux-E14mqW/linux-4.4.0/fs/btrfs/extent-tree.c:6553 > __btrfs_free_extent.isra.68+0x8ff/0xd30 [btrfs]() > [ 167.004736] BTRFS: Transaction aborted (error -2) > … > [ 167.005011] BTRFS: error (device sda2) in __btrfs_free_extent:6553: > errno=-2 No such entry > [ 167.005041] BTRFS info (device sda2): forced readonly > [ 167.005044] BTRFS: error (device sda2) in btrfs_run_delayed_refs:2930: > errno=-2 No such entry > … > > Full dmesg: https://pastebin.com/XNKJbN15
I suggest trying a more recent kernel and see if that can handle the problem better, 4.14.48 or newer. > > I unmounted the filesystem and ran btrfs check. I let it run overnight. > Output: The crossing stripe boundaries message sounds like messages we saw with an older btrfs-progs. What version are you using? I suggest 4.16.2 and running 'btrfs check --mode=lowmem' option. It will be slow but it's a different implementation than the default. -- Chris Murphy -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
