linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Anna Schumaker <schumaker.anna@gmail.com>
To: Olga Kornievskaia <kolga@netapp.com>,
	Trond.Myklebust@primarydata.com, anna.schumaker@netapp.com
Cc: linux-nfs@vger.kernel.org
Subject: Re: [PATCH 1/1] PNFS fix fallback to MDS if got error on commit to DS
Date: Thu, 30 Mar 2017 13:34:52 -0400	[thread overview]
Message-ID: <1c58c56a-3a16-2a5d-b87c-d0019762ec9e@gmail.com> (raw)
In-Reply-To: <20170330141055.61977-1-kolga@netapp.com>

Hi Olga,

On 03/30/2017 10:10 AM, Olga Kornievskaia wrote:
> Upong receiving some errors (EACCES) on commit to the DS the code
> doesn't fallback to MDS and intead retrieds to the same DS again.

Just so I know what's going on: do you want this patch instead of the first one in the thread?

Thanks,
Anna
> 
> Signed-off-by: Olga Kornievskaia <kolga@netapp.com>
> ---
>  fs/nfs/filelayout/filelayout.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/fs/nfs/filelayout/filelayout.c b/fs/nfs/filelayout/filelayout.c
> index a3fc48b..59e1efa 100644
> --- a/fs/nfs/filelayout/filelayout.c
> +++ b/fs/nfs/filelayout/filelayout.c
> @@ -202,10 +202,10 @@ static int filelayout_async_handle_error(struct rpc_task *task,
>  			task->tk_status);
>  		nfs4_mark_deviceid_unavailable(devid);
>  		pnfs_error_mark_layout_for_return(inode, lseg);
> -		pnfs_set_lo_fail(lseg);
>  		rpc_wake_up(&tbl->slot_tbl_waitq);
>  		/* fall through */
>  	default:
> +		pnfs_set_lo_fail(lseg);
>  reset:
>  		dprintk("%s Retry through MDS. Error %d\n", __func__,
>  			task->tk_status);
> 

  reply	other threads:[~2017-03-30 17:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-15 20:42 [PATCH 1/1] PNFS fix fallback to MDS if got error on commit to DS Olga Kornievskaia
2017-03-28 13:41 ` Olga Kornievskaia
2017-03-30 14:10   ` Olga Kornievskaia
2017-03-30 17:34     ` Anna Schumaker [this message]
2017-03-30 17:59       ` Olga Kornievskaia

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=1c58c56a-3a16-2a5d-b87c-d0019762ec9e@gmail.com \
    --to=schumaker.anna@gmail.com \
    --cc=Trond.Myklebust@primarydata.com \
    --cc=anna.schumaker@netapp.com \
    --cc=kolga@netapp.com \
    --cc=linux-nfs@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).