Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
In my experience (and I could be wrong) the difference between the two comes down to which version of heartbeat you're using. In one of the production setups I run, we're using heartbeat 2.0.2, which doesn't support things like the Master/Slave resource type, so you need to let the systems bring up drbd on their own, putting both nodes into secondary mode, then when heartbeat brings up the drbddisk resource, it'll make one of them primary. In the event of failover, the other node will be made primary. With later versions that do support Master/Slave, you should use the drbd resource, because that is the one made to work with Master/ Slave, and the one that completely controls the initialisation and promition/demotion of nodes. As I said, though, I could be wrong about this. It's just my experience. Regards, Adrian Overbury Inomial Pty Ltd adrian at inomial.com Kenji HIROHAMA wrote: > > Hello, > > According to this page, it seems that we should use "drbd" resource, > not "drbddisk" resource type, with Heartbeat2/CRM; > http://www.drbd.org/drbd8-howto2.html > > I think these two resources means the following two files; > - /etc/init.d/drbd > - /etc/ha.d/resource.d/drbddisk > > Then, if there is any reason we should use "drbd" resource type rather > than "drbddisk", > would you please tell me the reason? > > I would like to know the difference. > > Thanks, > > -- > kenji.hirohama at nospam.gmail.com > Kenji Hirohama > _______________________________________________ > drbd-user mailing list > drbd-user at lists.linbit.com > http://lists.linbit.com/mailman/listinfo/drbd-user