From: David Ford <david@linux.com>
To: Pavel Machek <pavel@suse.cz>
Cc: Rik van Riel <riel@conectiva.com.br>,
kernel list <linux-kernel@vger.kernel.org>
Subject: Re: swapoff weird
Date: Sat, 09 Dec 2000 14:41:44 -0800 [thread overview]
Message-ID: <3A32B528.8747332C@linux.com> (raw)
In-Reply-To: <20001209222427.A1542@bug.ucw.cz> <Pine.LNX.4.21.0012091941170.19389-100000@duckman.distro.conectiva> <20001209230615.C5542@atrey.karlin.mff.cuni.cz>
[-- Attachment #1: Type: text/plain, Size: 556 bytes --]
> I can't swapoff. Therefore filesystem is busy (it must be -- kernel
> might be writing to file on it!). And no way to get out of that.
It's busy because some portion of memory is in use. manually kill things as
best you can. this will clean out the swap. once you've gotten all
applications killed cleanly you can forcibly reboot with little damage. this
is pretty much the only way out. we don't have any method (currently) to
turn off a swap file if it's deleted.
Some ideas for the future, /var/run/swap.inode files, some form of sysctl.
-d
[-- Attachment #2: Card for David Ford --]
[-- Type: text/x-vcard, Size: 274 bytes --]
begin:vcard
n:Ford;David
x-mozilla-html:TRUE
url:www.blue-labs.org
adr:;;;;;;
version:2.1
email;internet:david@blue-labs.org
title:Blue Labs Developer
note;quoted-printable:GPG key: http://www.blue-labs.org/david@nifty.key=0D=0A
x-mozilla-cpt:;9952
fn:David Ford
end:vcard
next prev parent reply other threads:[~2000-12-09 23:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-09 21:24 swapoff weird Pavel Machek
2000-12-09 21:41 ` Rik van Riel
2000-12-09 22:06 ` Pavel Machek
2000-12-09 22:41 ` David Ford [this message]
2000-12-09 22:46 ` David Feuer
2000-12-10 7:56 ` Peter Samuelson
2000-12-10 9:10 ` David Feuer
2000-12-15 18:32 ` Pavel Machek
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3A32B528.8747332C@linux.com \
--to=david@linux.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@suse.cz \
--cc=riel@conectiva.com.br \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox