ReadyNAS NV RAIDiator 4.1.6: Alloc null skbuff in pool

I see you've indicated in another post you are running a 3rd party RAM module. What happens if you put the stock memory module back in?

mdgm wrote:
I see you've indicated in another post you are running a 3rd party RAM module. What happens if you put the stock memory module back in?

I bought from the approved hardware list & tested it thoroughly (though not recently).

Anyhow, I can try that, but one variable is going to be that I'm running 1 GB and it came with one of a smaller size (256 or 512 - I forget). Is your thinking that the size is an issue? Or do you suspect the 3rd party RAM is defective?

BTW, I've been running and checking MD5's on my data and copying lots of it around (with the NAS running stably, the whole time), so I feel it's unlikely that the RAM is defective. It could be, but in my experience, bad RAM usually causes data errors before it starts to cause any sort of instability.

The main reason I asked is that I'm just wondering if it indicates a configuration problem that might be affecting my performance.

It might not be anything to do with the memory if you added it a long time ago (though memory can and does fail sometimes so it'd be a good idea to run the memory test a few times). More recently RAM manufacturers having been messing with these modules under the hood rendering them incompatible e.g. changes in production of the Kingston module have rendered newer versions with the same module number incompatible.

You could have a hardware problem with one of your devices or cabling. Do you see any errors in the error count under Network > Interfaces?

I can find one thread with a possibly similar error (though it's quite old, don't revive it, keep your posts in this thread): http://www.readynas.com/forum/viewtopic.php?f=7&t=5780&start=0

I guess it may be possible that one of your devices doesn't support jumbo frames. Have you checked to make sure the NIC in your PC supports jumbo frames and that your router/switch does? If you disable jumbo frames do you still get the issue?

Also make sure you are using good Cat5e cables or newer.

You really want to eliminate a hardware problem before going and messing with configuration files (it's also a good idea to backup the configuration file before making a change in case you mess things up and don't remember what the old settings were).

Thanks for the help, but I think most of the possibilities you listed would have other, more severe symptoms, as well.

My search did not turn up that post. Though I guess I did my search on google, thinking it might be a generic linux kernel thing, and got just one hit that happened to be on this site. I then assumed that was probably the only hit on the site and didn't bother to try the site's search feature.

yoh-dah's reply is really along the lines of what I expected. I was hoping someone could either advise of a bottleneck I'm probably hitting, or point me towards a config change (e.g. increasing the number of buffers in the pool).

Anyway, it's not really a big deal.

While it may be unlikely that they are the cause, it's a good idea to check them first. You don't want to mess unnecessarily with config under the hood.

Was there any resolution on this? I'm seeing this on my old x600 (originally purchased from Infrant...). Here's a clip from /var/log/syslog:

Sep 20 12:34:30 raid1-x600 kernel: Alloc null skbuff in pool (1)
Sep 20 12:34:30 raid1-x600 kernel: Alloc null skbuff in pool (2)
Sep 20 12:34:30 raid1-x600 kernel: Alloc null skbuff in pool (3)
Sep 20 12:34:30 raid1-x600 kernel: Alloc null skbuff in pool (4)
Sep 20 12:34:30 raid1-x600 kernel: Alloc null skbuff in pool (5)
Sep 20 12:34:30 raid1-x600 kernel: Alloc null skbuff in pool (6)
Sep 20 12:34:30 raid1-x600 kernel: Alloc null skbuff in pool (7)
Sep 20 12:34:30 raid1-x600 kernel: Alloc null skbuff in pool (8)
Sep 20 12:34:30 raid1-x600 kernel: Alloc null skbuff in pool (9)
Sep 20 12:34:30 raid1-x600 kernel: Alloc null skbuff in pool (10)
Sep 20 12:34:30 raid1-x600 kernel: Alloc null skbuff in pool (11)
Sep 20 12:34:30 raid1-x600 kernel: Alloc null skbuff in pool (12)
Sep 20 12:34:30 raid1-x600 kernel: Alloc null skbuff in pool (13)
Sep 20 12:34:30 raid1-x600 kernel: Alloc null skbuff in pool (14)
Sep 20 12:34:30 raid1-x600 kernel: Alloc null skbuff in pool (15)
Sep 20 12:34:30 raid1-x600 kernel: Alloc null skbuff in pool (0)
Sep 20 12:34:30 raid1-x600 kernel: Alloc null skbuff in pool (1)
Sep 20 12:34:30 raid1-x600 kernel: Alloc null skbuff in pool (2)
Sep 20 12:34:30 raid1-x600 kernel: Alloc null skbuff in pool (3)
Sep 20 12:34:30 raid1-x600 kernel: Alloc null skbuff in pool (4)
Sep 20 12:34:30 raid1-x600 kernel: Alloc null skbuff in pool (5)
Sep 20 12:34:30 raid1-x600 kernel: Alloc null skbuff in pool (6)
Sep 20 12:34:30 raid1-x600 kernel: Alloc null skbuff in pool (7)

Performance is taking a hit as well... Any suggestions or things to look at?

Thanks,
/jamie

Is Jumbo Frames enabled. What version of RAIDiator?