search

rancher / convoy

A Docker volume plugin, managing persistent container volumes.
Apache License 2.0
1.31k stars 135 forks source link

Errors in Convoy log when backing up to S3 #200

Open peebles opened 7 years ago

peebles commented 7 years ago

Using the devicemapper driver, during a snapshot backup, I see a significant number of errors that looks like:

DEBU[2680] Generated snapshot changed blocks metadata    event=compare last_snapshot=snapvol120170302022205 object=snapshot pkg=objectstore reason=complete snapshot=snapvol120170302025135
DEBU[2680] Creating backup                               event=backup object=snapshot pkg=objectstore reason=start snapshot=snapvol120170302025135
DEBU[2680] Backup for snapvol120170302025135: segment 1/20, blocks 1/1  pkg=objectstore
ERRO[2681] {
  ContentType: "application/xml",
  Metadata: {

  }
}  pkg=s3
DEBU[2681] Created new block file at convoy-objectstore/volumes/vo/l1/vol1/blocks/a3/76/a376f5be6ac14a80f8a4ea01f6efb405c5dacf604cb256f0b00a0c668156e2a7.blk  pkg=objectstore
DEBU[2681] Backup for snapvol120170302025135: segment 2/20, blocks 1/1  pkg=objectstore
ERRO[2682] {
  ContentType: "application/xml",
  Metadata: {

  }
}  pkg=s3

Yet, many blocks do not have this (apparent) error, and the overall backup operation does not return an error ... it appears to the caller to have succeeded. Should I be worried?