The following is the error log we received, can anyone tell in details what could be the problem?
Nov 15 13:03:20 machine1 sshd(pam_unix)[6698]: session closed for user sasuser
Nov 15 13:03:24 machine1 sshd(pam_unix)[6782]: session opened for user sasuser by (uid=701)
Nov 15 13:03:30 machine1 sshd(pam_unix)[6782]: session closed for user sasuser
Nov 15 13:04:00 machine1 sshd(pam_unix)[6800]: session opened for user sasuser by (uid=701)
Nov 15 13:04:04 machine1 sshd(pam_unix)[6800]: session closed for user sasuser
Nov 15 13:05:35 machine1 ntpd[889]: time reset 0.492178 s
Nov 15 13:05:35 machine1 ntpd[889]: synchronisation lost
Nov 15 13:11:01 machine1 sshd(pam_unix)[8154]: session opened for user sasuser by (uid=701)
Nov 15 13:11:09 machine1 sshd(pam_unix)[8154]: session closed for user sasuser
Nov 15 13:11:26 machine1 kernel: cur_state = 0, new_state = 0
Nov 15 13:11:26 machine1 kernel:
Nov 15 13:11:26 machine1 kernel: GFS: Assertion failed on line 62 of file bits.c
Nov 15 13:11:26 machine1 kernel: GFS: assertion: "valid_change[new_state * 4 + cur_state]"
Nov 15 13:11:26 machine1 kernel: GFS: time = 1100495486
Nov 15 13:11:26 machine1 kernel: GFS: fsid=spcsas:sasdata.0: rgroup = 8125123
Nov 15 13:11:26 machine1 kernel:
Nov 15 13:11:26 machine1 kernel: Kernel panic: GFS: Record message above and reboot.
Nov 15 13:11:26 machine1 kernel:
Nov 15 13:26:16 machine1 syslogd 1.4.1: restart.
Nov 15 13:26:16 machine1 syslog: syslogd startup succeeded
Nov 15 13:26:16 machine1 kernel: klogd 1.4.1, log source = /proc/kmsg started.
I suspect something was changed and then, the system goes down but unsure what changes were made!
cur_state = 0, new_state = 0
valid_change[new_state * 4 + cur_state]"