Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
On Thu, Jun 01, 2006 at 05:01:48PM +0200, Lars Ellenberg wrote: > / 2006-06-01 15:52:19 +0100 > \ paddy: > > On Thu, Jun 01, 2006 at 04:29:16PM +0200, Rafael Diaz Maurin wrote: > > > Leroy van Logchem a écrit : > > > > > > > >>2/ Does it matter if both nodes have 2 differents versions of drbd > > > >>(are 0.7.10 and 0.7.19 compatible without losing data) ? Are the data > > > >>copied safely on both nodes ? > > > > > > > >My experience has been that it works fine. Upgrading doesnt change the > > > >ondisk structures if the versions (api:78/proto:74) don't change. > > > > > > All right, so in the case of upgrading version: 0.7.10 without stopping > > > the cluster it must be the drbd version: 0.7.17 (api:77/proto:74) > > > because drbd version: 0.7.10 (api:77/proto:74) > > > and since the drbd version: 0.7.18 (api:78/proto:74) > > > > > > best to check this, but off the top of my head you should be able to go > > by the protocol version, so you could go straight from .10 to .19 > > > > I don't recall what the api number is for exactly. > > protocol version: communication on the wire. > so no problem to connect 0.7.19 with 0.7.10 > > api version: communication of user space tools with kernel modul. > so you need to upgrade modules and drbdadm/drbdsetup at the same > time, and make sure that the old module is unloaded before you > install the new one. ah yes! quite an important detail that one :-) while we're on the subject, is there any hard and fast rule about the on-disk structures ? what is the migration path to 0.8 like ? Regards, Paddy -- Perl 6 will give you the big knob. -- Larry Wall