Date: Fri, 22 Jan 2016 22:35:27 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bug 181565] [swap] Problem with vnode-backed swap space. Message-ID: <bug-181565-3630-F9vx0vA5UY@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-181565-3630@https.bugs.freebsd.org/bugzilla/> References: <bug-181565-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=3D181565 Mark Millard <markmi@dsl-only.net> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |markmi@dsl-only.net --- Comment #4 from Mark Millard <markmi@dsl-only.net> --- FYI: 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. (A swap file by itself on its own partition/file system= has not shown the problem. Mixing with other IO from the same file system/parti= tion does. But only so much information can be put in a subject line.) 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 the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-181565-3630-F9vx0vA5UY>