Description of problem: When a collection split occurs during a collection_move_rename on an ec object, it can result in the old link being orphaned in the parent directory (see the commits for details). Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. Create new cluster 2. Create ec pool with one pg. 3. Fill up pool by alternately creating a new object and overwriting an existing object. All of the objects should have names longer than 300 characters. 4. When the pg collection splits, there should be an orphaned file in the <pgid>_head/ directory for the single pg on the osds with the pg. Actual results: 4. is proof that the bug happened. The following symptoms may also occur depending on the exact objects created: Scrubbing the pg may result in the pg being reported incorrectly as inconsistent. Removing the orphaned file and re-scrubbing should cause the pg to stop being inconsistent. Causing the pg mapping to change may cause the ENOTEMPTY crash in the linked bug. Again, the file remaining in the collection directory will be the orphaned file. Expected results: No orphaned file, crashes, or pg inconsistencies. Additional info:
https://github.com/ceph/ceph/pull/8136 -- merged. Not backported to hammer yet.
Still needs backport to hammer.
Looks like that PR in comment 1 already made it into v10.2.0 upstream? If that's the case, would you please re-target this bz to 1.3.3?
Pending backport to hammer.
Oops, I guess this stays in the 2.0 release tag so I should leave it as POST?
It's in 10.2.0
It's in 10.2.0, so it's MODIFIED I guess
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHBA-2016-1755.html