Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
Hi Lars >> 1) Is there a way to keep 0.7 and 0.8 in sync at least "one way" from >> 0.7 as primary and 0.8 as slave during the update > > no. Thats sad :( >> 2) Can I keep my data parts of the disks - I use internal meta-data >> storage? I tried "drbdadm create-md test" on a test partition and it >> SEEMS to work - but before I destroy any valuable data I want to go for >> sure.... > > it "should" work. it is intended to be used that way. > it did work for us in our testing environments. > but in case it eats your data for some reason, > and you don't have backups, that would be your problem, not mine ... Sure - backups are there but just converting the meta data is a task of minutes and creating totally new disks will take some hours of service downtime > but. thinking HA, > when 0.7.23 works for you, why would you want to upgrade a reliably > working known good production platform to a new version, > when you don't need the new features? See the null pointer post - it does not work after a kernel upgrade that was necessary du to security concerns. Oliver -- Diese Nachricht wurde digital unterschrieben oliwel's public key: http://www.oliwel.de/oliwel.crt Basiszertifikat: http://www.ldv.ei.tum.de/page72 -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 5146 bytes Desc: S/MIME Cryptographic Signature URL: <http://lists.linbit.com/pipermail/drbd-user/attachments/20070423/02484db3/attachment.bin>