From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from psmtp.com (na3sys010amx179.postini.com [74.125.245.179]) by kanga.kvack.org (Postfix) with SMTP id A63846B0044 for ; Mon, 9 Apr 2012 14:40:49 -0400 (EDT) Received: by yenm8 with SMTP id m8so2560608yen.14 for ; Mon, 09 Apr 2012 11:40:48 -0700 (PDT) Date: Mon, 9 Apr 2012 11:40:32 -0700 (PDT) From: Hugh Dickins Subject: Re: swapoff() runs forever In-Reply-To: <4F82B6ED.2010500@nod.at> Message-ID: References: <4F81F564.3020904@nod.at> <4F82752A.6020206@openvz.org> <4F82B6ED.2010500@nod.at> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-mm@kvack.org List-ID: To: Richard Weinberger Cc: Konstantin Khlebnikov , "linux-kernel@vger.kernel.org" , "linux-mm@kvack.org" , "paul.gortmaker@windriver.com" , Andrew Morton On Mon, 9 Apr 2012, Richard Weinberger wrote: > Am 09.04.2012 07:35, schrieb Konstantin Khlebnikov: > > Richard Weinberger wrote: > >> Hi! > >> > >> I'm observing a strange issue (at least on UML) on recent Linux kernels. > >> If swap is being used the swapoff() system call never terminates. > >> To be precise "while ((i = find_next_to_unuse(si, i)) != 0)" in try_to_unuse() > >> never terminates. > >> > >> The affected machine has 256MiB ram and 256MiB swap. > >> If an application uses more than 256MiB memory swap is being used. > >> But after the application terminates the free command still reports that a few > >> MiB are on my swap device and swappoff never terminates. > > > > After last tmpfs changes swapoff can take minutes. > > Or this time it really never terminates? > > I've never waited forever. ;-) Your lack of dedication is disappointing. > Once I've waited for >30 minutes. > > I don't think that it's related to tmpfs because it happens > also while shutting down the system after all filesystems have been unmounted. Like you I'd assume that it is really was going to be forever, rather than swapoff just being characteristically slow: a few MiB left on swap shouldn't take long to get off. I've not seen any such issue in recent months (or years), but I've not been using UML either. The most likely cause that springs to mind would be corruption of the vmalloc'ed swap map: that would be very likely to cause such a hang. You say "recent Linux kernels": I wonder what "recent" means. Is this something you can reproduce quickly and reliably enough to do a bisection upon? Thanks, Hugh -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/ Don't email: email@kvack.org