re: sosend returning ERESTART

2017-01-19 Thread Rick Macklem
Konstantin Belousov wrote: >On Wed, Jan 18, 2017 at 10:52:02PM +, Rick Macklem wrote: >> Colin Percival wrote: >> >On 01/18/17 02:36, Konstantin Belousov wrote: >> >> On Wed, Jan 18, 2017 at 04:37:40AM +, Colin Percival wrote: >> >>> Thanks, looks like that was exactly it -- if the TCP send

Re: sosend returning ERESTART

2017-01-19 Thread Rick Macklem
Konstantin Belousov wrote: >On Wed, Jan 18, 2017 at 10:52:02PM +, Rick Macklem wrote: >> Colin Percival wrote: >> >On 01/18/17 02:36, Konstantin Belousov wrote: >> >> On Wed, Jan 18, 2017 at 04:37:40AM +, Colin Percival wrote: >> >>> Thanks, looks like that was exactly it -- if the TCP send

Re: sosend returning ERESTART

2017-01-19 Thread Rick Macklem
Konstantin Belousov wrote: >On Wed, Jan 18, 2017 at 10:52:02PM +, Rick Macklem wrote: >> Colin Percival wrote: >> >On 01/18/17 02:36, Konstantin Belousov wrote: >> >> On Wed, Jan 18, 2017 at 04:37:40AM +, Colin Percival wrote: >> >>> Thanks, looks like that was exactly it -- if the TCP send

Re: sosend returning ERESTART

2017-01-18 Thread Konstantin Belousov
On Wed, Jan 18, 2017 at 10:52:02PM +, Rick Macklem wrote: > Colin Percival wrote: > >On 01/18/17 02:36, Konstantin Belousov wrote: > >> On Wed, Jan 18, 2017 at 04:37:40AM +, Colin Percival wrote: > >>> Thanks, looks like that was exactly it -- if the TCP send buffer was full > >>> we would

Re: sosend returning ERESTART

2017-01-18 Thread Rick Macklem
Colin Percival wrote: >On 01/18/17 02:36, Konstantin Belousov wrote: >> On Wed, Jan 18, 2017 at 04:37:40AM +, Colin Percival wrote: >>> Thanks, looks like that was exactly it -- if the TCP send buffer was full >>> we would call sbwait, and if a signal arrived it would return ERESTART. >>> It lo

Re: sosend returning ERESTART

2017-01-18 Thread Rick Macklem
Colin Percival wrote: >On 01/18/17 02:36, Konstantin Belousov wrote: >> On Wed, Jan 18, 2017 at 04:37:40AM +, Colin Percival wrote: >>> Thanks, looks like that was exactly it -- if the TCP send buffer was full >>> we would call sbwait, and if a signal arrived it would return ERESTART. >>> It lo

Re: sosend returning ERESTART

2017-01-18 Thread Colin Percival
On 01/18/17 02:36, Konstantin Belousov wrote: > On Wed, Jan 18, 2017 at 04:37:40AM +, Colin Percival wrote: >> Thanks, looks like that was exactly it -- if the TCP send buffer was full >> we would call sbwait, and if a signal arrived it would return ERESTART. >> It looks like setting the SB_NOI

Re: sosend returning ERESTART

2017-01-18 Thread Konstantin Belousov
On Wed, Jan 18, 2017 at 04:37:40AM +, Colin Percival wrote: > On 01/17/17 02:06, Konstantin Belousov wrote: > > On Tue, Jan 17, 2017 at 04:57:23AM +, Colin Percival wrote: > >> I think I've tracked an NFS problem down to sosend returning ERESTART; it > >> looks like it's easy to work around

Re: sosend returning ERESTART

2017-01-17 Thread Colin Percival
On 01/17/17 02:06, Konstantin Belousov wrote: > On Tue, Jan 17, 2017 at 04:57:23AM +, Colin Percival wrote: >> I think I've tracked an NFS problem down to sosend returning ERESTART; it >> looks like it's easy to work around this, but I'm not sure *why* sosend is >> returning ERESTART... or for

Re: sosend returning ERESTART

2017-01-17 Thread Konstantin Belousov
On Tue, Jan 17, 2017 at 04:57:23AM +, Colin Percival wrote: > I think I've tracked an NFS problem down to sosend returning ERESTART; it > looks like it's easy to work around this, but I'm not sure *why* sosend is > returning ERESTART... or for that matter *how* since I can't find anywhere > in