Date: Fri, 25 Jan 2019 06:43:49 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 235125] Process was killed: out of swap space on gmirror + zfs Message-ID: <bug-235125-227-rAIIquIK8l@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-235125-227@https.bugs.freebsd.org/bugzilla/> References: <bug-235125-227@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=3D235125 Gordon Hartley <gro.dsbeerf.sgub@gordonhartley.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |gro.dsbeerf.sgub@gordonhart | |ley.com --- Comment #1 from Gordon Hartley <gro.dsbeerf.sgub@gordonhartley.com> --- I think this needs the 'importance'/severity needs major escalation because I've had it kill ssh sessions where I couldn't complete backups via scp, and it's killing the ssh session I'm su'd in when trying to understand the prob= lem. This has the potential to be one of those 'affects some people' that may transform into a case that takes out a massive amount of infrastructure that everyone depends on, and you can't remote in to solve the problem type scenarios... The result of this problem could be catastrophic in the wrong environment.= =20 My fear would be people upgrade production. Everything appears to be running smoothly for while, so safety is assumed, then whatever scenario that trigg= ers this behaviour occurs and you can't remote in to save the system, because t= he system keeps killing processes involving humans trying to save the system f= rom itself because the system veto's resource allocation for itself. --=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-235125-227-rAIIquIK8l>