linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Anand Jain <Anand.Jain@oracle.com>
To: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH 2/3] btrfs-progs: fix backref after init-csum-tree
Date: Mon, 02 Dec 2013 14:12:55 +0800	[thread overview]
Message-ID: <529C24E7.5040309@oracle.com> (raw)
In-Reply-To: <1385964715-23355-2-git-send-email-anand.jain@oracle.com>



  Further this needs your review. How should be a complete use case
  of this init-csum-tree feature. mainly how do we expect this work
  in the real scenario. what problem does this solve.

Thanks, Anand


On 12/02/13 02:11 PM, Anand Jain wrote:
> btrfsck reports backref error after running init-csum-tree
>
> btrfsck --init-csum-tree /dev/sdc
> btrfsck /dev/sdc
> ::
> ref mismatch on [29474816 16384] extent item 1, found 0
> Backref 29474816 root 7 not referenced back 0x1101d30
> Incorrect global backref count on 29474816 found 1 wanted 0
> backpointer mismatch on [29474816 16384]
> owner ref check failed [29474816 16384]
> Errors found in extent allocation tree or chunk allocation
> ::
>
> Signed-off-by: Anand Jain <anand.jain@oracle.com>
> ---
>   cmds-check.c |    6 ++++++
>   1 files changed, 6 insertions(+), 0 deletions(-)
>
> diff --git a/cmds-check.c b/cmds-check.c
> index afad8a1..6a8d351 100644
> --- a/cmds-check.c
> +++ b/cmds-check.c
> @@ -6161,6 +6161,7 @@ int cmd_check(int argc, char **argv)
>   		} else if (option_index == 2) {
>   			printf("Creating a new CRC tree\n");
>   			init_csum_tree = 1;
> +			repair = 1;
>   			ctree_flags |= OPEN_CTREE_WRITES;
>   		} else if (option_index == 3) {
>   			init_extent_tree = 1;
> @@ -6234,6 +6235,11 @@ int cmd_check(int argc, char **argv)
>   		ret = btrfs_commit_transaction(trans, info->csum_root);
>   		if (ret)
>   			exit(1);
> +
> +		ret = check_chunks_and_extents(root);
> +		if (ret)
> +			fprintf(stderr,
> +				"Errors found in extent allocation tree or chunk allocation\n");
>   		goto out;
>   	}
>   	ret = check_chunks_and_extents(root);
>

  reply	other threads:[~2013-12-02  6:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-02  6:11 [PATCH 1/3] btrfs-progs: Turning ON incompat isn't an error Anand Jain
2013-12-02  6:11 ` [PATCH 2/3] btrfs-progs: fix backref after init-csum-tree Anand Jain
2013-12-02  6:12   ` Anand Jain [this message]
2013-12-02  6:11 ` [PATCH 3/3] btrfs-progs: qgroup destroy says create failed Anand Jain

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=529C24E7.5040309@oracle.com \
    --to=anand.jain@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).