Re: [PATCH] Btrfs-progs: allow --init-extent-tree to work when extent tree is borked

[Martin <m_btrfs@ml1.co.uk>]

On 25/10/13 19:01, Josef Bacik wrote:
> Unfortunately you can't run --init-extent-tree if you can't actually read the
> extent root.  Fix this by allowing partial starts with no extent root and then
> have fsck only check to see if the extent root is uptodate _after_ the check to
> see if we are init'ing the extent tree.  Thanks,
> 
> Signed-off-by: Josef Bacik <jbacik@fusionio.com>
> ---
>  cmds-check.c |  9 ++++++---
>  disk-io.c    | 16 ++++++++++++++--
>  2 files changed, 20 insertions(+), 5 deletions(-)
> 
> diff --git a/cmds-check.c b/cmds-check.c
> index 69b0327..8ed7baa 100644
> --- a/cmds-check.c
> +++ b/cmds-check.c

Hey! Quick work!...

Is that worth patching locally and trying against my example?

Thanks,
Martin