Quote:
Originally Posted by twobob
ah ha  well, one might hope for a but more life then. But not much given your results.
I suppose I should go wiki the total RAM. but I am CERTAIN it is more than a linux webserver I ran for the best part of a decade. Thus it is probably possible to eke out some sort of life. How much, only testing will tell. |
Bet your web server had swap enabled.
My NSLU-2 has 32Mbyte of RAM and it runs Debian armel.
That is 1/4 the RAM of the smallest amount provided with any Kindle model and 1/8 the RAM in the K4.
Quote:
Originally Posted by pepijndevos
First time it happened while dd/mkfs'ing the file, later while downloading/extracting the Arch rootfs.
|
Although the O.P. does not mention **what** file system they where trying to make, it most likely has the same behavior as ext2/ext3 creation.
When RAM constrained, you will find first that you can create an ext2 file system and then add a journal (making it an ext3) but you can not initially create an ext3 file system.
Plus, once you trigger that error, it is very likely that the OOM killer has run.
Translation: No other observations are relevant until after the next complete re-boot.