Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
Hi, I have a question regarding the population of /dev/drbd/by-res/ path. I've done something like: 1) create new resource resA -> add to drbd.conf, device /dev/drbd0 2) drbdadm create-md resA 3) drbdadm adjust resA 4) drbdadm wait-connect resA, .., let it sync with other node .. 5) drbdadm down resA 6) remove resource resA from drbd.conf 7) create new resource resB -> add to drbd.conf, device /dev/drbd0 8) drbdadm create-md resB 9) drbdadm adjust resB 10) drbdadm wait-connect resB, .., let it sync with other node .. 11) Surprise, I see in /dev/drbd/by-res the old symlink named resA -> ../../drbd0, and not the new link named resB -> ../../drbd0. Do I have to consider special steps to shutdown & cleanup resources to keep the /dev/drbd/by-res/ mechanism functioning and to prevent it from clashing with follow-up resource creations recycling the same /dev/drbd device ? WR, Bruno -- bruno at ic3s.de bruno at voigt.tv -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 197 bytes Desc: OpenPGP digital signature URL: <http://lists.linbit.com/pipermail/drbd-user/attachments/20090325/7051a26f/attachment.pgp>