Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
On Mon, May 24, 2004 at 01:56:48AM +0200, Fur?sz P?ter wrote: > > > Try to run again drbdadm up all, and it's work :) My /proc/drbd show > > > this now: > > > > > > version: 0.7-pre7 cvs $Date: 2004/05/19 19:53:20 $ > (api:72/proto:72) > > > 0: cs:Connected st:Secondary/Secondary ld:Consistent > > > ns:0 nr:0 dw:0 dr:0 al:0 bm:0 lo:0 pe:0 ua:0 ap:0 > > > 1: cs:Unconfigured > > > > > > - FINALLY: > > > When I do /etc/init.d/drbd start > > > > > > Starting DRBD resources: ioctl() failed: Device or resource > busy > > > Command line was '/sbin/drbdsetup /dev/nb0 disk /dev/hda3 > > > internal -1 --on-io-error=detach' > > > drbdsetup exited with code 20 > > > > > > Failed setting up r1 > > > > > > When I run this: /sbin/drbdsetup /dev/nb0 disk /dev/hda3 > > > internal -1 --on-io-error=detach > > > ioctl() failed: Device or resource busy > > > > > > What is the problem? Thank you for any help. > > > > admited, our userlevel error messages could be more informative. but, > > if you configure an already configured device, you get a "busy!" back. > > I think this is valid behaviour. > > > > I think it is not configured, becouse I have wrote, I create the nb0 and nb1 > devices directly before I run drbdsetup. I don't know why my device > busy :( > I have wrote step by step what I did. Any idea what's wrong with my > solution? you dont use drbdsetup directly. you use drbdadm. which you did. if /proc/drbd shows anything different than Unconfigured, it is configured. if you do a drbdadm up all by hand, and then you do a /etc/init.c/drbd start, then probably you get a BUSY. which needs to be improved: > > however we possibly need to add a "ignore reconfigure with exact same > > settings" to the drbd init script to be LSB conform, which iirc requires > > a start on an already started "service" to be silently ignored. Lars Ellenberg