From owner-freebsd-i386@freebsd.org Fri Jan 22 22:49:05 2016 Return-Path: Delivered-To: freebsd-i386@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id EF7BCA8E8D6 for ; Fri, 22 Jan 2016 22:49:05 +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 mx1.freebsd.org (Postfix) with ESMTPS id DAD991965 for ; Fri, 22 Jan 2016 22:49:05 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u0MMn5BN075559 for ; Fri, 22 Jan 2016 22:49:05 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-i386@FreeBSD.org Subject: [Bug 206492] System hangs on huge disk activity Date: Fri, 22 Jan 2016 22:49:06 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.2-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: markmi@dsl-only.net X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-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-i386@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: I386-specific issues for FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 22 Jan 2016 22:49:06 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D206492 Mark Millard changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |markmi@dsl-only.net --- Comment #2 from Mark Millard --- If you use a swapfile on a file-system/partition that gets a mix of other IO then see Bug 206048 - 11.0-CURRENT -r293227 (and others) arm (rpi2/BeagleBone Black) amd64 etc: swapfile usage hangs; swap partition works for a problem that may apply to 10.x as well when using things like: file=3D/var/spool/swap/swapfile file=3D/swap0 --unless those files are on their own file systems/partitions not used for other (used) files. It may be worth testing if the involved 10.x context(s) hang before settlin= g on this sort of placement of the file. One of the comments suggested a command like: stress -d 2 -m 3 --vm-keep was sufficient to show the problem on at least 11.0-CURRENT amd64 contexts.= I guess that command is from the port sysutils/stress . It would actually be good to have 10.x comments in Bug 206048 reporting how such testing went if someone tries it. --=20 You are receiving this mail because: You are on the CC list for the bug.=