From: higuita <higuita@GMX.net>
To: Chris Murphy <lists@colorremedies.com>
Cc: Qu Wenruo <quwenruo.btrfs@gmx.com>,
Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: btrfs errors
Date: Sat, 17 Mar 2018 01:34:38 +0000 [thread overview]
Message-ID: <20180317013438.73e5bc35@couracado.motaleite.net> (raw)
In-Reply-To: <CAJCQCtQg5_V0POgNbQs894Bq6JExpdb5b38F_T000kFanMQxag@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 4390 bytes --]
Thanks for the reply!
On Tue, 13 Mar 2018 22:24:43 -0600, Chris Murphy
<lists@colorremedies.com> wrote:
> If you search the list for 'corrupt leaf bad key ordering' the top two
> causes are bad RAM and flaky power supply. These can be hard to narrow
> down.
I will try to get new power supply to test as the current one have
about almost 10 years, so probably it this one the source of the problem.
> a. Make sure backups are up to date. Hopefully you can mount the
> volume read only
yes, i have updated backups and i can mount the filesystem without any
problem. I can always reformat the partition and restore, but i would
like to use this to learn how to repair btrfs partitions and help
improving the btrfs if possible.
> b. Make sure you're using a recent btrfs-progs
Check! i'm using btrfs-progs v4.15.1,
> c. (optional) take a btrfs image before you do the repair because if
> something blows up, at least that will help a dev figure out why btrfs
> check blew up your file system.
done! i was expecting a image with at least my used space ( ~40GB),
but i got a 1GB file. Is that normal?
> But yes pretty good chance it can be fixed with 'btrfs check
> --repair'
After booting with a livecd and running a --repair with
btrfs-progs v4.15.1, it didn't look it have done almost anything to the
errors, running a new check still show mostly the same errors:
# btrfs check --force /dev/vdisk/root
WARNING: filesystem mounted, continuing because of --force
Checking filesystem on /dev/vdisk/root
UUID: c6cbf25f-f020-4247-822d-d9a85ec3c09f
checking extents
parent transid verify failed on 4505600 wanted 12266 found 13304
parent transid verify failed on 4505600 wanted 12266 found 13304
Ignoring transid failure
leaf parent key incorrect 4505600
bad block 4505600
ERROR: errors found in extent allocation tree or chunk allocation
checking free space cache
checking fs roots
parent transid verify failed on 4505600 wanted 12266 found 13304
Ignoring transid failure
leaf parent key incorrect 4505600
parent transid verify failed on 4505600 wanted 12266 found 13304
Ignoring transid failure
leaf parent key incorrect 4505600
parent transid verify failed on 4505600 wanted 12266 found 13304
Ignoring transid failure
leaf parent key incorrect 4505600
parent transid verify failed on 4505600 wanted 12266 found 13304
Ignoring transid failure
leaf parent key incorrect 4505600
parent transid verify failed on 4505600 wanted 12266 found 13304
Ignoring transid failure
leaf parent key incorrect 4505600
parent transid verify failed on 4505600 wanted 12266 found 13304
Ignoring transid failure
leaf parent key incorrect 4505600
parent transid verify failed on 4505600 wanted 12266 found 13304
Ignoring transid failure
leaf parent key incorrect 4505600
parent transid verify failed on 4505600 wanted 12266 found 13304
Ignoring transid failure
leaf parent key incorrect 4505600
parent transid verify failed on 4505600 wanted 12266 found 13304
Ignoring transid failure
leaf parent key incorrect 4505600
parent transid verify failed on 4505600 wanted 12266 found 13304
Ignoring transid failure
leaf parent key incorrect 4505600
checking csums
parent transid verify failed on 4505600 wanted 12266 found 13304
Ignoring transid failure
checking root refs
ERROR: transid errors in file system
found 46024671232 bytes used, error(s) found
total csum bytes: 0
total tree bytes: 1035763712
total fs tree bytes: 980156416
total extent tree bytes: 55296000
btree space waste bytes: 194602932
file data blocks allocated: 44942737408
referenced 59370504192
So looks like btrfs check --repair do not really know how to fix this
Thanks for the help
higuita
--
Naturally the common people don't want war... but after all it is the
leaders of a country who determine the policy, and it is always a
simple matter to drag the people along, whether it is a democracy, or
a fascist dictatorship, or a parliament, or a communist dictatorship.
Voice or no voice, the people can always be brought to the bidding of
the leaders. That is easy. All you have to do is tell them they are
being attacked, and denounce the pacifists for lack of patriotism and
exposing the country to danger. It works the same in every country.
-- Hermann Goering, Nazi and war criminal, 1883-1946
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
next prev parent reply other threads:[~2018-03-17 1:34 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-14 2:07 btrfs errors higuita
2018-03-14 4:24 ` Chris Murphy
2018-03-17 1:34 ` higuita [this message]
2018-03-17 17:31 ` Chris Murphy
-- strict thread matches above, loose matches on Subject: below --
2021-05-09 22:08 BTRFS Errors Michael Stickel
2021-05-15 2:24 ` Zygo Blaxell
[not found] <632175948.36.1565689408284.JavaMail.gkos@xpska>
2019-08-13 9:48 ` btrfs errors Konstantin V. Gavrilenko
2019-08-13 10:55 ` Qu Wenruo
[not found] ` <744798339.29.1565703591504.JavaMail.gkos@xpska>
2019-08-13 14:01 ` Qu Wenruo
[not found] ` <1425294964.32.1565720950325.JavaMail.gkos@xpska>
2019-08-13 23:24 ` Qu Wenruo
2019-08-14 9:12 ` Konstantin V. Gavrilenko
[not found] <AFB7E63B2FEE4449B3DBF47BC3AA36F085956971@server2k8.thomii.com>
2011-12-02 12:34 ` Mike Thomas
2011-12-02 12:38 ` Fajar A. Nugraha
2011-12-02 12:42 ` Mike Thomas
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180317013438.73e5bc35@couracado.motaleite.net \
--to=higuita@gmx.net \
--cc=linux-btrfs@vger.kernel.org \
--cc=lists@colorremedies.com \
--cc=quwenruo.btrfs@gmx.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).