@Test
  public void testBug41119() {
    String oldValue = System.getProperty(DiskStoreImpl.RECOVER_VALUE_PROPERTY_NAME);
    System.setProperty(DiskStoreImpl.RECOVER_VALUE_PROPERTY_NAME, "false");
    try {
      diskProps.setDiskDirs(dirs);
      diskProps.setPersistBackup(true);
      diskProps.setRegionName("testRecoverValuesFalse");
      region = DiskRegionHelperFactory.getSyncPersistOnlyRegion(cache, diskProps, Scope.LOCAL);
      region.put(1, 1);
      region.invalidate(1);
      region.put(1, 2);
      region.close();

      region = DiskRegionHelperFactory.getSyncPersistOnlyRegion(cache, diskProps, Scope.LOCAL);

      assertEquals(null, ((LocalRegion) region).getValueInVM(1));
      assertEquals(2, region.get(1));
    } finally {
      if (oldValue != null) {
        System.setProperty(DiskStoreImpl.RECOVER_VALUE_PROPERTY_NAME, oldValue);
      } else {
        System.clearProperty(DiskStoreImpl.RECOVER_VALUE_PROPERTY_NAME);
      }
    }
  }
This tests the case where potential of writing a dummy byte was there. The case would be
compactor terminating early. The create is present in both Htree as well as Oplog. When
recovery is done, the create is added to the Oplog createdEntrySet. Now while compactor
iterates over the entries in the region, it skips the created entry because its Htree Offset is
> -1. As a result it leaves it in created set & so when the compactor processes the created Set
it thinks that the entry is now referenced in the any of the subsequent oplogs & thus
overwrites it with a byte[].
geode-core/src/integrationTest/java/org/apache/geode/internal/cache/DiskRegRecoveryJUnitTest.java