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@lists.linbit.com http://lists.linbit.com/mailman/listinfo/drbd-user
