FreeNas security run output - problem with lost pages of memory

Status
Not open for further replies.

Frosch1482

Dabbler
Joined
Feb 16, 2014
Messages
28
Dear all,

This morning I got strange FreeNas security output message.
Unfortunalely I´m not so much experianced with these kind of messages that I do not fully understand what FreeNas want´s to tell me.

I´m just a bit alarmed because I read a out "memory pages lost" and I have in my mind that ZFS doesn´t like memory issues at all =)

Last thing what I want to do is loose all the data :)

Any Idea what the box want`s to tell me in detail?

Code:
freenas.local kernel log messages:
epair0a: link state changed to DOWN
epair0b: link state changed to DOWN
ifa_del_loopback_route: deletion failed
Freed UMA keg (udp_inpcb) was not empty (20 items).  Lost 2 pages of memory.
Freed UMA keg (udpcb) was not empty (336 items).  Lost 2 pages of memory.
Freed UMA keg (tcpreass) was not empty (84 items).  Lost 1 pages of memory.
Freed UMA keg (tcp_inpcb) was not empty (20 items).  Lost 2 pages of memory.
Freed UMA keg (tcpcb) was not empty (12 items).  Lost 3 pages of memory.
Freed UMA keg (ripcb) was not empty (20 items).  Lost 2 pages of memory.
hhook_vnet_uninit: hhook_head type=1, id=1 cleanup required
hhook_vnet_uninit: hhook_head type=1, id=0 cleanup required
epair1a: link state changed to DOWN
epair1b: link state changed to DOWN
ifa_del_loopback_route: deletion failed
Freed UMA keg (udp_inpcb) was not empty (30 items).  Lost 3 pages of memory.
Freed UMA keg (udpcb) was not empty (336 items).  Lost 2 pages of memory.
Freed UMA keg (tcpreass) was not empty (84 items).  Lost 1 pages of memory.
Freed UMA keg (tcptw) was not empty (200 items).  Lost 4 pages of memory.
Freed UMA keg (tcp_inpcb) was not empty (110 items).  Lost 11 pages of memory.
Freed UMA keg (sackhole) was not empty (101 items).  Lost 1 pages of memory.
Freed UMA keg (tcpcb) was not empty (24 items).  Lost 6 pages of memory.
Freed UMA keg (ripcb) was not empty (20 items).  Lost 2 pages of memory.
hhook_vnet_uninit: hhook_head type=1, id=1 cleanup required
hhook_vnet_uninit: hhook_head type=1, id=0 cleanup required
epair2a: link state changed to DOWN
epair2b: link state changed to DOWN
bridge0: link state changed to DOWN
em0: promiscuous mode disabled
Syncing disks, vnodes remaining...0 0 0 0 0 0 done
CPU: Intel(R) Celeron(R) CPU G1610 @ 2.60GHz (2594.16-MHz K8-class CPU)
Timecounter "TSC-low" frequency 1297079720 Hz quality 1000
vboxdrv: fAsync=0 offMin=0x2cc offMax=0xa74
em0: promiscuous mode enabled
epair0a: Ethernet address: 02:71:71:00:08:0a
epair0b: Ethernet address: 02:71:71:00:09:0b
epair1a: Ethernet address: 02:30:3f:00:09:0a
epair1b: Ethernet address: 02:30:3f:00:0a:0b
epair2a: Ethernet address: 02:37:3f:00:0a:0a
epair2b: Ethernet address: 02:37:3f:00:0b:0b
arp: 10.0.0.111 moved from 02:37:3f:00:0a:0a to 74:d0:2b:99:c2:f8 on epair2b
 

Frosch1482

Dabbler
Joined
Feb 16, 2014
Messages
28
Thanks, but unfortunately i do not fully understand.
As far as I understood the problem comes from a NIC driver that is not really perfectly implemented on FreeBSD. If I have no issues with my LAN i can ignore this error and the ZFS pool is not on risk due to silent ram failure, is it right?
 
Status
Not open for further replies.
Top