On Wednesday, 9 October 2019 21:45:33 UTC+1, Chris Davies wrote:
>
> Here's where it's gone pear-shaped. The fsck fails during the cycling of 
> the metadata. I've added some debug to help identify what's going on, but I 
> can't see where the HTTPError is escaping without being rewritten as 
> NoSuchObject:
>

As far as getting my data back online I've worked aroud the problem. After 
several iterations I was able to add an "except HTTPError // if 404 then 
pass" type construct into the relevant part of metadata.py, which I've now 
removed again. I'm sure this isn't the correct solution, as HTTPError is 
almost always converted to NoSuchObject lower down in the code, but I can't 
see the failure path here to address it directly for you.

Regards,
Chris

-- 
You received this message because you are subscribed to the Google Groups 
"s3ql" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/s3ql/df2a63a1-9d1d-4a31-96f5-ce00f20e4afa%40googlegroups.com.

Reply via email to