[DRBD-user] drbd turned on me, and bit my hand this morn

Lars Ellenberg Lars.Ellenberg at linbit.com
Tue Dec 6 19:09:47 CET 2005

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


/ 2005-12-06 11:56:52 -0500
\ Brad Barnett:
> 
> 
> 
> Just to add to this.
> 
> When drbdadm is in this "locked" state, I can not kill it, or kill -9 it. 
> This means that I must reboot the box, instead of rmmod the module and
> make my configuration changes.
> 
> Because of this, I do not think this is the expected behaviour.
> 
> I'm using 0.7.10-3 (The latest Debian stable version), and found the same
> behaviour with 0.7.14 freshly installed from tarballs.


how much storage?

how long did you wait before rebooting the box?

what is in dmesg or kern.log?

what does /proc/drbd look like at that time?

did you try to boot the box without drbd/heartbeat started by init,
then start drbd by hand? if so, any difference?


-- 
: Lars Ellenberg                                  Tel +43-1-8178292-0  :
: LINBIT Information Technologies GmbH            Fax +43-1-8178292-82 :
: Schoenbrunner Str. 244, A-1120 Vienna/Europe   http://www.linbit.com :
__
please use the "List-Reply" function of your email client.



More information about the drbd-user mailing list