<div dir="ltr">When ==> <span style="color:rgb(0,0,0);font-size:12.8px">During normal operation</span><div><span style="color:rgb(0,0,0);font-size:12.8px"><br></span></div><div><span style="color:rgb(0,0,0);font-size:12.8px">What's the IO stack below DRBD ==> 4 Disks in JBOD</span><span style="color:rgb(0,0,0);font-size:12.8px"><br></span></div><div><span style="color:rgb(0,0,0);font-size:12.8px"><br></span></div><div><span style="color:rgb(0,0,0);font-size:12.8px">Kernel upgrade is not possible now ... but at the same time its not too old ( v.</span><font color="#000000"><span style="font-size:12.8px">2.6.32-431.20.3)</span></font></div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Oct 15, 2015 at 2:34 PM, Lars Ellenberg <span dir="ltr"><<a href="mailto:lars.ellenberg@linbit.com" target="_blank">lars.ellenberg@linbit.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On Thu, Oct 15, 2015 at 12:32:11PM +0300, Ammar Sheikh Saleh wrote:<br>
> Hi all,<br>
><br>
> I have one cluster with 2 nodes in active-active - master/slave setup<br>
><br>
> I see the following error messages in the system logs:<br>
<br>
</span>*when*.<br>
<br>
After a hard crash?<br>
After a simulated Crash?<br>
After a switchover?<br>
After a failover?<br>
During normal operation?<br>
<br>
What's the IO stack below DRBD?<br>
<span class=""><br>
> Jan 5 11:07:23 lws1h1 kernel: EXT4-fs error (device drbd1): ext4_mb_generate_buddy: EXT4-fs: group 3785: 27507 blocks in bitmap, 27576 in gd<br>
> Jan 5 11:07:53 lws1h1 kernel: EXT4-fs error (device drbd1): ext4_mb_generate_buddy: EXT4-fs: group 2437: 9219 blocks in bitmap, 32546 in gd<br>
> Jan 5 11:07:53 lws1h1 kernel: EXT4-fs error (device drbd1): ext4_mb_generate_buddy: EXT4-fs: group 2438: 9075 blocks in bitmap, 32760 in gd<br>
> Jan 5 11:07:53 lws1h1 kernel: EXT4-fs error (device drbd1): ext4_mb_generate_buddy: EXT4-fs: group 2442: 9078 blocks in bitmap, 32768 in gd<br>
> Jan 5 20:18:27 lws1h1 kernel: JBD: Spotted dirty metadata buffer (dev = drbd1, blocknr = 0). There's a risk of filesystem corruption in case of system crash.<br>
> Jan 5 22:02:18 lws1h1 kernel: EXT4-fs error (device drbd1): ext4_mb_generate_buddy: EXT4-fs: group 3795: 32532 blocks in bitmap, 29780 in gd<br>
> Jan 5 22:02:19 lws1h1 kernel: JBD: Spotted dirty metadata buffer (dev = drbd1, blocknr = 0). There's a risk of filesystem corruption in case of system crash.<br>
><br>
> What is the appropriate action to fix this issue<br>
<br>
</span>Did you even google for the message?<br>
"JBD: Spotted dirty metadata buffer" turns up several bugzillas from<br>
2010 and 2012, suggesting kernel upgrade would help.<br>
<span class="HOEnZb"><font color="#888888"><br>
<br>
--<br>
: Lars Ellenberg<br>
: <a href="http://www.LINBIT.com" rel="noreferrer" target="_blank">http://www.LINBIT.com</a> | Your Way to High Availability<br>
: DRBD, Linux-HA and Pacemaker support and consulting<br>
<br>
DRBD® and LINBIT® are registered trademarks of LINBIT, Austria.<br>
__<br>
please don't Cc me, but send to list -- I'm subscribed<br>
_______________________________________________<br>
drbd-user mailing list<br>
<a href="mailto:drbd-user@lists.linbit.com">drbd-user@lists.linbit.com</a><br>
<a href="http://lists.linbit.com/mailman/listinfo/drbd-user" rel="noreferrer" target="_blank">http://lists.linbit.com/mailman/listinfo/drbd-user</a><br>
</font></span></blockquote></div><br></div>