Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
Hi list, I tried to convert a drbd ressource from version 0.7.25 to 8.0.7 following Florians upgrade guide. Problem is that drbdadm does not recognize the v07 Magic number and offers to generate a new meta data block. I've attached drbd.conf files for both versions. What can I do to convert the drbd ressource without risk of data loss? Regards, Andreas -------------- next part -------------- resource r0 { protocol C; incon-degr-cmd "echo foo"; # killall heartbeat would be a good alternative :-> disk { on-io-error panic; } syncer { rate 100M; # Note: 'M' is MegaBytes, not MegaBits } net { max-buffers 2048; ko-count 4; on-disconnect reconnect; } on rmcfs01 { device /dev/drbd0; disk /dev/cciss/c0d0p1; address 172.17.4.1:7789; meta-disk internal; } on rmcfs02 { device /dev/drbd0; disk /dev/cciss/c0d0p1; address 172.17.4.2:7789; meta-disk internal; } } -------------- next part -------------- global { usage-count no; } common { syncer { rate 100M; } protocol C; handlers { pri-on-incon-degr "echo o > /proc/sysrq-trigger ; halt -f"; pri-lost-after-sb "echo o > /proc/sysrq-trigger ; halt -f"; local-io-error "echo o > /proc/sysrq-trigger ; halt -f"; } disk { on-io-error call-local-io-error; } net { max-buffers 2048; ko-count 4; } } resource r0 { on rmcfs01 { device /dev/drbd0; disk /dev/cciss/c0d0p1; address 172.17.4.1:7789; meta-disk internal; } on rmcfs02 { device /dev/drbd0; disk /dev/cciss/c0d0p1; address 172.17.4.2:7789; meta-disk internal; } }