Date: Tue, 27 Dec 2016 23:35:27 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 202420] Unmount Of Swap Files At Reboot Fails Message-ID: <bug-202420-8-bhajE7Nk3C@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-202420-8@https.bugs.freebsd.org/bugzilla/> References: <bug-202420-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=3D202420 Jilles Tjoelker <jilles@FreeBSD.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jilles@FreeBSD.org --- Comment #1 from Jilles Tjoelker <jilles@FreeBSD.org> --- It looks like this situation occurs only with manually added swap devices (including swap files) and not with swap devices added by /etc/rc.d/swap and /etc/rc.d/swaplate, since no writable filesystems are available when /etc/rc.d/swap runs and /etc/rc.d/swaplate removes any "late" devices it ad= ded when the system is shut down. Note that swapoff -a looks at /etc/fstab, not at the currently active swap devices (as would be shown by swapinfo). If additional logic is desired to turn off (some of the) active swap device= s, it should probably be in init(8) (and reboot(8)) or in the kernel, so it executes after all other processes have terminated and the resulting I/O is minimized. It might be useful to non-forcibly unmount tmpfs (or all) mounts first. The actual panic with the usual information may be interesting as well. Normally, a failure to read from swap causes the affected process(es) to cr= ash with SIGBUS (but things might be different for pageable kernel memory such = as pipe buffers and execve arguments, or if a process has been swapped out and= the kernel stack cannot be read back from swap). --=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-202420-8-bhajE7Nk3C>