kern.maxfiles limit exceeded by uid 0

[nunya]

Not long ago, I upgraded from 9.1 to 9.2. Since then, I keep getting this error. The FreeNAS system will become unresponsive after several hours / days. I can't establish any rhyme, reason, or pattern. The only way to recover is to reboot.

It's a standalone server I built last year. I ordinarily run it headless, but put a monitor and keyboard on for troubleshooting (couldn't connect via http or ssh).

Any idea what is causing this error? Should I just go back to 9.1?

Thanks

 

[Yatti420]

Are you running plugins? Plex? More specs please..

 

[nunya]

No plugins or anything special. Very lightly used 1TB system on a home network.

 

[Yatti420]

I noticed its 9.2.1 Beta.. Have you enabled autotune or done any kind of tuning at all?? It's akso 4gb - are you running ZFS?

 

[nunya]

Yes, autotune is enabled. It seems like it kept all of my settings in tact. Yes, I'm using ZFS. It hasn't been a problem up until the upgrade

 

[dlavigne]

How much memory in this system? Does removing the autotune settings fix the problem? Are you able to add more RAM?

 

[nunya]

I did not remove the autotune setting. However, it's done it twice today after working fine for several days. I can't afford more RAM right now. I haven't had much work lately. I did go back to 9.2.0 to see if that makes a difference. Not sure how I wound up with the beta. I should have noticed that in the file name.

 

[nunya]

Going back to 9.2.0 cured my ills. Thanks anyway for the help.

 

[Yatti420]

You need more ram.. Alot more for ZFS via FreeNAS..

 

[nunya]

You need more ram.. Alot more for ZFS via FreeNAS..

Not in the budget right now. Everything is back to normal on 9.2.0.

 

[Yatti420]

Normal? Using autotuning or any tunables with such little ram goes against the documentation and what the standard seems to be.. It would not surprise me if your speeds are actually slower then what you had before.. I'm pretty sure autotune etc is designed for systems with 32+gb of ram..

 

[cyberjock]

Oh.... he can't afford more RAM. I wonder if he'll be able to pay to get his data back when his pool goes to crap! Especially when he sees the cost of data recovery is significantly higher than a RAM stick.

 

[Yatti420]

I just don't mess with it.. I don't want to lose my pools..

 

[jgreco]

Not to beat a dead horse here, but the 8GB minimum in the docs isn't really a suggestion. We've seen a bunch of people come through the forum with trashed pools on 4GB or 6GB. We don't know why; none of those with the problem have been able to debug. It works fine for people right up to the point where suddenly it doesn't.

As long as you have the budget for potentially unrecoverable pool failure, well, good. In my experience, fate does not target you right up to the point that you have irreplaceable data on there.