From: James Pearson <james-p@moving-picture.com>
To: linux-kernel@vger.kernel.org
Subject: Side effects of a <defunct> kswapd ?
Date: Mon, 26 Jan 2004 12:07:56 +0000 [thread overview]
Message-ID: <4015031C.F7CFA671@moving-picture.com> (raw)
I have number of machines that have <defunct> kswapd processes - I'm
fairly sure what is causing this - it's an issue with autofs v4 and a
'VFS: Busy inodes after unmount. Self-destruct in 5 seconds Have a nice
day...' problem.
There are a few threads about this on the linux-nfs list - e.g.
http://marc.theaimsgroup.com/?t=106332683300004&r=1&w=2
Using autofs v4.1.0 appears to fix this problem.
However, I was wondering what would be the side effects of having a
<defunct> kswapd? - the box _appears_ to keep running fine (running
heavy CPU/memory applications).
Thanks
James Pearson
reply other threads:[~2004-01-26 12:07 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4015031C.F7CFA671@moving-picture.com \
--to=james-p@moving-picture.com \
--cc=linux-kernel@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.