From owner-freebsd-stable@freebsd.org Mon Aug 17 19:31:07 2015 Return-Path: Delivered-To: freebsd-stable@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 46CD19BC490 for ; Mon, 17 Aug 2015 19:31:07 +0000 (UTC) (envelope-from tundra@tundraware.com) Received: from oceanview.tundraware.com (oceanview.tundraware.com [45.55.60.57]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "oceanview.tundraware.com", Issuer "oceanview.tundraware.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 0ADBA1636 for ; Mon, 17 Aug 2015 19:31:06 +0000 (UTC) (envelope-from tundra@tundraware.com) Received: from [192.168.0.2] (ozzie.tundraware.com [75.145.138.73]) (authenticated bits=0) by oceanview.tundraware.com (8.15.2/8.15.2) with ESMTPSA id t7HJLCEn006634 (version=TLSv1.2 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO) for ; Mon, 17 Aug 2015 19:21:12 GMT (envelope-from tundra@tundraware.com) Message-ID: <55D23423.8090101@tundraware.com> Date: Mon, 17 Aug 2015 14:21:07 -0500 From: Tim Daneliuk User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.8.0 MIME-Version: 1.0 CC: FreeBSD Stable Maling List Subject: Re: Swap Questions References: <55CDE9EE.5090603@tundraware.com> <55CF8E0B.7050608@tundraware.com> In-Reply-To: Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.4.3 (oceanview.tundraware.com [45.55.60.57]); Mon, 17 Aug 2015 19:21:12 +0000 (UTC) X-TundraWare-MailScanner-Information: Please contact the ISP for more information X-TundraWare-MailScanner-ID: t7HJLCEn006634 X-TundraWare-MailScanner: Found to be clean X-TundraWare-MailScanner-From: tundra@tundraware.com X-Spam-Status: No X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Aug 2015 19:31:07 -0000 On 08/17/2015 12:53 PM, Antony Uspensky wrote: > On Sat, 15 Aug 2015, Tim Daneliuk wrote: > >> So -L does fix the problem - sort of. The machine picks up the file as >> additional swap on boot just fine. HWOEVER, when I try to reboot or shut >> down the host, I get a panic telling me some noise about not being able >> to shutdown swap for some reason. > > Try to swapoff (by hands) before shutdown. > Shutdown sequence, I think, unmounts carrying disk before swapping off a carried file. If I am right, -L should be processed on shutdown also. > Just a guess. Yes, that did it. But, isn't this kind of an operational bug? Shouldn't the shutdown logic do the swapoff before the unmount if it sees files being used for swap? i.e. Should I enter this as a bug report? The only reason this matters - and it's a pretty big reason - is for production servers when someone logs in remotely, becomes root, and issued "reboot". The machine hangs at the panic and never comes back ... something you do not see unless you are in a console of some sort ... -- ---------------------------------------------------------------------------- Tim Daneliuk tundra@tundraware.com PGP Key: http://www.tundraware.com/PGP/