Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
Do not hijack threads. On Tue, Jan 27, 2009 at 04:30:44PM -0700, ha at buglecreek.com wrote: > I am in the process of upgrading the OS on a 2 node cluster that is > running heartbeat-2.1.4-2.1 (R1 style), drbd-8.0.14, drbdlinks. I have > rebuilt one node and while switching back and forth between nodes while > testing I noticed the following log entries: > > INFO: Running start for /dev/drbd0 on /shared > kernel: EXT3-fs warning: maximal mount count reached, running e2fsck is > recommended > kernel: EXT3 FS on drbd0, internal journal > > When heartbeat mounts the drbd device I am getting the maximal mount > count warning. I'm not sure how to handle this on a drbd device. I > have a simple setup with a separate disk on each node dedicated to drbd. > No lvm, raid etc. It just gets mounted to /shared by heartbeat. I'm > getting this on both nodes. Can you do a fsck on the backing device > (/dev/hda1) on the node that is not primary without causing problems? No. Do not bypass drbd. > Can anyone suggest a way to handle this? either forget about the fsck. if the warnings annoy you, disable the mount count and mount time counters, see tune2fs -c and -i (use on drbd0!) or fsck the DRBD. -> umount /shared, fsck drbd0, mount /shared. as you say you use heartbeat in haresources mode, that should be straight forward. if you where in CRM mode, you'd need to set the target role of the Filesystem to stopped temporarily, or set it to unmanaged. -- : Lars Ellenberg : LINBIT | Your Way to High Availability : DRBD/HA support and consulting http://www.linbit.com DRBD® and LINBIT® are registered trademarks of LINBIT, Austria. __ please don't Cc me, but send to list -- I'm subscribed