lkml.org 
[lkml]   [2018]   [Jul]   [26]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
SubjectRe: [BUG BISECT] NFSv4 client fails on Flush Journal to Persistent Storage
From
Date


> On Jul 26, 2018, at 4:46 AM, Krzysztof Kozlowski <krzk@kernel.org> wrote:
>
> On 25 July 2018 at 16:31, Chuck Lever <chuck.lever@oracle.com> wrote:
>>
>>
>>> On Jul 25, 2018, at 9:27 AM, Krzysztof Kozlowski <krzk@kernel.org> wrote:
>>>
>>> On 18 June 2018 at 18:20, Chuck Lever <chuck.lever@oracle.com> wrote:
>>>>
>>>> The extra serialization appears to have a reproducible performance
>>>> impact on RDMA, which no longer takes the reserve_lock when allocating
>>>> a slot.
>>>>
>>>> I could put an xprt_alloc_xid call in xprt_alloc_slot, but that would
>>>> only work for socket-based transports. Would it be OK if RDMA had its
>>>> own XID allocation mechanism?
>>>
>>> Hi,
>>>
>>> On recent next the issue appeared again. My boards with NFSv4 root
>>> timeout on 80% of boots. This time my NFS server is faster - Pi3 B+
>>> :).
>>>
>>> Is this know? Should I start long bisect or maybe you can point me to
>>> possible causes?
>>
>> Hi Krzysztof, I don't know of any recent changes. Bisecting would be
>> a good place to start.
>
> Hi,
>
> That was my mistake because of missing part of NFS server
> configuration on new board. I tested again recent releases and current
> linux-next and everything works fine.
>
> Sorry for the noise.

Thanks for the update.


--
Chuck Lever



\
 
 \ /
  Last update: 2018-07-27 03:49    [W:0.059 / U:0.752 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site