Actions
Bug #14938
closed[hammer] repeated puts on an object can violate the pool quota
Status:
Won't Fix
Priority:
Urgent
Assignee:
-
Category:
-
Target version:
-
% Done:
0%
Source:
other
Tags:
Backport:
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):
Description
This is easy to reproduce in hammer. It seems that we don't throw out the cached obc object info and on the second put erroneously believe that we are overwriting an existing object of the same size. On current master, the client blocks on the osdmap full flag, but I suspect that the bug is still present osd-side, just harder to trigger.
Updated by Samuel Just about 8 years ago
- Subject changed from [hammer] repeated puts on an object can violate the pool quota to [hammer, also master?] repeated puts on an object can violate the pool quota
Updated by Samuel Just about 8 years ago
- Subject changed from [hammer, also master?] repeated puts on an object can violate the pool quota to [hammer] repeated puts on an object can violate the pool quota
- Status changed from New to Won't Fix
Actually, this is fixed in master. It's too complicated to backport imho. Marking won't fix.
Actions