linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Vackář František" <vackarf@gmail.com>
To: Hugo Mills <hugo@carfax.org.uk>, linux-btrfs@vger.kernel.org
Subject: Re: Btrfs check dont repair
Date: Fri, 2 Oct 2015 12:10:48 +0200	[thread overview]
Message-ID: <CAMH1C+oe6nBYH5JdfYxNNjF181je9_ON=pwTCWMOaHj4sqbm_Q@mail.gmail.com> (raw)
In-Reply-To: <CAMH1C+oztyJ1-M8AxXCG_Lt9AD1JycaneGVG1CikZZfRkq_93Q@mail.gmail.com>

So... I find a solution! :)

I tried to play with mount options. Finally I sucessfully mounted
corrupted btrfs with

mount -t btrfs -oro,degraded,recovery  /dev/sdb2 /mnt/hdd-root/

Thank you for help. Now I copy all data to external drive and make new
filestystem.

Frantisek



2015-10-02 11:05 GMT+02:00 Vackář František <vackarf@gmail.com>:
> I'm not sure if it was my last email with attachement delivered.
>
> My last email is below. Attachement is uploaded here:
> http://franta.naobzoru.cz/files/btrfs-failed.txt
>
> Thank you.
>
> Frantisek
>
> 2015-09-27 11:51 GMT+02:00 Vackář František <vackarf@gmail.com>:
>> So I copy with dd all my 1.7 TB partition with broken btrfs on
>> external hdd and try to repair, but without success.
>>
>> I tried to apply patch to actual sources but its too different to
>> apply. So I downloaded sources from april 2014 (last before date od
>> patch) and it was applied correctly. But when I ran it (./btrfsck
>> --repair /dev/sdb2) it faild. Output is in attachment. Do you have any
>> idea what to do?
>>
>> Frantisek
>>
>> 2015-09-25 12:06 GMT+02:00 Hugo Mills <hugo@carfax.org.uk>:
>>> On Fri, Sep 25, 2015 at 11:36:55AM +0200, Vackář František wrote:
>>>> Now I have memory ok.
>>>>
>>>> I found this patch, but i am not sure, if its the correct one.
>>>> https://www.mail-archive.com/linux-btrfs@vger.kernel.org/msg33496.html
>>>>
>>>> Cay you help me please, witch patch i should use?
>>>
>>>    Yes, that's the patch series (you'll need all three patches). David
>>> Sterba said it didn't apply cleanly any more; I don't know how hard
>>> it'll be to fix up the problems, though.
>>>
>>>    Hugo.
>>>
>>>> Frantisek
>>>>
>>>> 2015-09-23 17:22 GMT+02:00 Vackář František <vackarf@gmail.com>:
>>>> > Yes, I have bad ram. I ran memtest and memory is really bad.
>>>> >
>>>> > So a must buy new memory first.
>>>> >
>>>> > Thank you.
>>>> >
>>>> > Frantisek
>>>> >
>>>> > 2015-09-23 16:43 GMT+02:00 Hugo Mills <hugo@carfax.org.uk>:
>>>> >> 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             | Do not meddle in the affairs of wizards, for they
>>> hugo@... carfax.org.uk | are subtle, and quick to anger.
>>> http://carfax.org.uk/  |
>>> PGP: E2AB1DE4          |                                        J.R.R. Tolkein

  reply	other threads:[~2015-10-02 10:10 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
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 [this message]
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='CAMH1C+oe6nBYH5JdfYxNNjF181je9_ON=pwTCWMOaHj4sqbm_Q@mail.gmail.com' \
    --to=vackarf@gmail.com \
    --cc=hugo@carfax.org.uk \
    --cc=linux-btrfs@vger.kernel.org \
    /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).