All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Miguel Negrão" <miguel.negrao-lists@friendlyvirus.org>
To: "list, btrfs" <linux-btrfs@vger.kernel.org>
Subject: btrfsck errors - what to do ?
Date: Mon, 25 Nov 2013 18:25:40 +0000	[thread overview]
Message-ID: <52939624.1020603@friendlyvirus.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 4269 bytes --]

Hi

I have a filesystem which I can mount without problems and use. I've
done a scrub on it two days ago which came back with 0 errors.
Today I ran a btrfsck which displayed quite a lot of errors, I tried
correcting them with the --repair flat, but after, running btrfsck
without the --repair again displays the same errors, so it appears it
didn't correct them.

What do the errors mean ? What should I do with this filesystem ? Format
and copy data back from backup ? Besides the btrfsck errors the
filesystem is behaving normally, no errors or problems. Can I still
trust this filesystem ?

I would really apreciate some advice here.

best,
Miguel Negrão

entire btrfsck output: http://ubuntuone.com/5eezQ0UqSHomKBbqXTKOLa
it's a 50MB file zipped to 3.5MB.

scrub status for 155b2835-4900-47e3-be45-a32f9d27ec8f
	scrub started at Sat Nov 23 23:28:47 2013, running for 37956 seconds
	total bytes scrubbed: 1.13TiB with 0 errors


Incorrect global backref count on 1908117016576 found 1 wanted 2
backpointer mismatch on [1908117016576 4096]
ref mismatch on [1908117020672 4096] extent item 1, found 2
Incorrect global backref count on 1908117020672 found 1 wanted 2
backpointer mismatch on [1908117020672 4096]
ref mismatch on [1908117024768 4096] extent item 1, found 2
Incorrect global backref count on 1908117024768 found 1 wanted 2
backpointer mismatch on [1908117024768 4096]
ref mismatch on [1908117032960 4096] extent item 1, found 2
Incorrect global backref count on 1908117032960 found 1 wanted 2
backpointer mismatch on [1908117032960 4096]
ref mismatch on [1908117041152 4096] extent item 1, found 2
Incorrect global backref count on 1908117041152 found 1 wanted 2
backpointer mismatch on [1908117041152 4096]
ref mismatch on [1908117405696 4096] extent item 1, found 2
Incorrect global backref count on 1908117405696 found 1 wanted 2
backpointer mismatch on [1908117405696 4096]
ref mismatch on [1908117409792 4096] extent item 1, found 2
Incorrect global backref count on 1908117409792 found 1 wanted 2
backpointer mismatch on [1908117409792 4096]
ref mismatch on [1908117684224 4096] extent item 2, found 3
Incorrect global backref count on 1908117684224 found 2 wanted 3
backpointer mismatch on [1908117684224 4096]
ref mismatch on [1908117696512 4096] extent item 2, found 3
Incorrect global backref count on 1908117696512 found 2 wanted 3
backpointer mismatch on [1908117696512 4096]
ref mismatch on [1908117741568 4096] extent item 2, found 3
Incorrect global backref count on 1908117741568 found 2 wanted 3
backpointer mismatch on [1908117741568 4096]
ref mismatch on [1908117749760 4096] extent item 2, found 3
Incorrect global backref count on 1908117749760 found 2 wanted 3
backpointer mismatch on [1908117749760 4096]
ref mismatch on [1908117811200 4096] extent item 2, found 3
Incorrect global backref count on 1908117811200 found 2 wanted 3
backpointer mismatch on [1908117811200 4096]
ref mismatch on [1908117905408 4096] extent item 2, found 3
Incorrect global backref count on 1908117905408 found 2 wanted 3
backpointer mismatch on [1908117905408 4096]
ref mismatch on [1908117913600 4096] extent item 2, found 3
Incorrect global backref count on 1908117913600 found 2 wanted 3
backpointer mismatch on [1908117913600 4096]
ref mismatch on [1908118331392 4096] extent item 1, found 2
Incorrect global backref count on 1908118331392 found 1 wanted 2
backpointer mismatch on [1908118331392 4096]
ref mismatch on [1908130492416 4096] extent item 1, found 2
Incorrect global backref count on 1908130492416 found 1 wanted 2
backpointer mismatch on [1908130492416 4096]
Errors found in extent allocation tree or chunk allocation
checking free space cache
checking fs roots
checking csums
checking root refs
Checking filesystem on /dev/sdc1
UUID: 155b2835-4900-47e3-be45-a32f9d27ec8f
cache and super generation don't match, space cache will be invalidated
found 148859392835 bytes used err is 0
total csum bytes: 1870992636
total tree bytes: 9800355840
total fs tree bytes: 6846132224
total extent tree bytes: 673153024
btree space waste bytes: 2150974105
file data blocks allocated: 5702728269824
 referenced 3158280015872
Btrfs v0.20-rc1-335-gf00dd83



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 555 bytes --]

                 reply	other threads:[~2013-11-25 18:32 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=52939624.1020603@friendlyvirus.org \
    --to=miguel.negrao-lists@friendlyvirus.org \
    --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.