I recently built a new Windows 11 system, as my old 10 box was showing its age, and I'm running into a very strange problem with Sonarr in conjunction with DP.
Both Sonarr and DP report 800 GB of free space. This is based on a target pool with a total of 83 TB (soon to be 101 TB, as I just received another drive today). I know weird things can start to happen when a file system approaches zero space, but 800 GB seems like plenty of play.
The problem is that Sonarr can't import anything to the pool, as it doesn't think it has the necessary space. These are (relatively) small episodic files at around 7 GB each. I know this because I went through the latest Sonarr log and saw this rather alarming entry:
"System.IO.IOException: There is not enough space on the disk."
I've done a few Google searches of this error as it relates to Sonarr, but it looks like whatever bug caused this was fixed long ago. I also scanned their Discord to see if this is a new bug, but no one has reported anything. As such, I can only surmise the problem is on DP's end.
So, any ideas? Is there some invisible drivespace overhead DP employs to manage pools that isn't reported to the user? I'm not doing any duplication, but even if I were, 800 GB is still 800 GB of presumably usable space. I'm using the latest versions of both DP and Scanner. Thanks in advance.
Question
fleggett1
I recently built a new Windows 11 system, as my old 10 box was showing its age, and I'm running into a very strange problem with Sonarr in conjunction with DP.
Both Sonarr and DP report 800 GB of free space. This is based on a target pool with a total of 83 TB (soon to be 101 TB, as I just received another drive today). I know weird things can start to happen when a file system approaches zero space, but 800 GB seems like plenty of play.
The problem is that Sonarr can't import anything to the pool, as it doesn't think it has the necessary space. These are (relatively) small episodic files at around 7 GB each. I know this because I went through the latest Sonarr log and saw this rather alarming entry:
I've done a few Google searches of this error as it relates to Sonarr, but it looks like whatever bug caused this was fixed long ago. I also scanned their Discord to see if this is a new bug, but no one has reported anything. As such, I can only surmise the problem is on DP's end.
So, any ideas? Is there some invisible drivespace overhead DP employs to manage pools that isn't reported to the user? I'm not doing any duplication, but even if I were, 800 GB is still 800 GB of presumably usable space. I'm using the latest versions of both DP and Scanner. Thanks in advance.
Link to comment
Share on other sites
2 answers to this question
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.