Hello All,
I have experienced system hang-up after running the latest LTP(http://ltp.sourceforge.net/) tool as a part of durability testings on our GFS environement. I was using 2 DELL PE1950 servers which installed CentOS4.3(IA32) and DELL EMC AX150 was setup as a GFS shared storage connected to each servers. We did "./runltp -d /gfs3" to run the LTP tool on one server and another server remained just idle. Here are the extracted /var/log/messages taken when the system was stopped:
Oct 4 13:15:47 centos1 kernel: lock_dlm: Assertion failed on line 500 of file /home/buildcentos/rpmbuild/BUILD/gfs-kernel-2.6.9-49/smp/src/dlm/plock.c
Oct 4 13:15:47 centos1 kernel: lock_dlm: assertion: "!error"
Oct 4 13:15:47 centos1 kernel: lock_dlm: time = 71704458
Oct 4 13:15:47 centos1 kernel: error=-11
Oct 4 13:15:47 centos1 kernel:
Oct 4 13:15:47 centos1 kernel: ------------[ cut here ]------------
Oct 4 13:15:47 centos1 kernel: kernel BUG at /home/buildcentos/rpmbuild/BUILD/fs-kernel-2.6.9-49/smp/src/dlm/plock.c:500!
Oct 4 13:15:47 centos1 kernel: invalid operand: 0000 [#1]
Oct 4 13:15:47 centos1 kernel: SMP
Oct 4 13:15:47 centos1 kernel: Modules linked in: parport_pc lp parport autofs i2c_dev i2c_core lock_dlm(U) gfs(U) lock_harness(U) dlm(U) cman(U) sunrpc dm_m rror dm_multipath dm_mod button battery ac md5 ipv6 joydev uhci_hcd ehci_hcd hw random shpchp bnx2 ext3 jbd qla6312 qla2xxx scsi_transport_fc megaraid_sas sd_m d scsi_mod
Oct 4 13:15:47 centos1 kernel: CPU: 0
Does anyone know whether this is a known problem or not? Or any suggestion?
It is most likely I will be able to reproduce this problem.
Thanks,
Tadashi
-- Linux-cluster mailing list Linux-cluster@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/linux-cluster
