Hi Gerd,
On Monday 03 January 2005 11:13, Gerd Knorr wrote:
> > (Is 2.6.8-24.10 a 2.6.8 with back-ported fixes from 2.6.10 ?)
>
> Yep, there is a batch of fixes backported to fix the breakouts ...
Is there any chance, that the bugfixfor the
"/tmp-fills-irreversibly-and-cannot-be-unmounted" problem,
that seems to be fixed starting with 2.6.10-rc3-bk10 (and was
positively tested by me in the final 2.6.10) is being backported
to a SuSE 2.6.8-XX.YY host kernel, too?
...and a happy new year!
Armin.
--
--- May the Source be with you! Linux. ---
--- secure eMail: http://www.gnupg.de/ ---
--- Begin Message ---
A little more info...
My method for causing the problem every time (example works under 2.6.9-ck3 and
2.6.10-rc2-bk7)
# mount tmpfs tmp/ -t tmpfs
# TMPDIR=./tmp/ /kernels/non-fix-kill-patched-kernel rootfs=debian.fs
# uml_mconsole .uml/xxx/mconsole cad
# kill -KILL
# umount tmp/
umount: /root/tmp: device is busy
(cad is set to shutdown in the UML's inittab. After sending CAD, it hangs,
which
requires kill)
Under 2.6.10-rc3-bk10 this works fine --the tmpfs mount is unmounted without
problems. Perhaps it's fixed in recent patches. :)
-Chris
---
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
___
User-mode-linux-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
--- End Message ---
--- Begin Message ---
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/ ---
pgp5fQgD0zHQV.pgp
Description: PGP signature
--- End Message ---
pgpkCBr3ge9GY.pgp
Description: PGP signature
