Bug #4289

Setting the memory limit in DVR profile breaks all recordings with "Not enough disk space" error

Added by Marco Jakobs over 1 year ago. Updated about 1 year ago.

Status:InvalidStart date:2017-03-17
Priority:NormalDue date:
Assignee:Adam Sutton% Done:

0%

Category:PVR / DVR
Target version:-
Found in version:2431-2482 Affected Versions:

Description

This bug was introduced betweek build 2402 and 2431.

I was always using the option to limit the DVR memory use to 2TB in the DVR profile (see attached screenshot). That was never an issue.

After updating from 2402 to 2482 I did loose a show which was not recorded. Error message was "Not enough disk space", although 2.4TB were free on the mount where TVH stores the recordings.

I went back several versions down to 2431 which was the oldest build accessable by me. The error persists, going back to 2402 and it was working again.

Finally I found out that disabling the option to limit the memory which is used by the DVR in the profile (setting the number to 0) solved this and the recordings are working again. Seems that a bug introduced in a build between 2402 and 2431 did break the memory limit option and renders recording unusable due to the "Not enough disk space" error.

TVH_DVRbug.jpg - Parameter which causes the bug, must be set to "0" now (44.3 KB) Marco Jakobs, 2017-03-17 13:05

TVH Storage.jpg (5.71 KB) Marco Jakobs, 2017-03-20 12:46

History

#1 Updated by glenn ch about 1 year ago

What does the tvheadend webinterface show for free/used and total disk space?
Does it work when manually you delete a recording before starting a new one?

#2 Updated by Marco Jakobs about 1 year ago

glenn ch wrote:

What does the tvheadend webinterface show for free/used and total disk space?

The display here is correct, see attached screenshot.

Does it work when manually you delete a recording before starting a new one?

No, that does not help. It seems once the memory limitation is set in the DVR profile it just does not do any recordings and fails with "Not enough disk space" error.

#3 Updated by glenn ch about 1 year ago

I cannot reproduce your issue but I noticed your screenshot shows "2000" as max storage use setting.
This setting is in MiB, not GB, so you need another three "0".

If this is not the problem, please post a debug log.

#4 Updated by Marco Jakobs about 1 year ago

Hi Glenn,

OK, that seems to be the problem. But it was working for >1 year with the same setting, was it changed from GB to MiB at some point? Or it was my stupidity a year ago, not taking affect to a bug which was now recently fixed.

That issue can be closed, thanks for pointing out!

#5 Updated by Jaroslav Kysela about 1 year ago

  • Status changed from New to Invalid

Also available in: Atom PDF