Bug #20243
Updated by David Zafman almost 7 years ago
With this error state <pre> shard disk size oi size 0 1 0 1 1 1 2 1 1 </pre> Currently all we see is object_info_inconsistency and attr_value_mismatch. Without snapshots there is no info from list-inconsistent-snapset which included some additional size checking. In be_select_auth_object we should check for a shards disk size vs oi_size. This should be a new disk_size_shard error. This would make that shard less likely to be the authoritative one. We should ignore system xattrs when checking for attr_value_mismatch. We will ignore strange xattr keys and never report a attr_name_mismatch. Already present in the code: We have object error size_mismatch when different shard don't have the same disk size (maybe rename to disk_size_mismatch too?) We have shard error size_mismatch_oi which like other _oi errors means the disk size doesn't match the authoritative size