This clone is to fix this BZ in Hammer / RHCS 1.3.
+++ This bug was initially created as a clone of Bug #1318055 +++
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):
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.
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.
No orphaned file, crashes, or pg inconsistencies.
--- Additional comment from Samuel Just on 2016-03-15 17:52:51 EDT ---
https://github.com/ceph/ceph/pull/8136 -- merged. Not backported to hammer yet.
--- Additional comment from Samuel Just on 2016-04-08 10:41:56 EDT ---
Still needs backport to hammer.
Change was merged to hammer upstream and will be in v0.94.8.
Sam is there a Teuthology test for this? (how would I find that information myself? Would I see some reference to the upstream Redmine ticket in ceph-qa-suite.git?)
medium priority for 1.3.3. testing.
Followed the bug description and didn't find any orphan objects or crashed.
Hence marking this as verified.
Verified on 0.94.9-1.el7cp.x86_64
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.