Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
> What is the best way to manage a split-brain on a Master<>Master setup on > DRBD 8.0 ? > I would go with stonith to prevent it and let the running one bring up the shot node. Or if your stonith device is configurable let the poweroff be short (15 s). > DRBD will see by itself see if a node is up for what I unserstood, but > what when a node comes back online, will it be automaticly sync it to 1-1 > for both ways ? > See the roadmap for detailed information on the various recovery methods. The master which keeps on running holds the most current state of the filesystem blocks is a nice assumption to use with the sync from the host with the most changes and highest internal version (not the right word, but look it up in the docs). > Some People claim that when node-2 came back online it needs to resync all > the data from node-01. Is this true, or is it smart enought to only sync > the new files ? > You never sync files. It's a smart *block* level replication. > If someone can give me some examples or can make this clear to me, this > would be great. > No examples yet, sorry.