From: Pavel Volkov <negaipub@gmail.com>
To: linux-btrfs@vger.kernel.org
Subject: Re: Error: could not do orphan cleanup -22
Date: Tue, 11 Feb 2014 00:53:57 +0400 [thread overview]
Message-ID: <2047838.eX9UXPvc1f@melforce> (raw)
In-Reply-To: <2047669.QmpNhlvBGM@melforce>
Some more update.
I checked the FS with btrfsck:
checking extents
ref mismatch on [17018880 8192] extent item 1, found 2
Incorrect local backref count on 17018880 root 258 owner 826 offset 0 found 2 wanted 1 back 0x961b268
backpointer mismatch on [17018880 8192]
ref mismatch on [17027072 8192] extent item 1, found 2
Incorrect local backref count on 17027072 root 258 owner 827 offset 0 found 2 wanted 1 back 0x93ce988
backpointer mismatch on [17027072 8192]
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/sdb3
UUID: c3f3a649-d8c3-49e1-9962-9b3ca9f54f1d
free space inode generation (0) did not match free space cache generation (6151)
free space inode generation (0) did not match free space cache generation (6151)
found 226798495277 bytes used err is 0
total csum bytes: 619125860
total tree bytes: 1041760256
total fs tree bytes: 270155776
total extent tree bytes: 22577152
btree space waste bytes: 164080420
file data blocks allocated: 1102635630592
referenced 634893860864
Btrfs v3.12
Is it ok to try repairing it?
next prev parent reply other threads:[~2014-02-10 20:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-09 20:20 Error: could not do orphan cleanup -22 Pavel Volkov
2014-02-10 19:38 ` Pavel Volkov
2014-02-10 20:53 ` Pavel Volkov [this message]
2014-02-10 21:13 ` Josef Bacik
2014-02-10 21:52 ` Pavel Volkov
2014-02-12 7:32 ` Pavel Volkov
2014-02-12 14:38 ` Pavel Volkov
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=2047838.eX9UXPvc1f@melforce \
--to=negaipub@gmail.com \
--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