From: Jan Schubert <Jan.Schubert@GMX.li>
To: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH v8 0/8] Btrfs scrub: print path to corrupted files and trigger nodatasum fixup
Date: Fri, 29 Jul 2011 15:53:27 +0000 (UTC) [thread overview]
Message-ID: <loom.20110729T174701-406@post.gmane.org> (raw)
In-Reply-To: 4E31959B.60907@jan-o-sch.net
Jan Schmidt <list.btrfs <at> jan-o-sch.net> writes:
> 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).
Thx Jan, I did not follow your advice but used the btrfs-debug-tree to
determine the affected files. After deleting them it has been OK.
Interessting thing is, that in one case copying the file has been
possible to resolve one of these errors (after deleting the original file
of course). Other affected file throw an input/output error when trying
to access them.
Let me know when I can test some more things. I can offer to run the
newest kernels and patches and report any issues!?
Thx,
Jan
prev parent reply other threads:[~2011-07-29 15:53 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
2011-07-29 15:53 ` Jan Schubert [this message]
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=loom.20110729T174701-406@post.gmane.org \
--to=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).