Re: WIerdness when creating Loop-aes file?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Wed, March 8, 2006 21:00, Jan Johansson wrote:
> Mar  7 19:20:41 cookiemonster kernel: Swap cache: add 637, delete 530,
> find 111/130, race 0+0 Mar  7 19:20:41 cookiemonster kernel: Out of
> Memory: Killed process 29237 (mysqld).

> Mar  7 19:21:09 cookiemonster kernel: Swap cache: add 637, delete 530,
> find 111/130, race 0+0 Mar  7 19:21:09 cookiemonster kernel: Out of
> Memory: Killed process 26106 (apache2).

hm, /me fails to see the relation to loop-aes here. sure, loading another
module alters the kernel in some way, and accessing a loop-device could
have an impact on the VM - but this just looks like an "ordinary" OOM
error.
at what stage did the error occur?

> Running Debian 3.1
> cookiemonster:~/VMware# uname -a
> Linux cookiemonster 2.6.8-2-686 #1 Tue Aug 16 13:22:48 UTC 2005 i686

hm, have you
1) tried a recent (vanilla) kernel?
2) searched debian/bugs for any OOM issues?

is this reproducible in any way?
if yes, did the recent kernel help? if not, you've got reason to Cc: LKML :)

cheers,
Christian.
-- 
make bzImage, not war


-
Linux-crypto:  cryptography in and on the Linux system
Archive:       http://mail.nl.linux.org/linux-crypto/


[Index of Archives]     [Kernel]     [Linux Crypto]     [Gnu Crypto]     [Gnu Classpath]     [Netfilter]     [Bugtraq]
  Powered by Linux