On 26/07/2013 20:37, Artem Belevich wrote:
> On Fri, Jul 26, 2013 at 10:10 AM, Dominic Fandrey wrote:
>
>> Amd exhibits several very strange behaviours.
>>
>> a)
>> During the first start it writes the wrong PID into the pidfile,
>> it however still reacts to SIGTERM.
>>
>> b)
>> After starting it
On 26/07/2013 19:10, Dominic Fandrey wrote:
> On 25/07/2013 12:00, Konstantin Belousov wrote:
>> On Thu, Jul 25, 2013 at 09:56:59AM +0200, Dominic Fandrey wrote:
>>> On 22/07/2013 12:07, Konstantin Belousov wrote:
On Mon, Jul 22, 2013 at 11:50:24AM +0200, Dominic Fandrey wrote:
> ...
>
Michael Tratz wrote:
>
> On Jul 24, 2013, at 5:25 PM, Rick Macklem
> wrote:
>
> > Michael Tratz wrote:
> >> Two machines (NFS Server: running ZFS / Client: disk-less), both
> >> are
> >> running FreeBSD r253506. The NFS client starts to deadlock
> >> processes
> >> within a few hours. It usually
On Sat, Jul 27, 2013 at 04:20:49PM -0400, Rick Macklem wrote:
> Michael Tratz wrote:
> >
> > On Jul 24, 2013, at 5:25 PM, Rick Macklem
> > wrote:
> >
> > > Michael Tratz wrote:
> > >> Two machines (NFS Server: running ZFS / Client: disk-less), both
> > >> are
> > >> running FreeBSD r253506. The
On Jul 27, 2013, at 1:20 PM, Rick Macklem wrote:
> Michael Tratz wrote:
>>
>> On Jul 24, 2013, at 5:25 PM, Rick Macklem
>> wrote:
>>
>>> Michael Tratz wrote:
Two machines (NFS Server: running ZFS / Client: disk-less), both
are
running FreeBSD r253506. The NFS client starts to d
On Jul 27, 2013, at 1:58 PM, Konstantin Belousov wrote:
> On Sat, Jul 27, 2013 at 04:20:49PM -0400, Rick Macklem wrote:
>> Michael Tratz wrote:
>>>
>>> On Jul 24, 2013, at 5:25 PM, Rick Macklem
>>> wrote:
>>>
Michael Tratz wrote:
> Two machines (NFS Server: running ZFS / Client: disk
On Sat, Jul 27, 2013 at 10:33:18AM +0200, Dominic Fandrey wrote:
> On 26/07/2013 19:10, Dominic Fandrey wrote:
> > On 25/07/2013 12:00, Konstantin Belousov wrote:
> >> On Thu, Jul 25, 2013 at 09:56:59AM +0200, Dominic Fandrey wrote:
> >>> On 22/07/2013 12:07, Konstantin Belousov wrote:
> On Mo
On Sat, Jul 27, 2013 at 03:13:05PM -0700, Michael Tratz wrote:
> Let's assume the pid which started the deadlock is 14001 (it will be a
> different pid when we get the results, because the machine has been restarted)
>
> I type:
>
> show proc 14001
>
> I get the thread numbers from that output