Andriy Gapon wrote:
> on 30/01/2013 00:44 Andriy Gapon said the following:
> > on 29/01/2013 23:44 Hiroki Sato said the following:
> >> http://people.allbsd.org/~hrs/FreeBSD/pool-20130130.txt
> >> http://people.allbsd.org/~hrs/FreeBSD/pool-20130130-info.txt
> >
> [snip]
> > See tid 100153 (arc
on 30/01/2013 00:44 Andriy Gapon said the following:
> on 29/01/2013 23:44 Hiroki Sato said the following:
>> http://people.allbsd.org/~hrs/FreeBSD/pool-20130130.txt
>> http://people.allbsd.org/~hrs/FreeBSD/pool-20130130-info.txt
>
[snip]
> See tid 100153 (arc reclaim thread), tid 100105 (page
Andriy Gapon wrote:
> on 30/01/2013 01:06 Rick Macklem said the following:
> > Andriy Gapon wrote:
> >> on 29/01/2013 23:44 Hiroki Sato said the following:
> >>> http://people.allbsd.org/~hrs/FreeBSD/pool-20130130.txt
> >>> http://people.allbsd.org/~hrs/FreeBSD/pool-20130130-info.txt
> >>
> >>
on 30/01/2013 01:06 Rick Macklem said the following:
> Andriy Gapon wrote:
>> on 29/01/2013 23:44 Hiroki Sato said the following:
>>> http://people.allbsd.org/~hrs/FreeBSD/pool-20130130.txt
>>> http://people.allbsd.org/~hrs/FreeBSD/pool-20130130-info.txt
>>
>> I recognize here a ZFS ARC deadloc
Andriy Gapon wrote:
> on 29/01/2013 23:44 Hiroki Sato said the following:
> > http://people.allbsd.org/~hrs/FreeBSD/pool-20130130.txt
> > http://people.allbsd.org/~hrs/FreeBSD/pool-20130130-info.txt
>
> I recognize here a ZFS ARC deadlock that should have been prevented by
> r241773
> and its
on 29/01/2013 23:44 Hiroki Sato said the following:
> http://people.allbsd.org/~hrs/FreeBSD/pool-20130130.txt
> http://people.allbsd.org/~hrs/FreeBSD/pool-20130130-info.txt
I recognize here a ZFS ARC deadlock that should have been prevented by r241773
and its MFCs (r242858 for 9, r242859 for 8
Hiroki Sato wrote
in <20130104.023244.472910818423317661@allbsd.org>:
hr> Konstantin Belousov wrote
hr> in <20130102174044.gb82...@kib.kiev.ua>:
hr>
hr> ko> > I might take a closer look this evening and see if I can spot anything
hr> ko> > in the log, rick
hr> ko> > ps: I hope Alan and K
Konstantin Belousov wrote
in <20130102174044.gb82...@kib.kiev.ua>:
ko> > I might take a closer look this evening and see if I can spot anything
ko> > in the log, rick
ko> > ps: I hope Alan and Kostik don't mind being added to the cc list.
ko>
ko> What I see in the log is that the lock cascade r
Rick Macklem wrote
in <1914428061.1617223.1357133079421.javamail.r...@erie.cs.uoguelph.ca>:
rm> Hiroki Sato wrote:
rm> > Hello,
rm> >
rm> > I have been in a trouble about my NFS server for a long time. The
rm> > symptom is that it stops working in one or two weeks after a boot. I
rm> > could no
On Wed, Jan 02, 2013 at 08:24:39AM -0500, Rick Macklem wrote:
> Hiroki Sato wrote:
> > Hello,
> >
> > I have been in a trouble about my NFS server for a long time. The
> > symptom is that it stops working in one or two weeks after a boot. I
> > could not track down the cause yet, but it is reprodu
Hiroki Sato wrote:
> Hello,
>
> I have been in a trouble about my NFS server for a long time. The
> symptom is that it stops working in one or two weeks after a boot. I
> could not track down the cause yet, but it is reproducible and only
> occurred under a very high I/O load.
>
> It did not pani
Hiroki Sato wrote:
> I have been in a trouble about my NFS server for a long time.
> The symptom is that it stops working in one or two weeks after
> a boot ... It did not panic, just stopped working---while it
> responded to ping, userland programs seemed not working ...
> Does anyone see
Hello,
I have been in a trouble about my NFS server for a long time. The
symptom is that it stops working in one or two weeks after a boot. I
could not track down the cause yet, but it is reproducible and only
occurred under a very high I/O load.
It did not panic, just stopped working---wh
13 matches
Mail list logo