On Tue, 2002-10-29 at 01:10, Heinz J . Mauelshagen wrote: > > Gregory, > > as Jon already thought, this seems to be a flaw in the VM subsystem. > > The ksymoops you provided shows that, because it fails in vmalloc when > lvm_snapshot_alloc_hash_table() tries to allocated virtual memory for the > copy-on-write exeception table it needs to track the changes which happen > to the original logical volume. > > Is there any chance to prove that by running the system with less than 2GB > of memory and _without_ high memory support for a test run? > > Regards, > Heinz -- The LVM Guy -- Actually, yes, I can run this on several other smaller-memory systems. I've got a machine I've been working on setting up that's 2GB exactly, and several others running 2.4.19 & LVM 1.0.5 with less than 1GB of ram. However, I've not had any of these systems produce errors like these. I can run the 2GB system with and without high memory support and try to induce a similar failure. Are there any specific tests you'd like me to run on this other system, in case I can't induce an Oops on it? Thanks, Gregory -- Gregory K. Ade <gkade@bigbrother.net> http://bigbrother.net/~gkade OpenPGP Key ID: EAF4844B keyserver: pgpkeys.mit.edu
Attachment:
signature.asc
Description: This is a digitally signed message part
