On Tuesday, 20 April 2021 06:19:25 EDT J. Hannken-Illjes wrote:
> As Manuel said this will block forever. Please try the attached diff
> that should prevent waits on negative or zero ticks.
>
> --
> J. Hannken-Illjes - hann...@eis.cs.tu-bs.de - TU Braunschweig (Germany)
Thanks! I can confirm
> On 19. Apr 2021, at 19:59, Andrew Parker wrote:
>
> On Monday, 19 April 2021 13:28:07 EDT Robert Elz wrote:
> > Date:Sun, 18 Apr 2021 18:58:56 +
> > From:Andrew Parker
> > Message-ID: <2245776.bZt9KSGgi3@t470s.local>
> >
> > | Does anyone else have a working
On Mon, Apr 19, 2021 at 05:59:39PM +, Andrew Parker wrote:
> [...]
>
> Oops. I completely misread how the return value of l2arc_write_interval is
> used so that patch doesn't make any sense. But adding the printf suggested
> earlier results in this just after boot:
>
>
> [14.600107]
On Monday, 19 April 2021 13:28:07 EDT Robert Elz wrote:
> Date:Sun, 18 Apr 2021 18:58:56 +
> From:Andrew Parker
> Message-ID: <2245776.bZt9KSGgi3@t470s.local>
>
> | Does anyone else have a working L2ARC?
>
> Sorry, don't even know what that is, and don't
Date:Sun, 18 Apr 2021 18:58:56 +
From:Andrew Parker
Message-ID: <2245776.bZt9KSGgi3@t470s.local>
| Does anyone else have a working L2ARC?
Sorry, don't even know what that is, and don't (currently anyway) use zfs,
but:
| - interval = hz *
> On 18. Apr 2021, at 20:58, Andrew Parker wrote:
>
> Hi,
>
> While trying to setup an L2ARC on my amd64 Xen dom0, I noticed that almost no
> data was feeding in to the cache. The counters in kstat.zfs.misc.arcstats.l2*
> indicate the l2arc feed process must be stuck somewhere.
Which counters
