Steps to reproduce:
Actual result:
Step 11: Error 'unmanagedDvm.storageSubsystem' spams Core's log, these errors identified a potential data inconsistency in the repository:
ERROR 2018-02-10T09:14:48 [134] - unmanagedDvm.storageSubsystem ()
02/10/2018: record_allocator_nas : invalid dfs_record 1159253 (ref_count: 0, mode 1) on device 1 before dfs_record deallocation.ERROR 2018-02-10T09:14:48 [134] - unmanagedDvm.storageSubsystem ()
02/10/2018: record_allocator_nas : invalid dfs_record 1159254 (ref_count: 0, mode 3) on device 1 before dfs_record deallocation.ERROR 2018-02-10T09:14:48 [134] - unmanagedDvm.storageSubsystem ()
02/10/2018: record_allocator_nas : invalid dfs_record 1159255 (ref_count: 0, mode 1) on device 1 before dfs_record deallocation....Failed to delete the records. The repository might be unavailable or corrupted
The operation with result type Replay.Core.Implementation.DedupeVolumeManager.DeleteRecordsResult (Delete Records; 1024 records; record IDs 0x1000000011cc96 (DvmDelete), 0x1000000011cc97 (DvmDelete), 0x1000000011cc98 (DvmDelete), 0x1000000011cc99 (DvmDelete), 0x1000000011cc9a (DvmDelete)...
Step 12: Replication has been failed with data inconsistency in the repository error - 'A bad record has been read. There may be a problem with the repository or the underlying storage device':
© ALL RIGHTS RESERVED. Feedback Terms of Use Privacy Cookie Preference Center