I am running vdr 1.4.1. Some days ago I found it running in the morning. It hadn't shut down after a recording. Trying a manual shutdown gave the error message:
"Recording in -244 minutes. Really shutdown?" (not this message exactly, but the German version). Pressing "OK" did not work, I had to log in to a console and to do a "shutdown -h".
Reason: /video was full, no recordings could be deleted, so VDR tried in vain again and again to start the programmed recording.
Shouldn't VDR stop its well meant but useless efforts at the latest if the event to record is over?
Wolfgang
Wolfgang Fritz wrote:
I am running vdr 1.4.1. Some days ago I found it running in the morning. It hadn't shut down after a recording. Trying a manual shutdown gave the error message:
"Recording in -244 minutes. Really shutdown?" (not this message exactly, but the German version). Pressing "OK" did not work, I had to log in to a console and to do a "shutdown -h".
Reason: /video was full, no recordings could be deleted, so VDR tried in vain again and again to start the programmed recording.
Shouldn't VDR stop its well meant but useless efforts at the latest if the event to record is over?
Didn't you get any "Not enough disk space to start recording!" messages? VDR shouldn't even start a recording if there is less than 300MB of free disk space.
Klaus
Didn't you get any "Not enough disk space to start recording!" messages? VDR shouldn't even start a recording if there is less than 300MB of free disk space.
What if a recording is started when there is 301MB of free space. Will VDR stop recording before it completely fills the disk? This might prevent the system from booting if the disk becomes completely filled and there are no separate partitions for /video.
BR.
Stone wrote:
Didn't you get any "Not enough disk space to start recording!" messages? VDR shouldn't even start a recording if there is less than 300MB of free disk space.What if a recording is started when there is 301MB of free space. Will VDR stop recording before it completely fills the disk?
If the disk runs nearly full during a recording, VDR tries to remove old recordings to make space for new ones. If this isn't possible, it will record until the disk is full.
This might prevent the system from booting if the disk becomes completely filled and there are no separate partitions for /video.
You really should use separate partitions for system and video data.
Klaus
syphyr@gmail.com(Stone) 24.06.06 13:45
Didn't you get any "Not enough disk space to start recording!"
Never saw that message. (But i'm running a rather old VDRi 1.3.25, sorry, will upgrade ASAP!)
messages?
VDR shouldn't even start a recording if there is less than 300MB of free disk space.
What if a recording is started when there is 301MB of free space.
I would vote VDR stop any recordings at 0% free disks. It's not worth the trouble and performance degration IMHO. (The current VDR may be 120GB, meaning at least 60h of recordings... what do the last 15min minutes matter?)
Will VDR stop recording before it completely fills the disk? This might prevent the system from booting if the disk becomes completely filled and there are no separate partitions for /video.
This should only be posible if vdr running as "root" (that's not required nor recommended anymore IIRC) Only root can fillup up any byte of disk, making it fill over 100%... The trick is: for root some MB auf diskspace are reserved to avoid such race conditions.
If VDR is running as "root" (as in old installations) it should stop any recordings at those 300MB (1%?) to avoid any lockups.
Using a second partion does not really help in this 100% cases, because the deletion attempt may fail and too the write access will become slow...
Google and me found the following hints:
tune2fs - adjust tunable filesystem parameters on ext2/ext3 filesystems
Number of blocks reserved for root. Ext2 reserves some blocks for root so that if the filesystem fills up, it is still possible to do system administration without having to delete anything. The reserved amount is by default 5 percent, which on most disks isn't enough to be wasteful. However, for floppies there is no point in reserving any blocks.
-m reserved-blocks-percentage Set the percentage of reserved filesystem blocks.
-m minfree This value specifies the percentage of space held back from nor- mal users; the minimum free space threshold. The default value used is 10%. This value can be set to zero, however up to a factor of three in throughput will be lost over the performance obtained at a 10% threshold. Note that if the value is raised above the current usage level, users will be unable to allocate files until enough files have been deleted to get under the higher threshold.
The command ist named "tune2fs" not "tunefs2" as goggle said...
Klaus Schmidinger schrieb:
Wolfgang Fritz wrote:
I am running vdr 1.4.1. Some days ago I found it running in the morning. It hadn't shut down after a recording. Trying a manual shutdown gave the error message:
"Recording in -244 minutes. Really shutdown?" (not this message exactly, but the German version). Pressing "OK" did not work, I had to log in to a console and to do a "shutdown -h".
Reason: /video was full, no recordings could be deleted, so VDR tried in vain again and again to start the programmed recording.
Shouldn't VDR stop its well meant but useless efforts at the latest if the event to record is over?
Didn't you get any "Not enough disk space to start recording!" messages? VDR shouldn't even start a recording if there is less than 300MB of free disk space.
I attach a trimmed and zipped syslog excerpt documenting the event. During the editing I found that VDR was less confused than I thought: The last timer event was still running when I found the VDR powered up in the morning, but the log may be nevertheless interesting for you because VDR managed to fill up the video partition to 100 %
Wolfgang
Klaus
vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
-
Klaus Schmidinger -
Stone -
UseNet-Posting-Nospam-74308-＠zocki.toppoint.de -
Wolfgang Fritz