On Mon, Jan 4, 2021 at 11:32 AM Sreyan Chakravarty <sreyan32@xxxxxxxxx> wrote: > > On Mon, Jan 4, 2021 at 10:14 PM Chris Murphy <lists@xxxxxxxxxxxxxxxxx> 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 ? Too early. The usual case of transid errors is drive firmware bugs *and* ill timed shutdown. Since you don't have an ill timed shutdown, it's less likely this is a drive firmware bug, but can't be ruled out. i.e. I'm proposing there might be a software bug here and we just need to figure it out. Bad memory usually shows up as bit flips and doesn't result in damage like this - but it has to be considered whether a bitflip can affect code. It can also be a kernel bug - the storage stack has many layers, not just Btrfs and dm-crypt. But no one wants to go blaming other people's work without understanding the problem. > Is my firmware so outdated that it can't handle BTRFS ? No. It's a bit complicated. Buggy drive firmware is common. But normally it doesn't matter mainly due to good luck. More than one thing has to go wrong to cause a problem like (a) firmware bug exists (b) firmware bug is triggered (c) crash/powerfail. If one of those is not true, then it's not a problem. There is also the transient hardware defect problem that can act like a bug but it's just rotting the metadata or data. It's not obvious but it is possible to piece together what's happened when we have enough information. > # 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 ? Rats. Can you retry by adding -w option? In the meantime I'll report back to upstream and see what they recommend next. > > 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. An alternative is matrix. We have a matrix-irc bridge in #fedora and pretty soon I think the plan is to switch mainly to matrix. So if you know about matrix then you can join #fedora - but I don't know how to explain it very well since I don't use matrix yet. I think it keeps the history for you, unlike IRC (I use a bouncer so I will see your messages later). I keep weird hours so it might overlap at some point. -- Chris Murphy _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
