Pid 2 [g_event] 100% busy

Status
Not open for further replies.

maurertodd

Dabbler
Joined
Nov 3, 2011
Messages
47
I was reviewing the status of my FreeNAS server and noticed the load was around 1. Then I looked at the CPU utilization on the reporting tab and saw it was at bouncing around 100% of the 200% available. I looked at the system processes and saw nothing. So I logged in via SSH and did the used "ps aux" of which the first few lines are below. What is g_event and why might it be using 100% for days on end?

FreeNAS-8.3.0-RELEASE-p1-x64 (r12825)
Intel(R) Celeron(R) CPU G550 @ 2.60GHz
3955MB

[todd@freenas] /# ps aux
USER PID %CPU %MEM VSZ RSS TT STAT STARTED TIME COMMAND
root 11 104.7 0.0 0 32 ?? RL 27Mar13 72136:20.00 [idle]
root 2 100.0 0.0 0 16 ?? RL 27Mar13 10945:07.72 [g_event]
root 0 0.0 0.2 0 6832 ?? DLs 27Mar13 140:41.82 [kernel]
root 1 0.0 0.0 3204 388 ?? ILs 27Mar13 0:00.01 /sbin/init --
root 3 0.0 0.0 0 16 ?? DL 27Mar13 14:43.32 [g_up]
root 4 0.0 0.0 0 16 ?? DL 27Mar13 22:01.33 [g_down]
root 5 0.0 0.0 0 16 ?? DL 27Mar13 0:00.00 [crypto]
root 6 0.0 0.0 0 16 ?? DL 27Mar13 0:00.00 [crypto returns]
root 7 0.0 0.0 0 16 ?? DL 27Mar13 0:00.00 [xpt_thrd]
root 8 0.0 0.0 0 16 ?? DL 27Mar13 0:00.00 [g_mp_kt]
root 9 0.0 0.0 0 16 ?? DL 27Mar13 0:05.80 [pagedaemon]
r
 

titan_rw

Guru
Joined
Sep 1, 2012
Messages
586
I've seen that before.

On my system it was after it dropped a hard drive due to read problems.

Rebooting the system fixed it. Replacing the failing hard drive fixed the underlying problem.
 

titan_rw

Guru
Joined
Sep 1, 2012
Messages
586
In as much as I would call failing hardware a bug.

I replaced the drive, and haven't had the problem since.
 

joeschmuck

Old Man
Moderator
Joined
May 28, 2011
Messages
10,970
If you suspect a drive, run a long smart test on all the drives and check the results. If you get nothing, do it again just to validate it.

Are you encrypting your drives?
 
Joined
Jun 17, 2013
Messages
36
I see the same issue. Not running with encrypted drives.

A drive started throwing read errors, and was booted out of the pool.

g_event started consuming 100% of the CPU.

I would think this is a bug--especially for a NAS. A drive failing shouldn't cause the CPU to max out and require a reboot.
 
Status
Not open for further replies.
Top