IPv6 address confusion in OSDs

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



We run a ten-node 64-OSD Ceph cluster and use IPv6 where possible.

Today I noticed this error message from an OSD just after I restarted
it (in an attempt to resolve an issue with some "stuck" pgs that
included that OSD):

2013-02-11 09:24:57.232811 osd.35 [ERR] map e768 had wrong cluster addr ([2001:620:0:6::106]:6822/1990 != my [fe80::67d:7bff:fef1:78b%vlan301]:6822/1990)

These two addresses belong to the same interface:

root@h1:~# ip -6 addr list dev vlan301
7: vlan301@bond0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 
    inet6 2001:620:0:6::106/64 scope global 
       valid_lft forever preferred_lft forever
    inet6 fe80::67d:7bff:fef1:78b/64 scope link 
       valid_lft forever preferred_lft forever

2001:620:... is the global-scope address, and this is how OSDs are
addressed in our ceph.conf.  fe80:... is the link-local address that
every IPv6 interface has.  Shouldn't these be treated as equivalent?
-- 
Simon.
--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [CEPH Users]     [Ceph Large]     [Information on CEPH]     [Linux BTRFS]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]
  Powered by Linux