On Mon, Feb 3, 2020 at 3:10 PM Qu Wenruo <quwenruo.btrfs@xxxxxxx> wrote: > On 2020/2/3 下午9:58, Robert Klemme wrote: > > I would assume as much as there were no power outages or crashes. I > > read about a bug recently (probably on > > https://www.reddit.com/r/btrfs/) that had to do with btrfs on LUKS and > > / or LVM. Could this be an explanation? > > No, it should only be some bug inside btrfs, nothing to do with lower stack. Unfortunately I have not found the source again. IIRC that was about a bug in btrfs code but showed only in combination with either LUKS and / or LVM. > >> Btrfs check --repair should be able to repair that, but not recommended > >> for your btrfs-progs version. > >> > >> There is a bug that any power loss or transaction abort in btrfs-progs > >> can further screw up your fs. > > > > That explains why a repair I recently attempted elsewhere did make > > things worse... > > > >> That bug is solved in v5.1 btrfs-progs. > >> I doubt it's backported for any btrfs-progs at all. > >> > >> So please use latest btrfs-progs to fix it. > >> A liveiso from some rolling distro would help. > > > > Is there a PPA? I could not find one so far. > > For "some rolling distro", I mean Arch... :-) Understood, but I would have liked to also install the newer tool version on that system. Anyway, I pulled a Xubuntu 19.10 and that has more recent btrfs tools. Repair went smoothly and system is up and running. As additional measure I installed Ubuntu's HWE packages to get a newer kernel (from 4.15 to 5.3.0). $ sudo apt install linux-generic-hwe-18.04 xserver-xorg-hwe-18.04 Just wanted to give you an update how it went. Again, thank you for your support! Kind regards robert -- [guy, jim, charlie, sho].each {|him| remember.him do |as, often| as.you_can - without end} http://blog.rubybestpractices.com/
