> 4. des. 2019 kl. 20:08 skrev Chris Murphy <lists@xxxxxxxxxxxxxxxxx>: > Why do you think it's complaining about the journal? I'm not seeing > tree log related messages here. Thanks for the reply! That must be a misunderstanding on my part (it's called "transid", which suggested something in the journal to me). > Is the output provided complete or are > there additional messages? No, that's it. > What do you get for: > > btrfs insp dump-s /dev/X Attached.
Attachment:
btrfs-insp-dump
Description: Binary data
> What kernel version was being used at the time of the first problem instance? Fedora's 5.2.8-300 kernel. > The transid messages above suggest some kind of failure to actually > commit what should have ended up on stable media. Also please provide: > > btrfs-find-root /dev/ Attached (compressed).
Attachment:
btrfs-find-root.xz
Description: Binary data
> btrfs check --mode=lowmem /dev/ Attached.
Attachment:
btrfs-check
Description: Binary data
> The latter will take a while and since it is an offline check will > need to be done in initramfs, or better from Live media which will > make it easier to capture the output. I recommend btrfs-progs not > older than 5.1.1 if possible. It is only for check, not with --repair, > so the version matters somewhat less if it's not too old. As you can see, it terminates almost immediately with an IO error. However, there's no error in the dmesg on the underlying device, which makes me think there's a bad bounds check or something similar. -- Gard
