public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Christian <evil@g-house.de>
To: linux-kernel@vger.kernel.org
Subject: VFS: Busy inodes after unmount. Self-destruct in 5 seconds.  Have a nice day... (2.6.9-rc3)
Date: Tue, 19 Oct 2004 03:19:45 +0200	[thread overview]
Message-ID: <41746BB1.3030405@g-house.de> (raw)

hi,

during the last days i noticed that my box is using a lot of swap 
memory. it does the same things as every time, perhaps some application 
is leaking memory, i don't know / will examine. then i was away a few 
days and back again i found a partition of mine unmounted. in my syslog 
i noticed this message:

VFS: Busy inodes after unmount. Self-destruct in 5 seconds.  Have a nice 
day...

i *think* this is the message just before unmounting the fs, but the OOM 
event was hours before, as the (slightly edited) log says:

http://www.nerdbynature.de/bits/sheep/2.6.9-rc3/messages.log
(the VFS warning is at the end)

maybe someone could have a look at it and explain to me what happened here?

this is all on debian/unstable, vanilla 2.6.9-rc3 compiled with 3.4.2, 
loop-aes modules loaded. the said fs which was (un)mounted is this:

/dev/hda1 on /data/Media type ext3 
(rw,noexec,nosuid,nodev,noatime,loop=/dev/loop5,\
gpgkey=/root/keys/hda1.gpg,encryption=twofish128)

evil@sheep:~$ free -m
              total   used   free     shared    buffers     cached
Mem:           250   210      40          0          2         67
-/+ buffers/cache:   139     110
Swap:          766   662     103


thank you,
Christian.

-- 
BOFH excuse #312:

incompatible bit-registration operators

                 reply	other threads:[~2004-10-19  1:20 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=41746BB1.3030405@g-house.de \
    --to=evil@g-house.de \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox