You are checking your MySQL logs in /var/log/mysqld.log and come across an error like this: 161222 18:03:40 [ERROR] /usr/libexec/mysqld: Table './eximstats/sends' is marked as crashed and last (automatic?) repair failed The Solution: cd /var/lib/mysql/eximstats myisamchk -r sends.MYI - recovering (with sort) MyISAM-table 'sends.MYI' Data records: 71129........

The best way I could figure out is to use another guest of some sort to do this, while assigning the disk that needs to be resized to the same guest. So say we have /dev/xvda as the guests drive and we've booted it up. We also have /dev/xvdb (this is going to be the image/disk to be resized). In this case it's based on an ext3/4 image. Run e2fsck on it to ensure there are no filesystem errors. e2fsck /dev/xvdb........

This assumes that you've at least created the correct partition for your DRBD already. Notice that I am "diskless", that's because either your DRBD partition doesn't exist/has been renamed (eg. sdb becomes sda when sdb dies and you reboot) or because that drive is really actually dead/gone. *If you need to permanently change the partition/device for your resource be sure to edit /etc/drbd.conf on both hosts and reload the config. (replace r0 with........