From: Hugo Mills <hugo@carfax.org.uk>
To: "Vackář František" <vackarf@gmail.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Btrfs check dont repair
Date: Wed, 23 Sep 2015 14:43:34 +0000 [thread overview]
Message-ID: <20150923144334.GP5918@carfax.org.uk> (raw)
In-Reply-To: <CAMH1C+r4yYU8hYfcZpFRyN1UWY8OPTs5Md7MdE=bm2RW9udREQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1906 bytes --]
On Wed, Sep 23, 2015 at 04:39:27PM +0200, Vackář František wrote:
> Hello,
>
> i have problem with my btrfs, can you help me, please? Its on my
> notebook. Sometimes it exhausted battery during sleep and died. But
> everytime FS was ok. But ones mount fail.
>
> Do you have any idea how repair it?
[snip]
> [root@rak ~]# dmesg | tail
[snip]
> [ 4108.444472] BTRFS critical (device sdb2): corrupt leaf, bad key
> order: block=3242455040,root=1, slot=0
You have bad RAM. You should run memtest and fix the hardware first.
After that, there's some patches that should allow btrfs repair to
fix bad key orders in most situations -- I think David was picking
them up again, but I don't know what state they're in right now.
Hugo.
> [ 4108.444649] BTRFS critical (device sdb2): corrupt leaf, bad key
> order: block=3242455040,root=1, slot=0
> [ 4108.444681] BTRFS error (device sdb2): Error removing orphan entry,
> stopping orphan cleanup
> [ 4108.444684] BTRFS error (device sdb2): could not do orphan cleanup -22
> [ 4111.047323] BTRFS: open_ctree failed
>
> [root@rak ~]# uname -a
> Linux rak 4.1.2-2-ARCH #1 SMP PREEMPT Wed Jul 15 08:30:32 UTC 2015
> x86_64 GNU/Linux
>
> [root@rak ~]# btrfs fi show /dev/sdb2
> Label: 'data' uuid: 754a3186-c0ae-4680-ab28-864c8bdad8b5
> Total devices 1 FS bytes used 1.23TiB
> devid 1 size 1.72TiB used 1.24TiB path /dev/sdb2
>
> btrfs-progs v4.2
>
> [root@rak ~]# btrfs --version
> btrfs-progs v4.2
>
> [root@rak ~]# btrfs fi show
> Label: 'data' uuid: 754a3186-c0ae-4680-ab28-864c8bdad8b5
> Total devices 1 FS bytes used 1.23TiB
> devid 1 size 1.72TiB used 1.24TiB path /dev/sdb2
>
> btrfs-progs v4.2
--
Hugo Mills | Sometimes, when I'm alone, I Google myself.
hugo@... carfax.org.uk |
http://carfax.org.uk/ |
PGP: E2AB1DE4 |
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2015-09-23 14:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-23 14:39 Btrfs check dont repair Vackář František
2015-09-23 14:43 ` Hugo Mills [this message]
2015-09-23 15:22 ` Vackář František
2015-09-25 9:36 ` Vackář František
2015-09-25 10:06 ` Hugo Mills
[not found] ` <CAMH1C+qD8Me-D0VVb5pntPQd4A9VXGCEbxQajZfDCEnWbJUxSA@mail.gmail.com>
2015-10-02 9:05 ` Vackář František
2015-10-02 10:10 ` Vackář František
2015-09-23 17:41 ` Austin S Hemmelgarn
2015-09-23 19:02 ` Vackář František
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=20150923144334.GP5918@carfax.org.uk \
--to=hugo@carfax.org.uk \
--cc=linux-btrfs@vger.kernel.org \
--cc=vackarf@gmail.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).