Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
Am 23.01.2013 um 19:01 schrieb Dan Barker: > If those time stamps are believable, then the problem occurred > before you started! > > I don't know of drbd accessing the config decks before a drbdadm > command, but it looks like you have proved that it happens. You > copied, it activated! Very strange result. I'll let the drbd authors > chime in on what new files in the config directory can cause before > you request something using them, but it looks like the way to do > this is to do the edit elsewhere, or "Save As" (:w <filename>). So we learned from this (again): Never configure on the fly. Edit your new resource-config in another place and then move it into / etc/drbd.d/. > > Actually, you have pacemaker and heartbeat in the mix. I imagine > they do watch directories for changes. It may not be drbd at all, > but drbdadm commands requested by those tools. The error-message comes from drbd/user/drbdadm_parser.c -> vcheck_uniq(). It checks if certain keys like resource-name in the config are unique. For some reasons this check seems to be activated via pacemaker/crm -> ocf:linbit:drbd -> monitor(?) -- as far as I understand the code. Helmut Wollmersdorfer