All of lore.kernel.org
 help / color / mirror / Atom feed
From: Boaz Harrosh <bharrosh@panasas.com>
To: "J. Bruce Fields" <bfields@fieldses.org>
Cc: "J. Bruce Fields" <bfields@redhat.com>,
	NFS list <linux-nfs@vger.kernel.org>
Subject: Re: [RFC] nfsd4: This is: "fix failure to end nfsd4 grace period" ++
Date: Fri, 26 Aug 2011 17:22:56 -0700	[thread overview]
Message-ID: <4E5838E0.4090703@panasas.com> (raw)
In-Reply-To: <20110826201910.GB17196@fieldses.org>

On 08/26/2011 01:19 PM, J. Bruce Fields wrote:
> On Fri, Aug 12, 2011 at 05:30:12PM -0700, Boaz Harrosh wrote:

<snip>

> @@ -156,12 +155,14 @@ out_put:
>  	dput(dentry);
>  out_unlock:
>  	mutex_unlock(&dir->d_inode->i_mutex);
> -	if (status == 0) {
> -		clp->cl_firststate = 1;
> +	if (status == 0)
>  		vfs_fsync(rec_file, 0);
> -	}
> +	else
> +		printk(KERN_ERR "NFSD: failed to write recovery record"
> +				" (err %d); please check that recovery"
> +				" directory exists and is writeable",
> +				status);

Bruce Hi

Which of the variables has the directory path?
Would we like to add that information in the print. From my experience
alot of times those type of problems is the mis-communication of
the path names, and it helps to see what name was actually attempted.

Other wise looks good
Thanks


>  	nfs4_reset_creds(original_cred);
> -	dprintk("NFSD: nfsd4_create_clid_dir returns %d\n", status);
>  	return status;
>  }
>  


  reply	other threads:[~2011-08-27  0:23 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-13  0:30 [RFC] nfsd4: This is: "fix failure to end nfsd4 grace period" ++ Boaz Harrosh
2011-08-26 20:19 ` J. Bruce Fields
2011-08-27  0:22   ` Boaz Harrosh [this message]
2011-08-27  0:46     ` J. Bruce Fields
2011-08-27  0:47       ` [PATCH 1/2] nfsd4: simplify recovery dir setting ++ J. Bruce Fields
2011-08-27  0:47         ` [PATCH 2/2] nfsd4: fix failure to end nfsd4 grace period J. Bruce Fields
2011-08-27  2:07           ` Boaz Harrosh
2011-08-27  2:13             ` J. Bruce Fields

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=4E5838E0.4090703@panasas.com \
    --to=bharrosh@panasas.com \
    --cc=bfields@fieldses.org \
    --cc=bfields@redhat.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 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.