Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
On Wed, Jun 14, 2006 at 08:12:20PM +0530, Milind Dumbare wrote: > So, I will have to do > root at dhruva:#drbdadm primary RES1 > And then dhruva will be primary ? Yes. > > Do I need to do > root at tucker:#drbdadm secondary RES1 > for making tucker partition as secondary? No. They both start as secondary, so you don't need this step. Only if you're switching from tucker to dhruva: tucker$ drdbadm secondary RES1 .... dhruva$ drbdadm primary RES1 > So for replicating data I will have to write data to /dev/drbd0... and > copies will be save susequently to dhruva and tucker? Yes. > Now next problem is. When I do as follows > > ===================== > [root at dhruva drbd]# drbdadm primary RES1 > ioctl(,SET_STATE,) failed: Input/output error > Local replica is inconsistent (--do-what-I-say ?) > Command 'drbdsetup /dev/drbd0 primary' terminated with exit code 21 Well, you've just created the configuration, but as far as drbd is concerned, it doesn't know which side to use as the "original". So you have to force one to become primary, as the error shows (option --do-what-I-say, but I don't remember if it is accepted by drbdadm or only by drbdsetup). -- lfr 0/0 -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: <http://lists.linbit.com/pipermail/drbd-user/attachments/20060614/4722c5af/attachment.pgp>