Can you turn your proxies request_node_count [3] >= 84 (3 nodes * 28 devices) and check again for the 404'd objects.
Do you have any dispersion populate/report data you can query [1]?
Can you describe your device failure/replacement procedure [2]?
Can you check the quarantined datadirs on the hosts - it shows they're empty - could be a mis-config throwing off reporting - unless... how have you been handling corrupted data?
Since this issue is troublshooting a particular deployment to attempt locate data or discover underlying bug(s) - it might be useful to move this to #openstack-swift on freenode for more responsive feedback - and then take the results of the investigation to create issue(s) for whatever gaps are uncovered.
e.g. this may turn out to be be a duplicate of lp bug #1619408
Can you turn your proxies request_node_count [3] >= 84 (3 nodes * 28 devices) and check again for the 404'd objects.
Do you have any dispersion populate/report data you can query [1]?
Can you describe your device failure/replacement procedure [2]?
Can you check the quarantined datadirs on the hosts - it shows they're empty - could be a mis-config throwing off reporting - unless... how have you been handling corrupted data?
Since this issue is troublshooting a particular deployment to attempt locate data or discover underlying bug(s) - it might be useful to move this to #openstack-swift on freenode for more responsive feedback - and then take the results of the investigation to create issue(s) for whatever gaps are uncovered.
e.g. this may turn out to be be a duplicate of lp bug #1619408
1. as covered in the admin guide - /docs.openstack .org/developer/ swift/admin_ guide.html# dispersion- report /docs.openstack .org/developer/ swift/admin_ guide.html# handling- drive-failure /docs.openstack .org/developer/ swift/deploymen t_guide. html#proxy- server- configuration
https:/
2. https:/
3. https:/