For a few days now vdr has not been deleting recordings from the harddisk. They are deleted using osd and the name has properly changed from .rec to .del but the files stays. And there is no hint in log about why this is happening.
Any ideas?
- Kartsa
No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.308 / Virus Database: 266.11.2 - Release Date: 2.5.2005
Kartsa writes:
For a few days now vdr has not been deleting recordings from the harddisk. They are deleted using osd and the name has properly changed from .rec to .del but the files stays. And there is no hint in log about why this is happening.
Any ideas?
The .del files are normally deleted when the disk is full. Is it?
yours, Jouni
On Tue, 3 May 2005, Jouni Karvo (JK) wrote:
JK> JK> Kartsa writes: JK> > For a few days now vdr has not been deleting recordings from the JK> > harddisk. They are deleted using osd and the name has properly JK> > changed from .rec to .del but the files stays. And there is no hint JK> > in log about why this is happening. JK> > JK> > Any ideas? JK> JK> The .del files are normally deleted when the disk is full. Is it? JK>
no. as soon as VDR isn't busy for a couple of minutes.
c ya Sergei
By looking at the log I found that there has not been any removing after april 30th. As if the change of mont would have something to do with it.
The reason I noticed this was the fact that diskspace was running out even though there were not so many recordings on the disk (according to vdr).
- Kartsa
----- Original Message ----- From: "Sergei Haller" Sergei.Haller@math.uni-giessen.de To: "Klaus Schmidinger's VDR" vdr@linuxtv.org Sent: Tuesday, May 03, 2005 12:20 PM Subject: Re: [vdr] VDR not removing recordings
On Tue, 3 May 2005, Jouni Karvo (JK) wrote:
JK> JK> Kartsa writes: JK> > For a few days now vdr has not been deleting recordings from the JK> > harddisk. They are deleted using osd and the name has properly JK> > changed from .rec to .del but the files stays. And there is no hint JK> > in log about why this is happening. JK> > JK> > Any ideas? JK> JK> The .del files are normally deleted when the disk is full. Is it? JK>
no. as soon as VDR isn't busy for a couple of minutes.
c ya Sergei --
Kartsa wrote:
By looking at the log I found that there has not been any removing after april 30th. As if the change of mont would have something to do with it.
The reason I noticed this was the fact that diskspace was running out even though there were not so many recordings on the disk (according to vdr).
Check your system log. There should be messages like this:
: low disk space while recording, trying to remove a deleted recording... : ...no deleted recording found, trying to delete an old recording... : deleting recording xxxxx.rec : low disk space while recording, trying to remove a deleted recording... : removing recording xxxxx.del
or
: ...no old recording found, giving up
Check for any error messages in that area.
Possible reasons: Does VDR have full write access to the recordings?
Cheers,
Udo
On Tue, 3 May 2005, Udo Richter (UR) wrote:
UR> Kartsa wrote: UR> > By looking at the log I found that there has not been any removing after UR> > april 30th. As if the change of mont would have something to do with it. UR> > UR> > The reason I noticed this was the fact that diskspace was running out UR> > even though there were not so many recordings on the disk (according to UR> > vdr). UR> UR> Check your system log. There should be messages like this: UR> UR> : low disk space while recording, trying to remove a deleted recording... UR> : ...no deleted recording found, trying to delete an old recording... UR> : deleting recording xxxxx.rec UR> : low disk space while recording, trying to remove a deleted recording... UR> : removing recording xxxxx.del UR> UR> or UR> UR> : ...no old recording found, giving up UR> UR> Check for any error messages in that area.
Kartsa is talking about something different: he delets a recording via VDR recordings menu. the recording's directory is renamed from .rec to .del, but never actually deleted from the harddisk.
c ya Sergei
----- Original Message ----- From: "Sergei Haller" Sergei.Haller@math.uni-giessen.de
On Tue, 3 May 2005, Udo Richter (UR) wrote:
UR> Kartsa wrote: UR> > By looking at the log I found that there has not been any removing after UR> > april 30th. As if the change of mont would have something to do with it. UR> > UR> > The reason I noticed this was the fact that diskspace was running out UR> > even though there were not so many recordings on the disk (according to UR> > vdr). UR> UR> Check your system log. There should be messages like this: UR> UR> : low disk space while recording, trying to remove a deleted recording... UR> : ...no deleted recording found, trying to delete an old recording... UR> : deleting recording xxxxx.rec UR> : low disk space while recording, trying to remove a deleted recording... UR> : removing recording xxxxx.del UR> UR> or UR> UR> : ...no old recording found, giving up UR> UR> Check for any error messages in that area.
Kartsa is talking about something different: he delets a recording via VDR recordings menu. the recording's directory is renamed from .rec to .del, but never actually deleted from the harddisk.
Yep, and as I allready stated there is nothing in log that vdr would even try to remove the deleted recordings.
There is one low disk space entry in log from april 24th and vdr removed deleted recordings succesfully at that time. No low disk space entrys after that even though on may 2nd only 1GB was free and I was forced to remove deleted recordings manually.
Btw what is the low disk space limit?
- Kartsa
Kartsa wrote:
There is one low disk space entry in log from april 24th and vdr removed deleted recordings succesfully at that time.
Ok, I thought VDR would really run out of disk space without deleting anything.
Btw what is the low disk space limit?
Exactly 1Gb or 39min 46sec free space. Below that, automatic clean up should happen soon, giving the messages above.
If you ever run out of disk space while recording, there must be something about this in the log files.
If you're not recording and not cutting, VDR will check every hour for deleted recordings that can be cleaned up.
Cheers,
Udo
Sergei.Haller@math.uni-giessen.de(Sergei Haller) 03.05.05 11:20
On Tue, 3 May 2005, Jouni Karvo (JK) wrote:
JK>> JK>> Kartsa writes: JK>>> For a few days now vdr has not been deleting recordings from the JK>>> harddisk. They are deleted using osd and the name has properly JK>>> changed from .rec to .del but the files stays. And there is no JK>>> hint in log about why this is happening. JK>>> JK>>> Any ideas? JK>> JK>> The .del files are normally deleted when the disk is full. Is it? JK>>
no. as soon as VDR isn't busy for a couple of minutes.
And the disc is not 100% full.
recently my vdr ran into a race condition and did not delete files too. I thought it was a problem of my box/version, but it seems to be a general problem? Has it to do with the month change?
Rainer
kari@kniivila.com(Kartsa) 03.05.05 19:26
Btw what is the low disk space limit?
That's approx half an hour of of recording, 1GByte.
It would be usefull too to have "no free disk" warning when the cleanup issued by the low disk space failed because the disc is already more than 100% full so all threads blocks. Currently i only see teh warning" "low disk space" and have to hope(!) that vdr will find files to delete... After a while teh messges disappers, but that does not mean that now enough disk is free. If not VDR simply records "black" and issues every some minutes the same low dick warning, ignoring the "emergency" state the box is in menawhile.
Rainer
From: "Udo Richter" udo_richter@gmx.de
Kartsa wrote:
Btw what is the low disk space limit?
Exactly 1Gb or 39min 46sec free space. Below that, automatic clean up should happen soon, giving the messages above.
If you ever run out of disk space while recording, there must be something about this in the log files.
If you're not recording and not cutting, VDR will check every hour for deleted recordings that can be cleaned up.
As of writing this my vdr box has not been doing anything for about 12 hours (no recordings nor watching) and I have 16 recordings on the disk which are waiting to be removed. All of those are deleted more than 12 hours ago and some of them even a couple of days ago.
I am about to reboot my vdr box for other reasons and if restarting it will give me some results I'll report it back here.
- Kartsa
From: "Kartsa" kari@kniivila.com
From: "Udo Richter" udo_richter@gmx.de
Kartsa wrote:
Btw what is the low disk space limit?
Exactly 1Gb or 39min 46sec free space. Below that, automatic clean up should happen soon, giving the messages above.
If you ever run out of disk space while recording, there must be something about this in the log files.
If you're not recording and not cutting, VDR will check every hour for deleted recordings that can be cleaned up.
As of writing this my vdr box has not been doing anything for about 12 hours (no recordings nor watching) and I have 16 recordings on the disk which are waiting to be removed. All of those are deleted more than 12 hours ago and some of them even a couple of days ago.
I am about to reboot my vdr box for other reasons and if restarting it will give me some results I'll report it back here.
After a reboot vdr removed all deleted recordings as soon as it was up and running.
So it seems like there is something odd in vdr itself or in my configuration.
I have vdr 1.3.23 subtitles 0.3.7 vdradmin 0.97-am3.1
- Kartsa
Kartsa wrote:
So it seems like there is something odd in vdr itself or in my configuration.
Try to investigate a bit:
The important call is RemoveDeletedRecordings(); in vdr.c, and goes to void RemoveDeletedRecordings(void) in recording.c.
Try adding some dsyslog messages in that area to see messages whenever VDR is in the mood for cleanup.
The actual call may happen quite frequently, dont know, but if you go into the block after the REMOVECHECKDELTA test, you should get messages at most once an hour.
Cheers,
Udo
From: "Udo Richter" udo_richter@gmx.de
Kartsa wrote:
So it seems like there is something odd in vdr itself or in my configuration.
Try to investigate a bit:
The important call is RemoveDeletedRecordings(); in vdr.c, and goes to void RemoveDeletedRecordings(void) in recording.c.
Try adding some dsyslog messages in that area to see messages whenever VDR is in the mood for cleanup.
The actual call may happen quite frequently, dont know, but if you go into the block after the REMOVECHECKDELTA test, you should get messages at most once an hour.
The problem is that after the restart vdr is again working properly ant thus making it impossible to investigate anything. But I'll try to add some dsyslog in case this event will occur again.
- Kartsa
kari@kniivila.com(Kartsa) 04.05.05 23:02
From: "Udo Richter" udo_richter@gmx.de
Kartsa wrote:
So it seems like there is something odd in vdr itself or in my configuration.
Try to investigate a bit:
The important call is RemoveDeletedRecordings(); in vdr.c, and goes to void RemoveDeletedRecordings(void) in recording.c.
Try adding some dsyslog messages in that area to see messages whenever VDR is in the mood for cleanup.
The actual call may happen quite frequently, dont know, but if you go into the block after the REMOVECHECKDELTA test, you should get messages at most once an hour.
The problem is that after the restart vdr is again working properly ant thus making it impossible to investigate anything. But I'll try to add some dsyslog in case this event will occur again.
In my case that did not help (I have a menu entry to force a warmstart)
But my VDR version is quite old(VDR version 1.3.18), so i did got give it much attention (assuming to hear: "Why do you use such a old version?")
But Ok, it seems not to be fixed:
:24 : record /video0/I_T_A/Rajasthan:_Unterwegs/2005-05-04.18:59.50.07.rec :24 : creating directory /video0/I_T_A/Rajasthan:_Unterwegs :24 : ERROR: /video0/I_T_A/Rajasthan:_Unterwegs: No space left on device :24 : timer 53 (18 1859-1945 'In den Tiefen des Alls') stop :24 : switching device 2 to channel 18 :24 : timer 53 (18 1859-1945 'In den Tiefen des Alls') start :24 : Title: 'Legendäre Zugreisen' Subtitle: 'Rajasthan: Unterwegs auf Schienen zu den Maharajas' :24 : record /video0/I_T_A/Rajasthan:_Unterwegs/2005-05-04.18:59.50.07.rec :24 : creating directory /video0/I_T_A/Rajasthan:_Unterwegs :24 : ERROR: /video0/I_T_A/Rajasthan:_Unterwegs: No space left on device :24 : timer 53 (18 1859-1945 'In den Tiefen des Alls') stop :24 : switching device 2 to channel 18 :24 : timer 53 (18 1859-1945 'In den Tiefen des Alls') start :24 : Title: 'Legendäre Zugreisen' Subtitle: 'Rajasthan: Unterwegs auf Schienen zu den Maharajas' :24 : record /video0/I_T_A/Rajasthan:_Unterwegs/2005-05-04.18:59.50.07.rec :24 : creating directory /video0/I_T_A/Rajasthan:_Unterwegs :24 : ERROR: /video0/I_T_A/Rajasthan:_Unterwegs: No space left on device :24 : timer 53 (18 1859-1945 'In den Tiefen des Alls') stop :24 : switching device 2 to channel 18 :24 : timer 53 (18 1859-1945 'In den Tiefen des Alls
(i have trucated the names a bit)
See that this is a race condition? All these attemps occurs in the same second! (the entire log is filled with that!) That stops only when the timer stops!
Why is it trying to generate the directory again and again?
did not see the warining "confirm: Low disk space!" in the state of "No space left on device" OK, "Low disk space!" would not be teh correct message, it should be "NO disk space!"! Maybe that's the reson why the is not informed anymore about the critical state?
Is that fixed in newer releases?
Rainer Zocholl wrote:
See that this is a race condition? All these attemps occurs in the same second!
Actually not a race condition, more like a denial of service.
Had something similar once, because of missing write access to a folder. VDR fails and tries again and again. There is no 'giving up' state for VDR.
Is that fixed in newer releases?
Just compared sources, there are no relevant changes in that area between .18 and .23. So I would guess that updating wont solve your problem.
In that case where your disk did run full: Did you have remaining *.del recordings waiting for cleanup? Are you sure there were *.rec recordings that were free for deleting? These clean up old recordings rules are *very* tricky.
I'm working on a patch that marks 'ready to delete' recordings, because I usually let VDR decide what to delete and when. (just dont have the time to get it completed.) As long as you dont see what may get deleted, this strategy is a mine field.
Cheers,
Udo
Udo Richter wrote:
Rainer Zocholl wrote:
See that this is a race condition? All these attemps occurs in the same second!
Actually not a race condition, more like a denial of service.
Had something similar once, because of missing write access to a folder. VDR fails and tries again and again. There is no 'giving up' state for VDR.
Is that fixed in newer releases?
Just compared sources, there are no relevant changes in that area between .18 and .23. So I would guess that updating wont solve your problem.
In that case where your disk did run full: Did you have remaining *.del recordings waiting for cleanup? Are you sure there were *.rec recordings that were free for deleting? These clean up old recordings rules are *very* tricky.
I'm working on a patch that marks 'ready to delete' recordings, because I usually let VDR decide what to delete and when. (just dont have the time to get it completed.) As long as you dont see what may get deleted, this strategy is a mine field.
Removing deleted recordings works just fine for me, as does automatic deleting/removing in case thedisk runs full while recording. I've never had any problem like the ones described here.
Maybe it's a problem with some patches or plugins? I use plain vanilla VDR.
Klaus
udo_richter@gmx.de(Udo Richter) 06.05.05 02:40
Rainer Zocholl wrote:
See that this is a race condition? All these attemps occurs in the same second!
Actually not a race condition, more like a denial of service.
OK. a "It does not work any more"-state ;-)
Had something similar once, because of missing write access to a folder. VDR fails and tries again and again. There is no 'giving up' state for VDR.
Is that fixed in newer releases?
Just compared sources, there are no relevant changes in that area between .18 and .23. So I would guess that updating wont solve your problem.
Thanks.
In that case where your disk did run full: Did you have remaining *.del recordings waiting for cleanup?
Yes. I deleted them manually finally form console I was very upset as i marked recordings over recordings for deletion, and VDR did not delete them. So i rebooted VDR "usually" a rebooted VDR "usually" first removes all "*.del" but it did not AFAIR Maybe that "cleanup" did not happen because a recording immediately starts?
Next time i will write down what was done. Now it's 10 days ago and i did not pay much attention to it.
Are you sure there were *.rec recordings that were free for deleting? These clean up old recordings rules are *very* tricky.
Seems so..no KISS ;-)
I'm working on a patch that marks 'ready to delete' recordings, because I usually let VDR decide what to delete and when. (just dont have the time to get it completed.) As long as you dont see what may get deleted, this strategy is a mine field.
"find -mane '*.del'" helps and is very fast.
But a key: "please lauch the deletion thread now" would be nice. Too a record size indicator would be nice, as i have still some recordings with VPS and it happens, that VDR restarts the recording at the begin of the next programm and sometime it records until i turn off the box... Rainer---<=====> Vertraulich // // <=====>--------------ocholl, Kiel, Germany ------------
Klaus.Schmidinger@cadsoft.de(Klaus Schmidinger) 06.05.05 10:41
Removing deleted recordings works just fine for me, as does automatic deleting/removing in case thedisk runs full while recording. I've never had any problem like the ones described here.
Maybe it's a problem with some patches or plugins? I use plain vanilla VDR.
This happens VERY seldom. Maybe one in 6 weeks or less. And as i know your system, it never touches "100% full" often. The "non-deletion" seems to occur when the disk 100% full. But OK, the question is: How could teh disk become 100% full when there are .del directries?
Maybe i noticed the low disk condition and deleted some recording? or maybe meanwhile the keep time expired?
Currently i have a little bit too many times programmed (or keep time ist too long) so i often have to delete manually and VDR is very often at 100% or 100%-1GB. Maybe i can now force the problem.
A (red?)display "No free disk,\n recording stopped" would be helpful, instead of the "low disk" display, when the disk has nothing free.
Too sometimes i record with 3 or four cards. That maybe fills up the disk faster than that crappy "ext3" can delete file? :-( (I was really surpried how long it take to delete 1GB file. What is ext3 doing there? Maybe i should use XFS? Or JFS?)
I don't know which of the few plugins i should blame. Maybe the Teletext because it is writing on the same disc, so it fills faster than VDR expectes?
Then i have "femon" and "undelete". That's all. Not very impressive dangerous plugins IMHO
A, VDR is still running as "root". So it's possible to write more than 100% to the disc. Maybe that's the problem and VDR/linux needs a tiny bit free?
Rainer---<=====> Vertraulich // // <=====>--------------ocholl, Kiel, Germany ------------
On 08 May 2005 00:24:00 +0200, Rainer Zocholl wrote:
I'm working on a patch that marks 'ready to delete' recordings, because I usually let VDR decide what to delete and when. (just dont have the time to get it completed.) As long as you dont see what may get deleted, this strategy is a mine field.
"find -mane '*.del'" helps and is very fast.
This will only the primary directories, the secondaries reached by symbolic links will still be available and unvisable now.
Try the undelete plugin.
Cheers, Emil
Klaus.Schmidinger@cadsoft.de(Klaus Schmidinger) 08.05.05 10:48
Once upon a time "Klaus Schmidinger " shaped the electrons to say...
Rainer Zocholl wrote:
... have still some recordings with VPS and it happens, that VDR restarts the recording at the begin of the next programm and sometime it records until i turn off the box...
This has been improved in version 1.3.23.
Ah, thanks. I think i'll try ASAP.
Rainer
Emil.Naepflein@philosys.de(Emil Naepflein) 08.05.05 09:23
Once upon a time "Emil Naepflein " shaped the electrons to say...
On 08 May 2005 00:24:00 +0200, Rainer Zocholl wrote:
I'm working on a patch that marks 'ready to delete' recordings, because I usually let VDR decide what to delete and when. (just dont have the time to get it completed.) As long as you dont see what may get deleted, this strategy is a mine field.
"find -mane '*.del'" helps and is very fast.
This will only the primary directories, the secondaries reached by symbolic links will still be available and unvisable now.
Which symbolic links you you mean?
I had once tried to use 2 discs. But that failed totally (i reported). That's the reason why video home is still called "video0". But there is no video1 anymore.
Try the undelete plugin.
I have installer. Very nice. Next time i'll use it to see if my "delete now" commands were really executed when the disc is already entirely(!) filled up to the very last block! Maybe VDR is so busy with complaining "disc is full" into syslog, that there is no time to mark the recordings or lanch the deletion thread? But: As i wrote i did not pay much attention to that as it occured only twice the last 3 month and i assumed a PBCK.
Rainer
-
Emil Naepflein -
Jouni Karvo -
Kartsa -
Klaus Schmidinger -
Rainer Zocholl -
Sergei Haller -
Udo Richter