You are not logged in.

#1 2015-12-06 16:02:35

nstgc
Member
Registered: 2014-03-17
Posts: 393

Btrfs: bad extend type mismatch with chunk after Magic SysRq REISUB

I was beta testing some software which crashed my system pretty hard. I ended resorting to Magic SysRq. I booted into an Arch image and ran the file checker. Several partitions are giving me bad extent [number , number ], type mismatch with chunk. From the btrfs mailing list it seems as if this only happens after an ext*-->btrfs conversion, however my volumes were never converted. It's also suppose to benign.

I can give any journal entries since there isn't anything in there from after Nov 25th. This is inspire of my system volume being supposedly error from according to both check and scrub. I have a snapshot of y Arch installation, and its journal goes past Nov 25. This volume is a raid1.

My raid5 seems to be the only one with this error, though I can't check the raid0 sitting on top of bcache. I'm currently running a scrub. So far, at 30% completion, its okay.

Really, I'm just looking for someone to either confirm that everything is okay and that the missing journal entries are due to something other than FS corruption, or points on what next to do. When my data is on the line, I tend to tred lightly.

http://comments.gmane.org/gmane.comp.fi … trfs/50411

Last edited by nstgc (2015-12-06 16:44:58)

Offline

Board footer

Powered by FluxBB