Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
Hello everyone,
I've read all the posts regarding the above situation, but could not get
anything to work in our installation.
After the primary server gets back post forced reboot, the secondary server
won't let go off the primary drbd state. Heartbet is working fine and
calling the drbddisk within its resources directory.
lsof and fuser don't report anything using /dev/drbd0 or /var/lib/mysql
(which is what's being synced across machines), but I went even further by
trying to disable almost all services and rmmod'ing several modules. Yet,
secondary stubbornly refuses to give it away.
After reading the other posts, I assume it has something to do with the
kernel? Both machines use Centos 4.4, with 2.6.9-42.0.3.ELsmp.
Secondary server says:
machine2# cat /proc/drbd
version: 0.7.21 (api:79/proto:74)
SVN Revision: 2326 build by buildsvn at build-i386, 2006-10-07 05:12:17
0: cs:Connected st:Primary/Secondary ld:Consistent
ns:94216 nr:0 dw:40 dr:94614 al:0 bm:29 lo:0 pe:0 ua:0 ap:0
if I try to force drbd into secondary state it gives me:
machine2# drbdadm secondary all
ioctl(,SET_STATE,) failed: Device or resource busy
Someone has opened the device for RW access!
Command 'drbdsetup /dev/drbd0 secondary' terminated with exit code 20
drbdsetup exited with code 20
I have a truckload of logs here so please tell me what I should provide for
further analysis.
Many thanks!
Cass Surek
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linbit.com/pipermail/drbd-user/attachments/20070213/4eb05e42/attachment.htm>