Bug #16421
closed
deep-scrub seems to update the omap digest on objects without any omap entries
Added by Samuel Just almost 8 years ago.
Updated over 7 years ago.
Description
Strictly speaking, this is correct, but it's silly for deep-scrub to emit repops persisting the omap digest for an object with no omap entries.
- Priority changed from High to Urgent
I assume we have a separate field that indicates the omap count or something? Don't want to skip scrubbing because the primary has no omaps when the replicas do. ;)
- Status changed from New to In Progress
- Assignee set to Samuel Just
- Status changed from In Progress to Rejected
I can't figure out why I thought this was true. I checked the code and it looks like object_info_t comes into the world with digests set to the seed, which would match an empty omap. I also grepped a few logs from recent runs and I don't see any evidence of extra digest updates. If someone remembers, reopen with more details!
Also available in: Atom
PDF