From: Jan Schmidt <list.btrfs@jan-o-sch.net>
To: Jan Schubert <Jan.Schubert@GMX.li>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>,
Chris Mason <chris.mason@oracle.com>
Subject: Re: [PATCH v7 0/8] Btrfs scrub: print path to corrupted files and trigger nodatasum fixup
Date: Tue, 26 Jul 2011 19:36:00 +0200 [thread overview]
Message-ID: <4E2EFB00.2000302@jan-o-sch.net> (raw)
In-Reply-To: <4E2E92FA.4060008@GMX.li>
On 26.07.2011 12:12, Jan Schubert wrote:
> On 07/26/2011 12:04 PM, Jan Schmidt wrote:
>> On 25.07.2011 17:58, Jan Schubert wrote:
>>> btrfs: unable to fixup at 182245531648
>>> btrfs: unable to fixup at 182245535744
>>> btrfs: unable to fixup at 182245539840
>> This is due to rate limitation of printk() to prevent flooding. I'd like
>> to continue discussion of this problem on the list, but I didn't reply
>> to the list this time due to the debug-tree link you gave me.
>
> OK, go on Jan, no problem. Is there any chance to use the numbers above
> to identify related files?
Thanks for sending the debug-tree output. Turns out that there is a
quite obvious bug in my code for extents that have refs but no inline
ref at all.
I'll fix this up and send a new version (hooray).
Jan: It would be nice if you could try the new patch set once I've sent
it. I don't need any additional input from you at the moment.
Chris: As you suggested, the new version will also include two separate
size fields in struct btrfs_data_container, which then can both be unsigned.
-Jan
prev parent reply other threads:[~2011-07-26 17:36 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-22 11:12 [PATCH v7 0/8] Btrfs scrub: print path to corrupted files and trigger nodatasum fixup Jan Schmidt
2011-07-22 11:12 ` [PATCH v7 1/8] btrfs: added helper functions to iterate backrefs Jan Schmidt
2011-07-27 7:59 ` Li Zefan
2011-07-27 8:06 ` Li Zefan
2011-07-27 8:22 ` Jan Schmidt
2011-07-22 11:12 ` [PATCH v7 2/8] btrfs scrub: added unverified_errors Jan Schmidt
2011-07-22 11:12 ` [PATCH v7 3/8] btrfs scrub: print paths of corrupted files Jan Schmidt
2011-07-22 11:12 ` [PATCH v7 4/8] btrfs scrub: bugfix: mirror_num off by one Jan Schmidt
2011-07-22 11:12 ` [PATCH v7 5/8] btrfs: add mirror_num to extent_read_full_page Jan Schmidt
2011-07-22 11:12 ` [PATCH v7 6/8] btrfs scrub: use int for mirror_num, not u64 Jan Schmidt
2011-07-22 11:12 ` [PATCH v7 7/8] btrfs scrub: add fixup code for errors on nodatasum files Jan Schmidt
2011-07-22 11:12 ` [PATCH v7 8/8] btrfs: new ioctls to do logical->inode and inode->path resolving Jan Schmidt
2011-07-23 22:38 ` [PATCH v7 0/8] Btrfs scrub: print path to corrupted files and trigger nodatasum fixup Jan Schubert
2011-07-24 11:36 ` Jan Schmidt
[not found] ` <4E2C0E2C.4070606@GMX.li>
[not found] ` <4E2C1E9D.1090403@jan-o-sch.net>
[not found] ` <4E2C8425.9090601@GMX.li>
2011-07-25 8:34 ` Jan Schmidt
[not found] ` <4E2D5C36.306@GMX.li>
2011-07-25 13:15 ` Jan Schmidt
[not found] ` <4E2D9290.6020600@GMX.li>
[not found] ` <4E2E912E.7040109@jan-o-sch.net>
[not found] ` <4E2E92FA.4060008@GMX.li>
2011-07-26 17:36 ` Jan Schmidt [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=4E2EFB00.2000302@jan-o-sch.net \
--to=list.btrfs@jan-o-sch.net \
--cc=Jan.Schubert@GMX.li \
--cc=chris.mason@oracle.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;
as well as URLs for NNTP newsgroup(s).