[sheepdog-users] copy policy for X not found, set 0

[Fabian Zimmermann]

Hi,

thanks for your answer:
> Do you mean:
>  - a node died with HDD crash
>  - you replaced the HDD
>  - formatted the node with new HDD with "dog cluster format"
>  - let the node join to your cluster
> ?
no, i mean:
- a node died with HDD crash
- i replaced the hdd
- i formated the hdd with a new fs (mkfs)
- let the node join to the cluster

Then the node started to recover, but the following msg are in the log:

>> Now my log contains a lot of:
>>
>> Jan 09 15:36:39  ALERT [main] get_vdi_copy_policy(117) copy policy for
>> 2f326 not found, set 0
>> Jan 09 15:36:39  ALERT [main] get_vdi_copy_policy(117) copy policy for
>> 2f326 not found, set 0
>> Jan 09 15:36:39  ALERT [main] get_vdi_copy_policy(117) copy policy for
>> 2f326 not found, set 0
>> Jan 09 15:36:39  ALERT [main] get_vdi_copy_policy(117) copy policy for
>> e31c5 not found, set 0
>> Jan 09 15:36:39  ALERT [main] get_vdi_copy_policy(117) copy policy for
>> e31c5 not found, set 0
>> Jan 09 15:36:39  ALERT [main] get_vdi_copy_policy(117) copy policy for
>> e31c5 not found, set 0
>> Jan 09 15:36:39  ALERT [main] get_vdi_copy_policy(117) copy policy for
>> 60e62 not found, set 0
>> Jan 09 15:36:39  ALERT [main] get_vdi_copy_policy(117) copy policy for
>> 60e62 not found, set 0
>> Jan 09 15:36:39  ALERT [main] get_vdi_copy_policy(117) copy policy for
>> 60e62 not found, set 0
>> Jan 09 15:36:39  ALERT [main] get_vdi_copy_policy(117) copy policy for
>> 2f326 not found, set 0
>> Jan 09 15:36:39  ALERT [main] get_vdi_copy_policy(117) copy policy for
>> 2f326 not found, set 0
>> Jan 09 15:36:39  ALERT [main] get_vdi_copy_policy(117) copy policy for
>> 2f326 not found, set 0
>> Jan 09 15:36:39  ALERT [main] get_vdi_copy_policy(117) copy policy for
>> 18f718 not found, set 0
>> Jan 09 15:36:39  ALERT [main] get_vdi_copy_policy(117) copy policy for
>> 18f718 not found, set 0
>> Jan 09 15:36:39  ALERT [main] get_vdi_copy_policy(117) copy policy for
>> 18f718 not found, set 0
>> Jan 09 15:36:39  ALERT [main] get_vdi_copy_policy(117) copy policy for
>> 9211f not found, set 0
>> Jan 09 15:36:39  ALERT [main] get_vdi_copy_policy(117) copy policy for
>> 9211f not found, set 0
>> Jan 09 15:36:39  ALERT [main] get_vdi_copy_policy(117) copy policy for
>> 9211f not found, set 0
>> Jan 09 15:36:39  ERROR [io 2247] sheep_exec_req(1096) failed Failed to
>> find requested tag
>> Jan 09 15:36:39  ERROR [io 2247] sheep_exec_req(1096) failed Failed to
>> find requested tag
>> Jan 09 15:36:39  ERROR [io 2247] sheep_exec_req(1096) failed Failed to
>> find requested tag
>> Jan 09 15:36:39  ERROR [io 2247] sheep_exec_req(1096) failed Failed to
>> find requested tag
>> Jan 09 15:36:45  ALERT [rw] get_vdi_copy_number(100) copy number for 0
>> not found, set 3
>> Jan 09 15:36:45  ALERT [rw] get_vdi_copy_number(100) copy number for 0
>> not found, set 3
>> Jan 09 15:36:45  ALERT [rw] get_vdi_copy_number(100) copy number for 0
>> not found, set 3
>> Jan 09 15:36:45  ALERT [rw] get_vdi_copy_number(100) copy number for 0
>> not found, set 3
>> Jan 09 15:36:45  ALERT [rw] get_vdi_copy_number(100) copy number for 0
>> not found, set 3
>> Jan 09 15:36:45  ALERT [rw] get_vdi_copy_number(100) copy number for 0
>> not found, set 3
>>
>> Should I have to worry about these lines?
>>
>> "dog cluster info" and "dog vdi list" still show "valid" information.
Thanks,

Fabian