badblocks first write a pattern in the disk, and after having finished
that part, it compares data actually written in the disk and checks
for errors, then it's when i get these errors, several allocation
failed messages, and VM killing first syslogd, klogd and in last place
badblocks proccess. Any idea why is this happening, are VM changes in
2.4.10 causing this ? Most of the RAM (320mb) is used by blackblocks,
but almost no swap is used.
Oct 10 23:55:50 fargo kernel: __alloc_pages: 0-order allocation failed
(gfp=0x1d2/0) from c0122ce7
Oct 10 23:55:50 fargo kernel: VM: killing process klogd
Oct 10 23:55:50 fargo kernel: __alloc_pages: 0-order allocation failed
(gfp=0x1d2/0) from c0122ce7
Oct 10 23:55:50 fargo last message repeated 2 times
Oct 10 23:55:50 fargo kernel: __alloc_pages: 0-order allocation failed
(gfp=0xf0/0) from c0132954
Oct 10 23:55:50 fargo kernel: __alloc_pages: 0-order allocation failed
(gfp=0x1d2/0) from c0122ce7
Oct 10 23:55:50 fargo kernel: __alloc_pages: 0-order allocation failed
(gfp=0x1d2/0) from c012349e
Oct 10 23:55:50 fargo kernel: __alloc_pages: 0-order allocation failed
(gfp=0x1d2/0) from c0122ce7
Oct 10 23:55:50 fargo last message repeated 12 times
Oct 10 23:55:50 fargo kernel: VM: killing process badblocks
David Gómez
"The question of whether computers can think is just like the question of
whether submarines can swim." -- Edsger W. Dijkstra
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/