From: KC <qwrules@gmail.com>
To: linux-btrfs@vger.kernel.org
Subject: btrfs check won't repair inode errors
Date: Mon, 03 Nov 2014 12:34:57 +0100 [thread overview]
Message-ID: <54576861.2030809@gmail.com> (raw)
I noticed my data partition had some inode inconsistencies, so I run
btrfs check --repair.
However, it did nothing and errors are still there:
[root@sandiskFit juha]# btrfs check --repair /dev/mapper/HDD--total-data
enabling repair mode
Fixed 0 roots.
Checking filesystem on /dev/mapper/HDD--total-data
UUID: 3dfb375d-6a7c-47a5-a134-179585941d51
checking extents
checking free space cache
cache and super generation don't match, space cache will be invalidated
checking fs roots
root 5 inode 2207209 errors 400, nbytes wrong
root 5 inode 2256086 errors 400, nbytes wrong
root 5 inode 2278303 errors 400, nbytes wrong
root 5 inode 2282131 errors 400, nbytes wrong
root 5 inode 2288244 errors 400, nbytes wrong
root 5 inode 2307687 errors 400, nbytes wrong
found 123129939084 bytes used err is 1
total csum bytes: 443189672
total tree bytes: 1094713344
total fs tree bytes: 501399552
total extent tree bytes: 81510400
btree space waste bytes: 164316106
file data blocks allocated: 617742684160
referenced 521218134016
Btrfs v3.17
[root@sandiskFit juha]# btrfs check /dev/mapper/HDD--total-data
Checking filesystem on /dev/mapper/HDD--total-data
UUID: 3dfb375d-6a7c-47a5-a134-179585941d51
checking extents
checking free space cache
cache and super generation don't match, space cache will be invalidated
checking fs roots
root 5 inode 2207209 errors 400, nbytes wrong
root 5 inode 2256086 errors 400, nbytes wrong
root 5 inode 2278303 errors 400, nbytes wrong
root 5 inode 2282131 errors 400, nbytes wrong
root 5 inode 2288244 errors 400, nbytes wrong
root 5 inode 2307687 errors 400, nbytes wrong
found 206299866321 bytes used err is 1
total csum bytes: 443189672
total tree bytes: 1094713344
total fs tree bytes: 501399552
total extent tree bytes: 81510400
btree space waste bytes: 164316106
file data blocks allocated: 617742684160
referenced 521218134016
Btrfs v3.17
I am using Btrfs tools v3.17 and kernel 3.17
reply other threads:[~2014-11-03 11:34 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=54576861.2030809@gmail.com \
--to=qwrules@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