[sheepdog] [PATCH 2/2] sheep: forbid revival of orphan objects

[Hitoshi Mitake]

At Tue, 16 Dec 2014 15:18:18 +0100,
Valerio Pachera wrote:
> 
> 2014-12-16 15:07 GMT+01:00 Valerio Pachera <sirio81 at gmail.com>:
> > It works fine!
> ...
> > There's only this corner case to fix:
> > all vdi are removed then and the disconnected node joins back the cluster
> 
> Please, notice that the same logic should apply to multi device:
> 
> create some vdi
> unplug a disk
> remove some vdi
> plug back the disk
> 
> This still causes
> 
> Dec 16 15:10:16   INFO [main] recover_object_main(930) object recovery
> progress  74%
> Dec 16 15:10:16  ERROR [rw 30554] sheep_exec_req(1170) failed Network
> error between sheep, remote address: 192.168.10.5:7000, op name:
> READ_PEER
> Dec 16 15:10:16  ERROR [rw 30553] sheep_exec_req(1170) failed Network
> error between sheep, remote address: 192.168.10.5:7000, op name:
> READ_PEER
> Dec 16 15:10:16  ERROR [rw 30500] sheep_exec_req(1170) failed Network
> error between sheep, remote address: 192.168.10.5:7000, op name:
> READ_PEER
> Dec 16 15:10:16  ERROR [rw 30500] sheep_exec_req(1170) failed Network
> error between sheep, remote address: 192.168.10.4:7000, op name:
> READ_PEER
> Dec 16 15:10:16  ERROR [rw 30554] sheep_exec_req(1170) failed Network
> error between sheep, remote address: 192.168.10.4:7000, op name:
> READ_PEER
> Dec 16 15:10:16  ALERT [rw 30500] recover_replication_object(419)
> cannot access any replicas of fd32fc00000013 at epoch 2
> Dec 16 15:10:16  ALERT [rw 30500] recover_replication_object(420)
> clients may see old data
> Dec 16 15:10:16  ERROR [rw 30500] recover_replication_object(427) can
> not recover oid fd32fc00000013
> Dec 16 15:10:16  ERROR [rw 30500] recover_object_work(600) failed to
> recover object fd32fc00000013
> Dec 16 15:10:16  ALERT [rw 30554] recover_replication_object(419)
> cannot access any replicas of fd32fc0000000b at epoch 2
> Dec 16 15:10:16  ALERT [rw 30554] recover_replication_object(420)
> clients may see old data
> Dec 16 15:10:16  ERROR [rw 30554] recover_replication_object(427) can
> not recover oid fd32fc0000000b
> Dec 16 15:10:16  ERROR [rw 30554] recover_object_work(600) failed to
> recover object fd32fc0000000b
> Dec 16 15:10:16  ERROR [rw 30553] sheep_exec_req(1170) failed Network
> error between sheep, remote address: 192.168.10.4:7000, op name:
> READ_PEER
> Dec 16 15:10:16  ERROR [rw 30552] sheep_exec_req(1170) failed Network
> error between sheep, remote address: 192.168.10.5:7000, op name:
> READ_PEER
> Dec 16 15:10:16  ALERT [rw 30553] recover_replication_object(419)
> cannot access any replicas of fd32fc00000012 at epoch 2
> Dec 16 15:10:16  ALERT [rw 30553] recover_replication_object(420)
> clients may see old data
> Dec 16 15:10:16  ERROR [rw 30553] recover_replication_object(427) can
> not recover oid fd32fc00000012
> Dec 16 15:10:16  ERROR [rw 30553] recover_object_work(600) failed to
> recover object fd32fc00000012
> 
> Notice I'm not using the option --enable-diskvnodes.
> 
> Thank you.

To be honest, the design of current md should be refined
completely. I'll work on the issue related to md in the future.

Thanks,
Hitoshi

> -- 
> sheepdog mailing list
> sheepdog at lists.wpkg.org
> http://lists.wpkg.org/mailman/listinfo/sheepdog