Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
On 15/10/15 13:02, Ammar Sheikh Saleh wrote: > When ==> During normal operation Are you attempting to use ext3/4 on both nodes at the same time? > > What's the IO stack below DRBD ==> 4 Disks in JBOD > > Kernel upgrade is not possible now ... but at the same time its not > too old ( v.2.6.32-431.20.3) That kernel belongs to CentOS/RHEL 6.5 which is now approaching 2 years old and has numerous security vulnerabilities present. > > > On Thu, Oct 15, 2015 at 2:34 PM, Lars Ellenberg > <lars.ellenberg at linbit.com <mailto:lars.ellenberg at linbit.com>> wrote: > > On Thu, Oct 15, 2015 at 12:32:11PM +0300, Ammar Sheikh Saleh wrote: > > Hi all, > > > > I have one cluster with 2 nodes in active-active - master/slave > setup > > > > I see the following error messages in the system logs: > > *when*. > > After a hard crash? > After a simulated Crash? > After a switchover? > After a failover? > During normal operation? > > What's the IO stack below DRBD? > > > 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 > > 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 > > 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 > > 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 > > 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. > > 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 > > 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. > > > > What is the appropriate action to fix this issue > > Did you even google for the message? > "JBD: Spotted dirty metadata buffer" turns up several bugzillas from > 2010 and 2012, suggesting kernel upgrade would help. > > > -- > : Lars Ellenberg > : http://www.LINBIT.com | Your Way to High Availability > : DRBD, Linux-HA and Pacemaker support and consulting > > DRBD® and LINBIT® are registered trademarks of LINBIT, Austria. > __ > please don't Cc me, but send to list -- I'm subscribed > _______________________________________________ > drbd-user mailing list > drbd-user at lists.linbit.com <mailto:drbd-user at lists.linbit.com> > http://lists.linbit.com/mailman/listinfo/drbd-user > > > > ______________________________________________________________________ > This email has been scanned by the Symantec Email Security.cloud service. > For more information please visit http://www.symanteccloud.com > ______________________________________________________________________ > > > _______________________________________________ > drbd-user mailing list > drbd-user at lists.linbit.com > http://lists.linbit.com/mailman/listinfo/drbd-user -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.linbit.com/pipermail/drbd-user/attachments/20151015/76d146d9/attachment.htm>