Re: RHEL7 hang (and probably mainline) while copying big files because of subrequests merging(?)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



> On Jul 11, 2016, at 10:15 AM, Alexey Dobriyan <adobriyan@xxxxxxxxx> wrote:
> 
> On Mon, Jul 11, 2016 at 4:52 PM, Weston Andros Adamson <dros@xxxxxxxxxx> wrote:
>> 
>>> On Jul 11, 2016, at 9:47 AM, Alexey Dobriyan <adobriyan@xxxxxxxxx> wrote:
>>> 
>>> On Mon, Jul 11, 2016 at 4:28 PM, Trond Myklebust
>>> <trondmy@xxxxxxxxxxxxxxx> wrote:
>>>> 
>>>>> On Jul 11, 2016, at 08:59, Alexey Dobriyan <adobriyan@xxxxxxxxx> wrote:
>>>>> 
>>>>> We have a customer who was able to reliably reproduce the following hang:
>>>>> (hang itself is rare but there are many machines, so it is not rare)
>>>>> 
>>>>> INFO: task ascp:66692 blocked for more than 120 seconds.
>>>> 
>>>> Why is this being reported here and not to Red Hat? Is the bug reproducible on the upstream kernel?
>>> 
>>> It is not a report per se, more heads up for other folks like CentOS
>>> and other rebuilders.
>>> I checked every NFS commit since 3.10, there seems to be nothing fixing it.
>>> As for testing mainline, I don't know, maybe we can arrange that.
>>> 
>>>  Alexey
>>> 
>> 
>> How have you checked every commit since 3.10 and not tested "mainline"?
>> 
>> I don't get how both can be true. Do you mean you manually inspected each
>> commit? I'm not sure the fix would be so obvious...
> 
> I've looked at commits. If the bug was fixed accidentally, then sorry
> for the noise.

I'm not saying it was fixed accidentally. The nfs client is a complex system and
bugs like this may manifest themselves in many different ways. I don't see how you
can just browse the commits to see if something like this was fixed. The commit message
could be something as simple as "handle error better" or "fix off-by-one calculation" --
how would you know that's the fix to your issue or not? 

A few data points that would be helpful:
 - is this reproducible on upstream kernels
 - more info on the workload- is it buffered IO? direct IO? What sizes are the writes?
 - is this reproducible with tcp transport instead of UDP? I ask this because the
   vast majority of testing of the nfs client is TCP, as there is really no reason
   to use UDP... Probably not the issue, but may be worth checking out.

-dros

--
To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html



[Index of Archives]     [Linux Filesystem Development]     [Linux USB Development]     [Linux Media Development]     [Video for Linux]     [Linux NILFS]     [Linux Audio Users]     [Yosemite Info]     [Linux SCSI]

  Powered by Linux