All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Armin M. Warda" <Armin.Warda@ePost.De>
To: user-mode-linux-devel@lists.sourceforge.net
Subject: [uml-devel] UML fills /tmp irreversibly (2.6.9-bb4 on SuSE 9.2)
Date: Tue, 14 Dec 2004 09:58:52 +0100	[thread overview]
Message-ID: <200412140958.58402.Armin.Warda@ePost.De> (raw)

[-- Attachment #1: Type: text/plain, Size: 1055 bytes --]

  Hi,

running UML 2.6.9-bb4 on SuSE Professional 9.2 with host kernel SuSE 
2.6.8-24.5 (with SKAS) I notice the strange effect, that /tmp keeps 
filling irreversibly.

/tmp space is not only consumed as long as UMLs are running (as seen 
with "lsof|grep deleted"), /tmp space is _not_released_ when the UMLs 
are gone. When all UMLs are gone "lsof|grep deleted" returns nothing, 
but "df /tmp" still shows the allocations. In this situation attempts 
to umount (or remount ro) the /tmp fail, even in single user mode.

The only way to recover from such a /tmp full situation is to reboot 
the host (then unmount of /tmp and the rootfs fail during shutdown, 
which causes fscks at the reboot...)

I tried out different filesystem types for /tmp: reiserfs 3.6, ext3 
and tmpfs, no difference.

Anybody seen such behaviour before?

I suppose this must be a bug of the _host_ kernel, not of the UML 
kernel. Do you agree?

  Armin.

-- 
   --- May the Source be with you! Linux. ---
   --- secure eMail: http://www.gnupg.de/ ---

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

             reply	other threads:[~2004-12-14  8:59 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-14  8:58 Armin M. Warda [this message]
2004-12-16 14:50 ` [uml-devel] Re: UML fills /tmp irreversibly (2.6.9-bb4 on SuSE 9.2) Armin M. Warda
     [not found] ` <20041216183604.GB24982@bytesex>
     [not found]   ` <200412162013.21197.blaisorblade_personal@yahoo.it>
2004-12-30 14:20     ` Armin M. Warda
2004-12-30 16:14       ` Christopher S. Aker
2004-12-31 11:22         ` Armin M. Warda
2005-01-01 20:10           ` Christopher S. Aker
2005-01-02  9:25             ` Armin M. Warda
2005-01-03 14:07               ` Armin M. Warda
2005-01-03 10:13       ` Gerd Knorr
2005-01-03 11:49         ` Armin M. Warda
     [not found]           ` <20050103133412.GA25262@bytesex>
2005-01-03 14:31             ` Armin M. Warda
2005-01-04 11:59               ` Gerd Knorr
2005-01-04 14:05                 ` Armin M. Warda
2005-01-04 14:39                   ` Gerd Knorr
2005-01-04 15:33                     ` Christopher S. Aker
2005-01-05 11:28                       ` Gerd Knorr
2005-01-05 14:22                         ` Armin M. Warda
2005-01-07 11:20                           ` Gerd Knorr
2005-01-04 14:52                   ` Michael Richardson
2005-01-08 12:15               ` Paolo Giarrusso
2005-01-10 13:10                 ` Gerd Knorr
     [not found] ` <200501101450.32169.Armin.Warda@gmx.de>
     [not found]   ` <20050111165848.GA20592@bytesex>
2005-01-12 15:53     ` Armin M. Warda
2005-01-17 15:26       ` Gerd Knorr

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=200412140958.58402.Armin.Warda@ePost.De \
    --to=armin.warda@epost.de \
    --cc=Armin.Warda@gmx.De \
    --cc=user-mode-linux-devel@lists.sourceforge.net \
    /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.