On Mon, Jan 4, 2021 at 10:14 PM Chris Murphy <lists(a)colorremedies.com> wrote:
transid errors like this indicate out of order writes due to drive
firmware not honoring file system write ordering and then getting a
badly timed crash/powerfail/shutdown.
First of all thanks for your quick response.
So would I be correct assuming that the problem is in my firmware ? Or
is it too early to say anything like that ?
Is my firmware so outdated that it can't handle BTRFS ?
You report that the file system went read only while using it. This
suggests a dropped write and the file system went read-only to limit
the damage. Ideally we'd get the log, if it made it to disk, to see
what lead up to this so we can determine what the problem is and get
it fixed. What I can tell you is this is not user error but that's not
much comfort.
Well it doesn't provide comfort but at least I can say that it wasn't
me who messed up my filesystem.
Yeah that's bad. I think it's fixable. We need to get a metadata dump
of the file system to see if fsck will fix it.
btrfs-image -c9 -t4 /dev/sdXY /mnt/path/to/file
That will include filenames but not any data. If you need to mask
filenames, add -ss option to the above. (-s won't help here). And the
path to file if you're on a live USB stick can just be something like
~/sreyan-btrfs.img and then put it up on the google drive.
I don't think there is any hope for my data, as I can't even create
the meta-data image:
# btrfs-image -c9 -t4 /dev/mapper/dm_crypt /run/media/liveuser/Backup\
Plus/btrfs_meta.img
parent transid verify failed on 55640064 wanted 44146 found 44438
parent transid verify failed on 55640064 wanted 44146 found 44438
parent transid verify failed on 55640064 wanted 44146 found 44438
Ignoring transid failure
parent transid verify failed on 55902208 wanted 44170 found 44438
Ignoring transid failure
parent transid verify failed on 56410112 wanted 44170 found 44439
Ignoring transid failure
parent transid verify failed on 58621952 wanted 44170 found 44439
Ignoring transid failure
ERROR: child eb corrupted: parent bytenr=178081497088 item=246 parent
level=1 child level=2
ERROR: cannot go to next leaf -5
ERROR: create failed: -5
What do I do now ?
I'm on
irc.freenode.net as cmurf that's usually the easier
way to get
help, on #fedora channel.
Do I need to have a bouncer ? I am in India, and I believe you are in
the US, so when you are active, I am usually sleeping.
Also, have you ever done a balance on this file system? (That is not
a
suggestion that you should or shouldn't have. Just a yes or no
question to try and piece together some other data points.)
No never did anything like that.
--
Regards,
Sreyan Chakravarty