[Ocfs2-users] server crash : Assertion failure in do_get_write_access (kernel 2.6.9-42.0.2.ELs

[Sunil Mushran]

Do you have a netconsole server setup? If not, it is recommended
that you do because it captures the full oops logs. For example,
if we had the full oops log, we would not only know the component
(ext3 or ocfs2) that triggered this and also the potential fix.

The non-auto-restart is because you have not set /proc/sys/kernel/panic
to a number > 0. You will find more in the ocfs2 faq. Or you could go thru
the section on kernel configuration in the ocfs2 1.4 user's guide.

Derek Hazell wrote:
> Hi OCFS2 forum
> A few things:
> (i) thanks for your support of OCFS2 on this forum
> (ii) the advice I received August 24 to run elevator=deadline io 
> scheduling seems to have helped - there have been no unexpected 
> reboots since then
> (iii) we did however have a crash last night on the same RHEL AS4 
> server (running ocfs2 1.2.9-1) -the crash may be unrelated to ocfs2 
> but I thought I'd run it past you anyway - here is a copy of a post I 
> made to a linux forum:
>
> /Last night one of our Linux servers (running RHEL AS4, kernel 
> 2.6.9-42.0.2.ELsmp) crashed. The server is part of a four node ocfs2 
> 1.2.9-1 cluster. After the crash I believe the server needed to be 
> manually restarted.
>
> I have cut the following out of /var/log/messages event log:
> Sep 23 19:15:33 ImageInt1 sshd(pam_unix)[10011]: session opened for 
> user root by root(uid=0)
> Sep 23 22:31:04 ImageInt1 kernel: Assertion failure in 
> do_get_write_access() at fs/jbd/transaction.c:693: 
> "handle->h_buffer_credits > 0"
> Sep 23 22:31:04 ImageInt1 kernel: ----------- [cut here ] --------- 
> [please bite here ] ---------
> Sep 23 22:31:06 ImageInt1 kernel: Kernel BUG at transaction:693
> Sep 23 22:31:06 ImageInt1 kernel: invalid operand: 0000 [1] SMP
> Sep 23 22:31:06 ImageInt1 kernel: CPU 1
> Sep 23 22:49:51 ImageInt1 syslogd 1.4.1: restart.
>
> I googled on internet for the assertion failure and found one report 
> saying it is a bug in the code, but there was no fix mentioned.
> /
> As always, any help is appreciated
>
> regards
> Derek