I have one more question with regard to mentioned kernel update to
2.6.18-308.4.1.el5 :<div>in extras repo there is a package available</div><div><br></div><div>kmod-drbd83</div><div>8.3.12</div><div><div>This package provides the drbd83 kernel modules built for the Linux</div><div> : kernel 2.6.18-274.17.1.el5 for the i686 family of processors.</div>
<div><div><br></div><div>We currently have installed kmod-drbd83:</div><div><br></div><div>8.3.8</div><div><div><div>This package provides the drbd83 kernel modules built for the Linux</div><div> : kernel 2.6.18-194.el5 for the i686 family of processors.</div>
</div></div><div><br></div><div>Should kmod-drbd83 version match current kernel version (from package description) or should kmod-drbd83 in version 8.3.8 be installed if we are using drbd83-8.3.8-1.el5.centos ?</div><div>
<br></div><div>Best regards,</div><div>Rafal.</div><div><br><div class="gmail_quote">2012/5/6 Rafa³ Radecki <span dir="ltr"><<a href="mailto:radecki.rafal@gmail.com" target="_blank">radecki.rafal@gmail.com</a>></span><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div>Hi all.</div><div><br></div>I have two hosts with drbd:<div><div>kmod-drbd83-8.3.8-1.el5.centos</div><div>drbd83-8.3.8-1.el5.centos</div>
</div><div>and kernel (CentOS 5.7):</div><div>2.6.18-308.4.1.el5</div><div><br></div>
<div>After a recent upgrade of kernel I have had two sitiuations when my ext3 filesystem on /dev/drbd0 became read-only. I've checked disks with smartctl -t long, they are ok. There are no messages with disks problems in /var/log/messages | dmesg. I've made fsck tonight but 3 hours after it has finished the problem repeated once more (under heavy load).</div>
<div><br></div><div>/var/log/messages:</div><div><br></div><div><div>May 6 06:22:27 srv1a kernel: EXT3-fs error (device drbd0): htree_dirblock_to_tree: bad entry in directory #43024813: rec_len</div><div>% 4 != 0 - offset=73728, inode=1701012818, rec_len=30313, name_len=101</div>
<div>May 6 06:22:27 srv1a kernel: Aborting journal on device drbd0.</div><div>May 6 06:22:28 srv1a kernel: journal commit I/O error</div><div>May 6 06:22:28 srv1a kernel: ext3_abort called.</div><div>May 6 06:22:28 srv1a kernel: journal commit I/O error</div>
<div>May 6 06:22:28 srv1a kernel: EXT3-fs error (device drbd0): ext3_journal_start_sb: Detected aborted journal</div><div>May 6 06:22:28 srv1a kernel: ext3_abort called.</div><div>May 6 06:22:28 srv1a kernel: EXT3-fs error (device drbd0): ext3_journal_start_sb: Detected aborted journal</div>
<div>May 6 06:22:28 srv1a kernel: Remounting filesystem read-only</div><div>May 6 06:22:28 srv1a kernel: __journal_remove_journal_head: freeing b_committed_data</div><div>May 6 06:22:28 srv1a kernel: __journal_remove_journal_head: freeing b_committed_data</div>
<div>May 6 06:22:28 srv1a kernel: __journal_remove_journal_head: freeing b_committed_data</div><div>May 6 06:22:28 srv1a kernel: journal commit I/O error</div><div>May 6 06:22:28 srv1a kernel: EXT3-fs error (device drbd0): htree_dirblock_to_tree: bad entry in directory #43024813: rec_len</div>
<div>% 4 != 0 - offset=106496, inode=1701012818, rec_len=30313, name_len=101</div><div>May 6 06:22:28 srv1a kernel: EXT3-fs error (device drbd0): htree_dirblock_to_tree: bad entry in directory #43024813: rec_len</div><div>
% 4 != 0 - offset=204800, inode=1869116005, rec_len=29811, name_len=46</div></div><div><br></div><div>I've found:</div><div><br></div><div><a href="https://bugzilla.redhat.com/show_bug.cgi?id=494927" target="_blank">https://bugzilla.redhat.com/show_bug.cgi?id=494927</a>
</div><div><br></div><div>There are some clues that it may be a kernel problem so I went back to:</div><div>2.6.18-274.7.1.el5</div><div><br></div><div>At the moment the situation is ok but I've read that the problem happens in random circumstances.</div>
<div><br></div><div>Any clues what to do?</div><div><br></div><div>Best regards,</div><div>Rafal.</div>
</blockquote></div><br></div></div></div>