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

[Josef Bacik <jbacik@fusionio.com>]

On Fri, Oct 25, 2013 at 07:27:24PM +0100, Martin wrote:
> 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?
> 

Yes, I'm a little worried about your particular case so I'd like to see if it
works.  If you don't see a lot of output after say 5 minutes let's assume I
didn't fix your problem and let me know so I can make the other change I
considered.  Thanks,

Josef