All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hendrik Friedel <hendrik@friedels.name>
To: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: btrfsck does not fix
Date: Sat, 11 Jan 2014 00:53:54 +0100	[thread overview]
Message-ID: <52D08812.3040707@friedels.name> (raw)
In-Reply-To: <52CC65C9.3090605@friedels.name>

Hello,

I was wondering whether I am doing something wrong in the way I am 
asking/what I am asking.
My understanding is, that btrfsck is not able to fix this error yet. So, 
I am surprised, that noone is interested in this, apparently?

Regards,
Hendrik Friedel

Am 07.01.2014 21:38, schrieb Hendrik Friedel:
> Hello,
>
>  >>>> I ran btrfsck on my volume with the repair option. When I re-run
> it, >>I get the same errors as before.
>> It mounts without errors? So why then btrfsck/btrfs repair? What
>> precipitated the repair?
>
> I don't know what caused the damage, but a check revealed this:
>
> Checking filesystem on /dev/sdb1
> UUID: 989306aa-d291-4752-8477-0baf94f8c42f
> checking extents
>
> Extent back ref already exists for 2994950590464 parent 863072366592 root 0
> Extent back ref already exists for 2994950836224 parent 863072366592 root 0
> Extent back ref already exists for 862762737664 parent 863072366592 root 0
> Extent back ref already exists for 2994950877184 parent 863072366592
> [...]
> Incorrect global backref count on 2995767250944 found 1 wanted 2
> backpointer mismatch on [2995767250944 4096]
> ref mismatch on [2995767304192 4096] extent item 1, found 2
> Incorrect global backref count on 2995767304192 found 1 wanted 2
> backpointer mismatch on [2995767304192 4096]
> ref mismatch on [2995768258560 4096] extent item 1, found 2
> Incorrect global backref count on 2995768258560 found 1 wanted 2
> backpointer mismatch on [2995768258560 4096]
> ref mismatch on [2995768459264 4096] extent item 1, found 2
> Incorrect global backref count on 2995768459264 found 1 wanted 2
> backpointer mismatch on [2995768459264 4096]
> Errors found in extent allocation tree or chunk allocation
>
> ref mismatch on [2995768459264 4096] extent item 1, found 2
> Incorrect global backref count on 2995768459264 found 1 wanted 2
> backpointer mismatch on [2995768459264 4096]
> Errors found in extent allocation tree or chunk allocation
> checking free space cache
> checking fs roots
> root 256 inode 9579 errors 100, file extent discount
> root 256 inode 9580 errors 100, file extent discount
> root 256 inode 14258 errors 100, file extent discount
> root 256 inode 14259 errors 100, file extent discount
> root 4444 inode 9579 errors 100, file extent discount
> root 4444 inode 9580 errors 100, file extent discount
> root 4444 inode 14258 errors 100, file extent discount
> root 4444 inode 14259 errors 100, file extent discount
> found 1993711951581 bytes used err is 1
> total csum bytes: 4560615360
> total tree bytes: 5643403264
> total fs tree bytes: 139776000
> total extent tree bytes: 263602176
> btree space waste bytes: 504484726
> file data blocks allocated: 6557032402944
>   referenced 6540949323776
> Btrfs v3.12
>
> This made me run btrfsck with the repair option:
>
>
> Extent back ref already exists for 2994950590464 parent 863072366592 root 0
>
> ref mismatch on [32935936 4096] extent item 1, found 2
> repair deleting extent record: key 32935936 168 4096
> adding new tree backref on start 32935936 len 4096 parent 2994784206848
> root 2994784206848
> Incorrect global backref count on 32935936 found 1 wanted 2
> backpointer mismatch on [32935936 4096]
> ref mismatch on [32997376 4096] extent item 1, found 2
> repair deleting extent record: key 32997376 168 4096
> adding new tree backref on start 32997376 len 4096 parent 2994824708096
> root 2994824708096
> Incorrect global backref count on 32997376 found 1 wanted 2
> backpointer mismatch on [32997376 4096]
>
> Incorrect global backref count on 8988365651968 found 1 wanted 0
> backpointer mismatch on [8988365651968 4096]
> repaired damaged extent references
> checking free space cache
> checking fs roots
> root 256 inode 9579 errors 100, file extent discount
> root 256 inode 9580 errors 100, file extent discount
> root 256 inode 14258 errors 100, file extent discount
> root 256 inode 14259 errors 100, file extent discount
> root 4444 inode 9579 errors 100, file extent discount
> root 4444 inode 9580 errors 100, file extent discount
> root 4444 inode 14258 errors 100, file extent discount
> root 4444 inode 14259 errors 100, file extent discount
> enabling repair mode
> Checking filesystem on /dev/sdc1
> UUID: 989306aa-d291-4752-8477-0baf94f8c42f
> cache and super generation don't match, space cache will be invalidated
> found 827360733827 bytes used err is 1
> total csum bytes: 4446455380
> total tree bytes: 5506977792
> total fs tree bytes: 137293824
> total extent tree bytes: 258691072
> btree space waste bytes: 496921489
> file data blocks allocated: 6440132583424
>   referenced 6424163344384
> Btrfs v3.12
>
>
> After this, I ran a check without the repair option again and the same
> errors persist.
>
> Greetings,
> Hendrik
>
>


-- 
Hendrik Friedel
Auf dem Brink 12
28844 Weyhe
Mobil 0178 1874363

  reply	other threads:[~2014-01-10 23:53 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-03 19:41 btrfsck does not fix Hendrik Friedel
2014-01-03 23:33 ` Chris Murphy
2014-01-04 21:21   ` Hendrik Friedel
2014-01-05 13:36     ` Hendrik Friedel
2014-01-05 16:55     ` Chris Murphy
2014-01-07 20:38       ` Hendrik Friedel
2014-01-10 23:53         ` Hendrik Friedel [this message]
2014-01-11  1:05           ` Chris Murphy
2014-01-12 22:31             ` Hendrik Friedel
2014-01-14  0:40               ` Chris Murphy
2014-01-14  6:03                 ` Duncan
2014-01-14  7:49                   ` Chris Murphy
2014-01-14  9:30                     ` Duncan
2014-01-14  9:38                       ` Hugo Mills
2014-01-14 17:17                       ` Chris Murphy
2014-01-18  7:20                         ` Chris Samuel
2014-01-14  8:16                 ` Hugo Mills
2014-01-19 19:37               ` Martin Steigerwald
2014-01-21 20:00                 ` Hendrik Friedel
2014-01-21 20:01                   ` Hendrik Friedel
2014-02-08 22:01                   ` Hendrik Friedel
2014-02-09  0:45                     ` Chris Murphy
2014-02-09  8:36                       ` Hendrik Friedel
2014-02-11  1:45                         ` Chris Murphy
2014-02-11  2:23                           ` Chris Murphy
2014-02-16 19:18                             ` Hendrik Friedel
2014-02-16 19:54                               ` Chris Murphy
2014-02-17  3:20                                 ` Duncan
2014-02-17  9:41                                   ` Goswin von Brederlow
2014-02-18 21:55                                   ` Hendrik Friedel
2014-02-18 22:12                                     ` Chris Murphy
2014-03-02 18:39                                       ` Hendrik Friedel
2014-03-03 22:35                                         ` Chris Murphy
2014-03-04  6:42                                           ` Hendrik Friedel
2014-03-04 17:02                                             ` Chris Murphy
2014-03-03  1:09                                 ` Russell Coker

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=52D08812.3040707@friedels.name \
    --to=hendrik@friedels.name \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.