All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kinglong Mee <kinglongmee@gmail.com>
To: "J. Bruce Fields" <bfields@fieldses.org>
Cc: Linux NFS Mailing List <linux-nfs@vger.kernel.org>,
	kinglongmee@gmail.com
Subject: Re: [PATCH v2] NFS4.1: try to clean sessions after testing
Date: Fri, 13 Jun 2014 18:44:25 +0800	[thread overview]
Message-ID: <539AD609.4040205@gmail.com> (raw)
In-Reply-To: <20140612152528.GD5437@fieldses.org>

On 6/12/2014 23:25, J. Bruce Fields wrote:
> On Thu, Jun 12, 2014 at 09:38:32AM +0800, Kinglong Mee wrote:
>> On 6/12/2014 07:24, Kinglong Mee wrote:
>>> On 6/12/2014 05:17, J. Bruce Fields wrote:
>>>> I tried to apply this, and the ipv6 patch (could we do that for 4.1
>>>> too?) and the 3 other patches, but:
>>>
>>> nfs4.1 has supports IPv6, the patch for nfs4.0 is a back-port from nfs4.1.
> 
> OK, thanks for explaining.
> 
>>>
>>>>
>>>> 	- there are some conflicts with the latest pynfs (e.g. I already
>>>> 	  added a few acl tests, apologies)
>>>> 	- I'm getting failures to write to a read-only fs, apparently
>>>> 	  one of the tests is trying to write to the export root?  I
>>>> 	  didn't check which one.
>>
>> Can you show me more information about this?
> 
> [root@pip5 pynfs]# ./nfs4.0/testserver.py f19:/exports/xfs/pynfstest-user --maketree
> Initialization failed, no tests run.
> Traceback (most recent call last):
>   File "./nfs4.0/testserver.py", line 381, in <module>
>     main()
>   File "./nfs4.0/testserver.py", line 344, in main
>     env.init()
>   File "/root/pynfs/nfs4.0/servertests/environment.py", line 140, in init
>     self._maketree()
>   File "/root/pynfs/nfs4.0/servertests/environment.py", line 162, in _maketree
>     check(res, msg="Trying to create /%s," % '/'.join(path))
>   File "/root/pynfs/nfs4.0/servertests/environment.py", line 253, in check
>     raise testmod.FailureException(msg)
> testmod.FailureException: Trying to create /tmp, should return NFS4_OK, instead got NFS4ERR_ROFS
> 
> This happens after the ipv6 patch.
> 
> Note /exports on my server is exported read-only, xfs is a separate writeable
> filesystem.

Thanks for your testing.
I have found this bug in IPv6 path, and will send three new path all I have.

thanks,
Kinglong Mee

  reply	other threads:[~2014-06-13 10:44 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-10 10:03 [PATCH] NFS4.1: try to clean sessions after testing Kinglong Mee
2014-06-10 11:55 ` [PATCH v2] " Kinglong Mee
2014-06-11 21:17   ` J. Bruce Fields
2014-06-11 23:24     ` Kinglong Mee
2014-06-12  1:38       ` Kinglong Mee
2014-06-12 15:25         ` J. Bruce Fields
2014-06-13 10:44           ` Kinglong Mee [this message]
2014-06-14  9:21             ` Kinglong Mee
2014-06-18 16:05               ` 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=539AD609.4040205@gmail.com \
    --to=kinglongmee@gmail.com \
    --cc=bfields@fieldses.org \
    --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.