Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 26 May 2017 21:22:58 +0000
From:      bugzilla-noreply@freebsd.org
To:        freebsd-fs@FreeBSD.org
Subject:   [Bug 219457] ZFS ARC eviction & system hangup
Message-ID:  <bug-219457-3630-AzrSYwR622@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-219457-3630@https.bugs.freebsd.org/bugzilla/>
References:  <bug-219457-3630@https.bugs.freebsd.org/bugzilla/>

next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D219457

--- Comment #12 from Anton Sayetsky <vsasjason@gmail.com> ---
(In reply to Fabian Keil from comment #6)

> The procstat output suggests that you might be using geli for the swap de=
vice.
Yes, you're right. I'm using GELI (AES-256-XTS/SHA256/onetime) over gmirror=
 of
2 gpt partitions.

> This is known to cause deadlocks under memory pressure:
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D209759
Disabled GELI swap & stopped relevant gmirror -- still got ARC eviction aft=
er
running tar...

> You could reduce vfs.zfs.deadman_synctime_ms to more quickly get
a panic when the system becomes unresponsive.
Unfortunately, I cannot see any panics (and thus, stack traces). System just
hangs w/o any output to logs or console, and all that I can do - reset or p=
ower
cycle through IPMI interface. I'm thinking about compiling kernel with KDB/=
DDB
and collecting coredump with NMI.

> It would probably help to see the counters in vm_cnt.
Attached relevant sysctl output & similar diagnostics as before, but w/o sw=
ap.

--=20
You are receiving this mail because:
You are the assignee for the bug.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-219457-3630-AzrSYwR622>