From owner-freebsd-bugs@freebsd.org Fri Jan 25 06:43:51 2019 Return-Path: Delivered-To: freebsd-bugs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8BB7514A9B82 for ; Fri, 25 Jan 2019 06:43:51 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 259B56BF02 for ; Fri, 25 Jan 2019 06:43:51 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id D4F4514A9B81; Fri, 25 Jan 2019 06:43:50 +0000 (UTC) Delivered-To: bugs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C355F14A9B80 for ; Fri, 25 Jan 2019 06:43:50 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 563B16BEFF for ; Fri, 25 Jan 2019 06:43:50 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id 9B650196CC for ; Fri, 25 Jan 2019 06:43:49 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id x0P6hnDr009379 for ; Fri, 25 Jan 2019 06:43:49 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id x0P6hnsf009378 for bugs@FreeBSD.org; Fri, 25 Jan 2019 06:43:49 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 235125] Process was killed: out of swap space on gmirror + zfs Date: Fri, 25 Jan 2019 06:43:49 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 11.2-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: gro.dsbeerf.sgub@gordonhartley.com X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 Jan 2019 06:43:51 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D235125 Gordon Hartley changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |gro.dsbeerf.sgub@gordonhart | |ley.com --- Comment #1 from Gordon Hartley --- 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.=