OK, so I've got this issue going on with Freenas 9.2.1.5 related to swap space. The server will be humming along just fine and periodically it begins running out of swap. Here's a short snippet from /var/log/messages:
...
May 15 19:00:27 fnas1 smbd[29911]: matchname: host name/name mismatch: 192.168.1.12 != (NULL)
May 15 19:00:27 fnas1 smbd[29911]: [2014/05/15 19:00:27.886593, 0] ../source3/lib/util_sock.c:1199(get_remote_hostname)
May 15 19:00:27 fnas1 smbd[29911]: matchname failed on 192.168.1.12
May 16 08:00:48 fnas1 kernel: swap_pager_getswapspace(16): failed
May 16 08:00:48 fnas1 kernel: swap_pager_getswapspace(16): failed
May 16 08:00:48 fnas1 kernel: swap_pager_getswapspace(8): failed
May 16 08:00:48 fnas1 kernel: swap_pager_getswapspace(16): failed
...
As you can see, it went from 19:00 until 08:00 the next day and no log entries, then it started running out of swap. After a few hundred of those swap_pager messages, it will usually start killing non-essential processes, starting with the Plex media server, and usually the Freenas HTTP GUI.
Anybody else seeing this? There aren't any Plex users up at 8:00am log time to cause any activity, and sometimes I do ANYDVD HD rips from my Windows workstation D: drive directly to a CIFS share on the Freenas box. It's usually done before the swap space messages begin.
Server hardware is ASUS P9X79 WS motherboard, Intel E5-2630V2 Hexa-core Xeon, 32GB ECC DDR3-1600 RAM, 6x WD RED 2TB in RAIDZ2, booting from USB 2.0 memory stick. Everything appears to work GREAT 99% of the time, except when the swap space runs out. System usually (lol) reports between 0MB and 300 MB swap utilized out of 14GB.
Getting frustrated. Tried watching some movies on ROKU at the beach house via Plex this weekend (remotely over Internet) and had to terminal service to my desktop PC back home, putty to the Freenas SSH prompt and do remote shutdown/reboot to get it back up and running. My father in law wasn't impressed. LOL.
Things I've tried --- break and rebuild disk pool as 3x2 disk mirrors thinking it was RAIDZ2 issue, no effect. Tried with and without a SSD ZIL and SSD L2ARC, and then both the ZIL + L2ARC. Performance was zippy, but didn't help the swap issue.
This has been going on a few weeks now and very frustrating.
Greg
...
May 15 19:00:27 fnas1 smbd[29911]: matchname: host name/name mismatch: 192.168.1.12 != (NULL)
May 15 19:00:27 fnas1 smbd[29911]: [2014/05/15 19:00:27.886593, 0] ../source3/lib/util_sock.c:1199(get_remote_hostname)
May 15 19:00:27 fnas1 smbd[29911]: matchname failed on 192.168.1.12
May 16 08:00:48 fnas1 kernel: swap_pager_getswapspace(16): failed
May 16 08:00:48 fnas1 kernel: swap_pager_getswapspace(16): failed
May 16 08:00:48 fnas1 kernel: swap_pager_getswapspace(8): failed
May 16 08:00:48 fnas1 kernel: swap_pager_getswapspace(16): failed
...
As you can see, it went from 19:00 until 08:00 the next day and no log entries, then it started running out of swap. After a few hundred of those swap_pager messages, it will usually start killing non-essential processes, starting with the Plex media server, and usually the Freenas HTTP GUI.
Anybody else seeing this? There aren't any Plex users up at 8:00am log time to cause any activity, and sometimes I do ANYDVD HD rips from my Windows workstation D: drive directly to a CIFS share on the Freenas box. It's usually done before the swap space messages begin.
Server hardware is ASUS P9X79 WS motherboard, Intel E5-2630V2 Hexa-core Xeon, 32GB ECC DDR3-1600 RAM, 6x WD RED 2TB in RAIDZ2, booting from USB 2.0 memory stick. Everything appears to work GREAT 99% of the time, except when the swap space runs out. System usually (lol) reports between 0MB and 300 MB swap utilized out of 14GB.
Getting frustrated. Tried watching some movies on ROKU at the beach house via Plex this weekend (remotely over Internet) and had to terminal service to my desktop PC back home, putty to the Freenas SSH prompt and do remote shutdown/reboot to get it back up and running. My father in law wasn't impressed. LOL.
Things I've tried --- break and rebuild disk pool as 3x2 disk mirrors thinking it was RAIDZ2 issue, no effect. Tried with and without a SSD ZIL and SSD L2ARC, and then both the ZIL + L2ARC. Performance was zippy, but didn't help the swap issue.
This has been going on a few weeks now and very frustrating.
Greg