Hi,
I got the VM error "VM: do_try_to_free_pages failed for mongo_read..."
and then I couldn't log into the system, when stress testing
reiserfs+raid0 setup on a 2.2.18 box using the reiserfs benchmark
mongo.sh. The problem was reporduceable on each run of mongo.sh.
./mongo.sh reiserfs /dev/md0 /mnt/testfs raid0-rfs 3
Thinking the raid code might cause the problem, I tested on reiserfs
only, but I got the same error message. Later, I found the same
problem running mongo.sh on an ext2 partition (stock kernel without
any patches).
I guess this problem is not reiserfs specific. What can I do now to
solve the problem?
Here is the hardware configuration of my test box:
PIII 600, 256M, Adaptec AIC-7896 SCSI controller, two Quantum SCSI
disks.
Regards,
--
Wenzhuo
This is a bad RAM problem, or insufficient RAM (slightly less possible)
On Tue, 6 Feb 2001, Wenzhuo Zhang wrote:
>
> Hi,
>
> I got the VM error "VM: do_try_to_free_pages failed for mongo_read..."
> and then I couldn't log into the system, when stress testing
> reiserfs+raid0 setup on a 2.2.18 box using the reiserfs benchmark
> mongo.sh. The problem was reporduceable on each run of mongo.sh.
>
> ./mongo.sh reiserfs /dev/md0 /mnt/testfs raid0-rfs 3
>
> Thinking the raid code might cause the problem, I tested on reiserfs
> only, but I got the same error message. Later, I found the same
> problem running mongo.sh on an ext2 partition (stock kernel without
> any patches).
>
> I guess this problem is not reiserfs specific. What can I do now to
> solve the problem?
>
> Here is the hardware configuration of my test box:
> PIII 600, 256M, Adaptec AIC-7896 SCSI controller, two Quantum SCSI
> disks.
>
> Regards,
>
> This is a bad RAM problem, or insufficient RAM (slightly less possible)
Unlikely to be either of those. My guess is its the reiserfs stuff interacting
with the 2.2 VM code badly. 2.2.19pre8 fixes the VM behaviour in the general
case and that might well make it handle the extra vm pressure reiserfs causes
Certainly I'd try 2.2.19pre3 or higher. I don't think its hardware or
reiserfs problems
Wenzhuo Zhang wrote:
>
> Hi,
>
> I got the VM error "VM: do_try_to_free_pages failed for mongo_read..."
> and then I couldn't log into the system, when stress testing
> reiserfs+raid0 setup on a 2.2.18 box using the reiserfs benchmark
> mongo.sh. The problem was reporduceable on each run of mongo.sh.
>
> ./mongo.sh reiserfs /dev/md0 /mnt/testfs raid0-rfs 3
>
> Thinking the raid code might cause the problem, I tested on reiserfs
> only, but I got the same error message. Later, I found the same
> problem running mongo.sh on an ext2 partition (stock kernel without
> any patches).
>
> I guess this problem is not reiserfs specific. What can I do now to
> solve the problem?
>
> Here is the hardware configuration of my test box:
> PIII 600, 256M, Adaptec AIC-7896 SCSI controller, two Quantum SCSI
> disks.
>
> Regards,
> --
> Wenzhuo
Honestly, the best thing to do is to upgrade to 2.4.1. VM on 2.2.recent is
not in good condition, and reiserfs exacerbates it.
Hans
On Tue, Feb 06, 2001 at 11:22:22AM +0000, Alan Cox wrote:
> > This is a bad RAM problem, or insufficient RAM (slightly less possible)
>
> Unlikely to be either of those. My guess is its the reiserfs stuff interacting
> with the 2.2 VM code badly. 2.2.19pre8 fixes the VM behaviour in the general
> case and that might well make it handle the extra vm pressure reiserfs causes
>
But I got the same VM error when I was testing on an ext2 partition
under stock kernel (without any external patches).
> Certainly I'd try 2.2.19pre3 or higher. I don't think its hardware or
> reiserfs problems
>
>
>
OK, I'll give 2.2.19pre8 a try.
--
Wenzhuo
> > with the 2.2 VM code badly. 2.2.19pre8 fixes the VM behaviour in the general
> > case and that might well make it handle the extra vm pressure reiserfs causes
> >
> But I got the same VM error when I was testing on an ext2 partition
> under stock kernel (without any external patches).
If the program does a lot of allocation and page dirtying you would see it
on 2.2.18 with any fs. Journalling fs's just make it more likely to trigger.
Andrea fixed this in 2.2.19pre3