Date: Wed, 31 Oct 2018 06:12:12 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 232800] Processes killed out of swap space Message-ID: <bug-232800-227-MebCNybMhZ@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-232800-227@https.bugs.freebsd.org/bugzilla/> References: <bug-232800-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=232800 --- Comment #3 from Mark Millard <marklmi26-fbsd@yahoo.com> --- (In reply to teksimian from comment #2) See bugzilla's https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206048 for why "swap is filebacked" should be avoided if one wants to avoid deadlocks and such. In particular, see its comments 7 and 8. I'd use a partition as the area for paging/swapping. Also the messages that are are like: Oct 30 23:16:52 host kernel: swap_pager: I/O error - pageout failed; blkno 477,size 69632, error 12 suggests an unreliable page/swap media. And, quoting Trev's reply (and the original question) from a list exchange: QUOTE What does the error swap_pager: indefinite wait buffer: mean? This means that a process is trying to page memory to disk, and the page attempt has hung trying to access the disk for more than 20 seconds. It might be caused by bad blocks on the disk drive, disk wiring, cables, or any other disk I/O-related hardware. If the drive itself is bad, disk errors will appear in /var/log/messages and in the output of dmesg. Otherwise, check the cables and connections. ENDQUOTE It is possible for a some systems to queue up more than the I/O system can process in 20 seconds, even when the I/O is working well (but is relatively slow compared to the work load). -- 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-232800-227-MebCNybMhZ>