I copied this from the console:
kernel panic: GFS: Assertion failed on line 242 of file linux_dio.c
gfs:assertion: "buffer_uptodate (bh)"
gfs:time=1139336367
gfs: fsid=CSM_ACN:u_af.3
The first part of the stack trace was logged by syslog:
Feb 7 11:19:27 inception kernel: Panicking because of write error
Feb 7 11:19:27 inception kernel: f41bfef8 f8f4cb72 00000001 c0384e98 00000000 00000246 00000021 f284bdec
Feb 7 11:19:27 inception kernel: c01297e3 0000000a 00000400 f8f6e169 cccb6da8 cccb6d60 e35a6b8c f284bdec
Feb 7 11:19:27 inception kernel: f8f308e5 f8f6c07e f8f6bfba 000000f2 00000013 f98ae000 f284bdec f284bd80
Feb 7 11:19:27 inception kernel: Call Trace: [<f8f4cb72>] gfs_asserti [gfs] 0x32 (0xf41bfefc)
The rest of the stack trace was was displayed on the console and I copied it down. If it would be of use, I can type it in.
Any ideas what would cause this?
There are 6 nodes in the cluster running Enterprise 3 update 6 and GFS 6.0.2.27.
thanks
Matt
-- Linux-cluster@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/linux-cluster
