On Jan 29, 2008, at 3:31 PM, Trond Myklebust wrote:
> On Tue, 2008-01-29 at 20:50 +0100, Gianluca Alberici wrote:
>> Hello,
>>
>> I confirm that i have encountered this same problem (EINVAL on open
>> (...O | TRUNC) with the following userspace servers:
>>
>> - nfs-user-server shipped with debian sarge/etch etc...
>> - cfsd (crypto file system which is an nfs server)
>>
>> I want to underline again that these userspace servers have been
>> woking
>> perfectly until 2.6.21.7 (which is the last 2.6.21)
>> Since 2.6.22 the problem came out and it is still present into 2.6.24
>> rc7 (last i tested). Conclusion: there must have been something
>> that is
>> changed in 2.6.22 that caused the problem.
>
> The only difference between these two dumps are the fact that the
> first
> one isn't using the Sun convention for telling NFSv2 servers to set to
> the current time (see the code in xdr_encode_current_server_time).
I thought I saw that on both SETATTRs, but I could be wrong.
> I don't see why this would be new behaviour after 2.6.21. The code for
> this has been in the NFS client since 2.6.15 at least...
A mount option is set on one test client, and not the other, perhaps?
--
Chuck Lever
chuck[dot]lever[at]oracle[dot]com
Hello again everybody
Here follows the testbench:
- I got two mirrors, same machine, same disk etc...chaged hostname, IP,
and on the second i have recompiled kernel.
- First: 2.6.21.7 on debian sarge
- Second: 2.6.22 same system.
- Onto both i got nfs-user-server and cfsd last versions
- The export file is the same (localhost /opt/nfs (rw, async), stripping
off the async option does not changes anything)
- Mount options are exactly the same.
The problem arises in the very same manner with both nfs and cfsd:
NFS:setattr {
...
...
RPC:call_decode {
return 22;
}
...
return 22;
}
I have tried these kernels:
2.6.16.11 works
2.6.20 works
2.6.21 works
2.6.21.7 works
2.6.22 doesnt work (contiguous to previous version)
2.6.23 doesnt work (same behavior as previous)
2.6.23.9 doesnt work (as above)
2.6.24rc7 doesnt work (as above)
I would really like to do more, client or server side, if you ave any
suggestions.
Can we find out what is the change (doesnt matter if it is a buf or bug
fix) that caused this problem ?
Thanks,
Gianluca
Chuck Lever wrote:
> On Jan 29, 2008, at 3:31 PM, Trond Myklebust wrote:
>
>> On Tue, 2008-01-29 at 20:50 +0100, Gianluca Alberici wrote:
>>
>>> Hello,
>>>
>>> I confirm that i have encountered this same problem (EINVAL on open
>>> (...O | TRUNC) with the following userspace servers:
>>>
>>> - nfs-user-server shipped with debian sarge/etch etc...
>>> - cfsd (crypto file system which is an nfs server)
>>>
>>> I want to underline again that these userspace servers have been woking
>>> perfectly until 2.6.21.7 (which is the last 2.6.21)
>>> Since 2.6.22 the problem came out and it is still present into 2.6.24
>>> rc7 (last i tested). Conclusion: there must have been something that is
>>> changed in 2.6.22 that caused the problem.
>>
>>
>> The only difference between these two dumps are the fact that the first
>> one isn't using the Sun convention for telling NFSv2 servers to set to
>> the current time (see the code in xdr_encode_current_server_time).
>
>
> I thought I saw that on both SETATTRs, but I could be wrong.
>
>> I don't see why this would be new behaviour after 2.6.21. The code for
>> this has been in the NFS client since 2.6.15 at least...
>
>
>
> A mount option is set on one test client, and not the other, perhaps?
>
> --
> Chuck Lever
> chuck[dot]lever[at]oracle[dot]com
> -
> To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
> the body of a message to [email protected]
> More majordomo info at http://vger.kernel.org/majordomo-info.html