All of lore.kernel.org
 help / color / mirror / Atom feed
From: Josef Bacik <josef@redhat.com>
To: Josef Bacik <josef@redhat.com>, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] Btrfs: always store the mirror we read the eb from
Date: Wed, 18 Apr 2012 09:41:12 -0400	[thread overview]
Message-ID: <20120418134111.GA1937@localhost.localdomain> (raw)
In-Reply-To: <20120418104407.GH20982@twin.jikos.cz>

On Wed, Apr 18, 2012 at 12:44:07PM +0200, David Sterba wrote:
> On Mon, Apr 16, 2012 at 09:42:26AM -0400, Josef Bacik wrote:
> > --- a/fs/btrfs/disk-io.c
> > +++ b/fs/btrfs/disk-io.c
> > @@ -390,8 +390,7 @@ static int btree_read_extent_buffer_pages(struct btrfs_root *root,
> >  
> >  		if (!failed_mirror) {
> >  			failed = 1;
> > -			printk(KERN_ERR "failed mirror was %d\n", eb->failed_mirror);
> > -			failed_mirror = eb->failed_mirror;
> > +			failed_mirror = eb->read_mirror;
> >  		}
> >  
> >  		mirror_num++;
> 
> this hunk does not apply for me (on top of master or for-linus), there's
> a different context. In your version the
> 
> 	if (!failed_mirror)
> 
> check is moved after
> 
>  392                 num_copies = btrfs_num_copies(&root->fs_info->mapping_tree,
>  393                                               eb->start, eb->len);
>  394                 if (num_copies == 1)
>  395                         break;
>  396
> 
> which was one of the incremental patches sent for testing, but it's
> needed.
> 
> 

Oh duh sorry I saved that patch as a commit in my tree but didn't actually send
it to the list, I will do that.  Thanks,

Josef

      reply	other threads:[~2012-04-18 13:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-16 13:42 [PATCH] Btrfs: always store the mirror we read the eb from Josef Bacik
2012-04-18 10:44 ` David Sterba
2012-04-18 13:41   ` Josef Bacik [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=20120418134111.GA1937@localhost.localdomain \
    --to=josef@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.