NASLite Network Attached Storage

I've been running NASLite-2 CDD for just under two months now and I must say that I am quite happy with it. That said however, one issue which I do feel is a bit of a bugbear is the drive recovery after an unscheduled shutdown (aka power failure/brown out). As I understand it e2fsk gets run at startup in a more thorough mode than it does when starting up after the server has been shut down properly. I guess this wouldn't ordinarily be a problem except for the case that it fails on the 320GB and 300GB drives in my configuration (see my signature) and hence these drives don't get mounted. After much head scratching I discovered that the '__alloc_pages: 0-order allocation failed (gfp=0x1d2/0)' comment in the system logs means that e2fsk has run out of memory and has been terminated prematurely. My solution to this is to physically move the drives to another machine with more memory and run NASLite-2 CDD on that machine to get it to 'clear' the drives. Given that this has happened to me at least a half dozen times since I started running NASLite you can imagine that I'm not too happy about it (and the fact that the Basic System Requirements for NASLite-2 CDD lists 64MB as sufficient). I have installed a UPS to handle most cases (it doesn't handle brown outs successfully though). I'm hoping to get another 32MB of RAM to take my total up to 96MB but it's quite difficult to find RAM for old Pentiums. Anyway, my question is, is there anyway around this and how would I calculate the RAM I need for e2fsk to run for a particular drive size?

64M of ram is a minimum and therefore insufficient for analysis and repair of a filesystem of that size. The problem can easily be resolved by adding more RAM.

I understand that but since drive recovery is one of the features of NASLite-2 product can't you provide some guidance as to how much RAM is required for this feature to function properly for a given drive size?

There was a post here somewhere that discussed this in more detail. Not sure what it was called. Basically, it depends on the number of files you have. On page 4 of the manual there is a blurb about large drives and more ram. 128M should solve your problem.