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

Fabian Zimmermann dev.faz at gmail.com
Fri Jan 9 16:19:37 CET 2015


Hello,

just had to replace a node in my cluster, because a hdd died. I replaced
the hdd, created a new fs and started sheepdog again.

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 a lot,

Fabian



More information about the sheepdog-users mailing list