Repository maintenance fails with the following error, when previously had been working fine.
Depending on the repository configuration, you may see the maintenance run for a while and fail, or fail right at the beginning.
With multiple extents, you would always see the failure at the exact same spot moving from 1 extent to another.
This may appear as a permissions issue, although the repository files can be browsed.
ERROR 2016-03-01T07:32:38 [218] - Replay.Core.Implementation.Repositories.Jobs.CheckRepositoryJob ()
Job 'Check repository 'Repository1'' failed
System.AggregateException: One or more errors occurred. ---> System.AggregateException: One or more errors occurred. ---> Replay.Core.Contracts.DedupeVolumeManager.DedupeVolumeManagerException: File system I/O error
Other stack trace examples:
Error checking the file system: 'ff639732-8061-446a-a91f-2e8a8629b75b', data path: 'c:\DLDisks\Repository1\disk_6B083FE0DC8BED001D8EE3BA8AEF920A\File_1', metadata path: 'c:\DLDisks\Repository1\disk_6B083FE0DC8BED001D8EE3BA8AEF920A\File_1' - Error(s) 'DvmFSIO'
at Replay.Core.Implementation.DedupeVolumeManager.Dvm.<>c__DisplayClass4.<StartFileSystemCheck>b__1()
at System.Threading.Tasks.Task.Execute()
--- End of inner exception stack trace ---
at System.Threading.Tasks.Task.Wait(Int32 millisecondsTimeout, CancellationToken cancellationToken)
at System.Threading.Tasks.Task.Wait()
at Replay.Core.Implementation.Repositories.Jobs.CheckRepositoryJob.CheckRepositoryTask()
at System.Threading.Tasks.Task.Execute()
--- End of inner exception stack trace ---
---> (Inner Exception #0) System.AggregateException: One or more errors occurred. ---> Replay.Core.Contracts.DedupeVolumeManager.DedupeVolumeManagerException: File system I/O error
ERROR 2016-03-01T07:32:38 [218] - unmanagedDvm.storageSubsystem ()
<01:32:38 PM> 03/01/2016: Scalar error reported. Windows error code 5
