Re: [Nbd] NBD, DISCARD/TRIM

[Paul Clements <paul.clements@...856...>]

On Thu, Mar 28, 2013 at 12:36 PM, folkert <folkert@...421...> wrote:
>> Very good. Would it be at all possible to try the attached patch,
>> which includes some additional debugging information, so that we can
>> see why this is happening?
>
> It is unclear which process is the trigger:
>
> [   71.078260] got ERESTARTSYS: sig:17 code:262145 sender:2853

OK, so sig 17 is SIGCHLD??? This is weird. I'm not that familiar with
latest upstream nbd-client, but is there maybe some fork or thread
that is happening? Is this ps listing all threads (perhaps 2853 is a
sub-thread of nbd-client?).

> root      2852     1  3 17:31 ?        00:00:03 nbd-client 172.16.86.1 12342 /dev/nbd0
> root      2854     2 46 17:31 ?        00:00:43 [nbd0]
>
> I would almost say that it is something in nbd-client itself?

Agreed...it certainly looks that way...

I'll look at latest nbd-client source and see if anything looks
suspicious, but in the meantime if anyone more familiar with that code
can chime in, that would be great.

--
Paul