From: Jan Schmidt <list.btrfs@jan-o-sch.net>
To: Jan Schubert <Jan.Schubert@GMX.li>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH v8 0/8] Btrfs scrub: print path to corrupted files and trigger nodatasum fixup
Date: Thu, 28 Jul 2011 19:00:11 +0200 [thread overview]
Message-ID: <4E31959B.60907@jan-o-sch.net> (raw)
In-Reply-To: <loom.20110728T163725-25@post.gmane.org>
On 28.07.2011 16:44, Jan Schubert wrote:
> Jan Schubert <Jan.Schubert <at> GMX.li> writes:
>> OK, Patch 1 to 3 did apply and run successfully on 3.0-git8. I've sent
>> Jan some more details about the output of the affected files (which is
>> actually just one quite large one).
>
> Hooray:
>
> scrub status for 03201fc0-7695-4468-9a10-f61ad79f23ca
> scrub started at Thu Jul 28 15:00:54 2011 and finished after 656 seconds
> total bytes scrubbed: 143.40GB with 0 errors
>
> Clean filesystem after deleting the (last) affected file, thx a lot!
:-)
> Next issue: I have an other filesystem which is also reportet as error free
> by scrub:
>
> scrub status for 62bab779-3a5e-4ad0-8f67-9d727813e7ea
> scrub started at Thu Jul 28 16:16:26 2011 and finished after 131 seconds
> total bytes scrubbed: 28.91GB with 0 errors
>
> Doing a btrfsck on the same filesystem I get:
>
> root 5 inode 5067 errors 400
> root 5 inode 5098 errors 400
> root 5 inode 5123 errors 400
> root 5 inode 5125 errors 400
> root 5 inode 6082 errors 400
> found 30889312256 bytes used err is 1
> total csum bytes: 30113200
> total tree bytes: 51560448
> total fs tree bytes: 8212480
> btree space waste bytes: 11638215
> file data blocks allocated: 30991843328
> referenced 31323025408
> Btrfs v0.19-100-g4964d65
>
> Is this something I should be concerned about (regarding the errors)?
I think you shouldn't. The "errors 400" is reported constantly in
#btrfs, it resolves to REF_ERR_NO_ROOT_BACKREF. There should be a
backref, but I haven't heard of any negative impact.
If you are curious, you can try to grab the "inspect-internal" patches
for btrfs-progs and use "btrfs inspect-internal resolve-inode 5067" to
see what files are referenced by those inodes (given you are still
running the kernel you used for scrubbing).
[... which reminds me I have to send a new version of the btrfs-progs
patches since the api changed with v8. damn.]
-Jan
next prev parent reply other threads:[~2011-07-28 17:00 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-27 14:56 [PATCH v8 0/8] Btrfs scrub: print path to corrupted files and trigger nodatasum fixup Jan Schmidt
2011-07-27 14:56 ` [PATCH v8 1/8] btrfs: added helper functions to iterate backrefs Jan Schmidt
2011-11-03 1:41 ` Li Zefan
2011-11-03 10:32 ` Jan Schmidt
2011-11-07 16:46 ` Arne Jansen
2011-07-27 14:56 ` [PATCH v8 2/8] btrfs scrub: added unverified_errors Jan Schmidt
2011-07-27 14:56 ` [PATCH v8 3/8] btrfs scrub: print paths of corrupted files Jan Schmidt
2011-07-27 14:56 ` [PATCH v8 4/8] btrfs scrub: bugfix: mirror_num off by one Jan Schmidt
2011-07-27 14:56 ` [PATCH v8 5/8] btrfs: add mirror_num to extent_read_full_page Jan Schmidt
2011-07-27 14:56 ` [PATCH v8 6/8] btrfs scrub: use int for mirror_num, not u64 Jan Schmidt
2011-07-27 14:56 ` [PATCH v8 7/8] btrfs scrub: add fixup code for errors on nodatasum files Jan Schmidt
2011-07-27 14:56 ` [PATCH v8 8/8] btrfs: new ioctls to do logical->inode and inode->path resolving Jan Schmidt
2011-07-27 16:39 ` [PATCH v8 0/8] Btrfs scrub: print path to corrupted files and trigger nodatasum fixup Jan Schubert
2011-07-27 22:34 ` Jan Schubert
2011-07-28 14:44 ` Jan Schubert
2011-07-28 17:00 ` Jan Schmidt [this message]
2011-07-29 15:53 ` Jan Schubert
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=4E31959B.60907@jan-o-sch.net \
--to=list.btrfs@jan-o-sch.net \
--cc=Jan.Schubert@GMX.li \
--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.