Date: Tue, 22 May 2018 15:29:24 +0300 From: Slawa Olhovchenkov <slw@zxy.spb.ru> To: Steve Wills <swills@FreeBSD.org> Cc: Alexander Leidinger <Alexander@leidinger.net>, current@freebsd.org Subject: Re: Deadlocks / hangs in ZFS Message-ID: <20180522122924.GC1954@zxy.spb.ru> In-Reply-To: <fa263af4-9bf7-88f8-8d23-21456daf7960@FreeBSD.org> References: <20180522101749.Horde.Wxz9gSxx1xArxkYMQqTL0iZ@webmail.leidinger.net> <fa263af4-9bf7-88f8-8d23-21456daf7960@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, May 22, 2018 at 08:17:00AM -0400, Steve Wills wrote:
> I may be seeing similar issues. Have you tried leaving top -SHa running
> and seeing what threads are using CPU when it hangs? I did and saw pid
> 17 [zfskern{txg_thread_enter}] using lots of CPU but no disk activity
> happening. Do you see similar?
Can you try https://reviews.freebsd.org/D7538 and report?
> On 05/22/18 04:17, Alexander Leidinger wrote:
> > Hi,
> >
> > does someone else experience deadlocks / hangs in ZFS?
> >
> > What I see is that if on a 2 socket / 4 cores -> 16 threads system I do
> > a lot in parallel (e.g. updating ports in several jails), then the
> > system may get into a state were I can login, but any exit (e.g. from
> > top) or logout of shell blocks somewhere. Sometimes it helps to CTRL-C
> > all updates to get the system into a good shape again, but most of the
> > times it doesn't.
> >
> > On another system at the same rev (333966) with a lot less CPUs (and AMD
> > instead of Intel), I don't see such a behavior.
> >
> > Bye,
> > Alexander.
> >
> _______________________________________________
> freebsd-current@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20180522122924.GC1954>