fix: quorum requirement for DeleteMarkers and parity upgraded objects (#14248)
fix: quorum requirement for DeleteMarkers and parity upgraded objects (#14248)

DeleteMarkers do not have a default quorum, i.e it is possible that
DeleteMarkers were created with n/2+1 quorum as well to make sure
that we satisfy situations such as those we need to make sure delete
markers only expect n/2 read quorum.

Additionally we should also look at additional metadata on the
actual objects that might have been "erasure" upgraded with new
parity when disks are down.

In such a scenario do not default to the standard storage class
parity, instead use the parityBlocks present on the FileInfo to
ensure that we are dealing with the correct quorum for READs and
DELETEs.
krisis/minio,donatello/minio,balamurugana/minio,minio/minio,vadmeste/minio,minio/minio,vadmeste/minio,balamurugana/minio,krisis/minio,donatello/minio