Server claiming drive full when its not

[davenlr]

My sagetv server (V7 on win7 64bit) using the service control, has suddenly started telling me the drive with my sagetv recording directory is full (2TB drive with 1TB free).

If I create a new subdirectory on that drive, and move all the files from the current subdirectory to the new one, then show the new directory as the recording directory, and remove the old one, it will start working again for a month or so, then say the drive is full again.

Does anyone know the cause/cure for this?

[bclenney]

In the Video Recording directories settings there is a diskspace usage rule. Maybe you have it set to leave that much available?

[davenlr]

Originally Posted by bclenney

In the Video Recording directories settings there is a diskspace usage rule. Maybe you have it set to leave that much available?

It is set to use all space.
Interestingly enough, when this happens, if I use the file system option to go to that drive, it has a red X on it, like Sage doesnt even know the drive is connected. Windows, however, sees it fine, and it passes all chkdsk tests. This all on the same computer.

[waynedunham]

Originally Posted by davenlr

My sagetv server (V7 on win7 64bit) using the service control, has suddenly started telling me the drive with my sagetv recording directory is full (2TB drive with 1TB free).

If I create a new subdirectory on that drive, and move all the files from the current subdirectory to the new one, then show the new directory as the recording directory, and remove the old one, it will start working again for a month or so, then say the drive is full again.

Does anyone know the cause/cure for this?

Check your Java Heap usage. I have seen that before and each time my Java Heap usage was at or very near the high limit.
I'm running the Sage Service on a WHS (old WHS, not the new one) machine. Shutting down the service and restarting has always got the drive free space reported by SageTv to be back where it belongs.

[evilpenguin]

That happened to me recently and it turned out to be because the UNC paths I was using for my recording drives stopped working in Sage for no good reason. I needed to go in and change them to absolute paths and things started working again.

[amac]

Evilpenquin's solution worked for me as well.
I removed the URI shared recording directories and replaced them with references to Windows mapped drives (to the same folders) and the video diskspace remaining is now accurate.

Prior to that, Sage was getting confused and reporting a ridiculously low number even when my local drives (not the URI based ones) had lots of free space.