[DRBD-user] State 'stalled'

Ben Clewett ben at roadrunner.uk.com
Tue May 15 09:11:27 CEST 2007

Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.


After my discovery of the 'stalled' problem I later found a solution:

I changed my protocol from 'B' to 'C' and the problem went away.

I would therefore suggest that there is a bug in the 'B' protocol in 
version 8.0.2.

For reference, I am using a 32 bit SUSE 10.1 brand new install, 
compiling DRBD from source.



Ben Clewett wrote:
> Dear DRBD,
> I have been using 8.0.2 for a few weeks now and find it very well 
> written and does the job very well.  Integration with Linux-ha works and 
> I don't seem to ever loose any data.
> But I keep encountering a real problem:
> After a crash-recovery, or by command, my two servers go into resync 
> mode.  If I then write some data to the mounted Primary, the sync goes 
> into 'stalled' mode.
> I cannot disconnect DRBD as the disks are mounted.
> I cannot unmount the partition as services are running.
> I cannot 'kill -9' the services as they are locked.
> All I can do is 'pause-sync' and 'resume-sync', but it goes straight 
> back to 'stalled' without transferring any data or releasing my services.
> I also can't shut-down for the above reasons.
> The only option which works is to switch off both servers and reboot. 
> After which the sync will complete no problem.
> Obviously I have a setting wrong or something.
> Can any kind member suggest anything I can try to avoid this death-trap?
> Thanks,
> Ben Clewett
> _______________________________________________
> drbd-user mailing list
> drbd-user at lists.linbit.com
> http://lists.linbit.com/mailman/listinfo/drbd-user

More information about the drbd-user mailing list