Sonarr 2.0.0.2629
After the upgrade got this error:
Unable to set last write time: The process cannot access the file XXXX because it is being used by another process.
The fles were not in use by anything else except Sonar as it just renamed them prior to wanting to change the time stamp
Please pastebin more of the log, a single line doesn’t give enough context.
Is this sufficient? This worked fine before this update.
System.IO.IOException: The process cannot access the file ‘\10.0.0.1\Files\XXXX’ because it is being used by another process.
at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
at System.IO.Directory.OpenHandle(String path)
at System.IO.Directory.SetLastWriteTimeUtc(String path, DateTime lastWriteTimeUtc)
at NzbDrone.Common.Disk.DiskProviderBase.FolderSetLastWriteTime(String path, DateTime dateTime) in m:\BuildAgent\work\6c3239faf2b92630\src\NzbDrone.Common\Disk\DiskProviderBase.cs:line 303
at NzbDrone.Core.MediaFiles.MediaFileAttributeService.SetFolderLastWriteTime(String path, DateTime time) in m:\BuildAgent\work\6c3239faf2b92630\src\NzbDrone.Core\MediaFiles\MediaFileAttributeService.cs:line 74
at NzbDrone.Core.MediaFiles.EpisodeFileMovingService.TransferFile(EpisodeFile episodeFile, Series series, List`1 episodes, String destinationFilename, TransferMode mode) in m:\BuildAgent\work\6c3239faf2b92630\src\NzbDrone.Core\MediaFiles\EpisodeFileMovingService.cs:line 133
What system is that share running on?
Is this a torrent or a usenet download?
Nothing has changed in regards to this code in this release (it hasn’t changed in quite a long time).
This is just me manually importing series. So no downloads invovled. This worked OK for about 30 series until the latest upgrade. The share has always been on a separate windows box (same share worked fine before the upgrade)
I tried new series -the same
Just before the time stamp Sonarr is renaming the files (which works and shows that Sonarr has required access to the share). I guess is something to do with the rename process not releasing the files in time for the time stamp process?
Likely something on the share locks it briefly when its renamed and blocks the timestamp update. Or could be something as simple as the Series on the share is open in Windows explorer, which causes it to be locked in Windows (which seems totally overkill).
Eventually I want to remove this functionality because its very specific to FlexRAID, but that won’t likely be for some time.