Date: Fri, 22 Jan 2016 22:49:06 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 206492] System hangs on huge disk activity Message-ID: <bug-206492-8-XgXPKSE2JH@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-206492-8@https.bugs.freebsd.org/bugzilla/> References: <bug-206492-8@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=206492 Mark Millard <markmi@dsl-only.net> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |markmi@dsl-only.net --- Comment #2 from Mark Millard <markmi@dsl-only.net> --- 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=/var/spool/swap/swapfile file=/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 settling 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. -- 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-206492-8-XgXPKSE2JH>