[DRBD-user] uuid_compare()=-1000 by rule 100

Felix Frank ff at mpexnet.de
Mon Nov 29 16:16:41 CET 2010

Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.

On 11/25/2010 12:38 PM, Pavlos Parissis wrote:
> On 25 November 2010 11:43, Lars Ellenberg<lars.ellenberg at linbit.com>  wrote:
>> On Thu, Nov 25, 2010 at 11:32:02AM +0100, Pavlos Parissis wrote:
>>> I guess the result of -1000 on uuid_compare is quite cryptic and
>>> doesn't give you much information on the root cause.
>> Then don't focus on that line, but on the next:
>> Nov 24 15:00:27 pbxsrv3 kernel: block drbd2: Unrelated data, aborting!
>> Still cryptic?
> Yes :-)
> what is unrelated data? Can this occur also in other cases? or just in
> my specific scenario?

It happens whenever you connect 2 DRBDs that are not meant to connect.

> Is this uuid check for the node itself of the data?

The UUIDs are per device. After all, you can easily screw up by 
specifying a wrong peer port and connecting to the correct peer, but 
totally wrong device on that peer.

> I know I am asking to much but a log line like "request from unknown
> host" or something similar could be more specific.

See above. DRBD cannot infer that much information from a failed UUID check.


More information about the drbd-user mailing list