[vdr] Re: Problems with recording

[Klaus Schmidinger <Klaus.Schmidinger@cadsoft.de>]

Ulrich Petri wrote:
> 
> Hi,
> 
> I have some toubles with recordings when diskspace is low (about 2.5
> hours left)
> Vdr displays the "Low diskspace" message and shortly after this (approx.
> 30 sec to 1 min)
> Either it exits or i get an arm crash. Then the driver is reloaded and
> the cycle begins again.
> After freeing some space (time left after deleting approx. 4h)
> The recording went on flawlesly.
> 
> This happend 4 times until now.
> 
> Recently it happend on Sunday when i recorded Episode I on Pro7 and
> today with ST:Voy on Prem SCIFI.
> 
> Following are the importent parts of the logfile.
> 
> Apr 23 18:50:44 linux vdr[3818]: timer 1 start
> Apr 23 18:50:44 linux vdr[3818]: switching to channel 52
> Apr 23 18:50:44 linux vdr[3818]: Title: 'Star Trek: Raumschiff Voyager'
> Subtitle: 'Kollektiv'
> Apr 23 18:50:44 linux vdr[3818]: executing '/root/vdr_record before
> "/video0/Star_Trek#3A_Raumschiff_Voyager/Kollektiv/2002-04-23.18.48.55.4
> 0
> .rec"'
> Apr 23 18:50:44 linux vdr: Before recording
> /video0/Star_Trek#3A_Raumschiff_Voyager/Kollektiv/2002-04-23.18.48.55.40
> .rec
> Apr 23 18:50:44 linux vdr[3818]: record
> /video0/Star_Trek#3A_Raumschiff_Voyager/Kollektiv/2002-04-23.18.48.55.40
> .rec
> Apr 23 18:50:44 linux vdr[3818]: recording VDR file to

This message indicates to me that you must be using some patch(es)
(the original would be "recording to ..." - I wonder why a patch would
modify that).

> '/video0/Star_Trek#3A_Raumschiff_Voyager/Kollektiv/2002-04-23.18.48.55.4
> 0.rec/002.vdr'
> Apr 23 18:50:44 linux vdr[3959]: output thread started (pid=3959)
> Apr 23 18:50:44 linux vdr[3960]: input thread started (pid=3960)
> Apr 23 18:50:45 linux vdr[3818]: max. latency time 1 seconds
> Apr 23 18:50:45 linux vdr[3818]: low disk space while recording, trying
> to remove a deleted recording...
> Apr 23 18:50:45 linux vdr[3818]: ...no deleted recording found, trying
> to delete an old recording...
> Apr 23 18:50:45 linux vdr[3818]: ...no old recording found, giving up
> Apr 23 18:50:45 linux vdr[3818]: confirm: Platte beinahe voll!
> Apr 23 18:51:14 linux vdr[3818]: not confirmed
> Apr 23 18:51:15 linux vdr[3818]: max. latency time 29 seconds
> Apr 23 18:51:16 linux vdr[3818]: ERROR: Kanal blockiert (zeichnet auf)!

This is odd! Apparently there was nobody there to confirm the message,
but immediately after the message disappeared there was an attempt to
switch the channel - how can that be?

> Apr 23 18:51:29 linux vdr[3960]: ERROR: video data stream broken
> Apr 23 18:51:29 linux vdr[3960]: initiating emergency exit
> 
> Apr 23 18:52:00 linux vdr[3960]: ERROR: video data stream broken
> Apr 23 18:52:00 linux vdr[3960]: initiating emergency exit
> Apr 23 18:52:15 linux vdr[3818]: PANIC: watchdog timer expired -
> exiting!
> 
> <snip driver reload & vdr start>
> 
> Apr 23 18:52:32 linux vdr[3989]: timer 1 start
> Apr 23 18:52:32 linux vdr[3989]: switching to channel 52
> Apr 23 18:52:33 linux vdr[3989]: Title: 'Star Trek: Raumschiff Voyager'
> Subtitle: 'Kollektiv'
> Apr 23 18:52:33 linux vdr[3989]: executing '/root/vdr_record before
> "/video0/Star_Trek#3A_Raumschiff_Voyager/Kollektiv/2002-04-23.18.48.55.4
> 0
> .rec"'
> Apr 23 18:52:33 linux vdr: Before recording
> /video0/Star_Trek#3A_Raumschiff_Voyager/Kollektiv/2002-04-23.18.48.55.40
> .rec
> Apr 23 18:52:33 linux vdr[3989]: record
> /video0/Star_Trek#3A_Raumschiff_Voyager/Kollektiv/2002-04-23.18.48.55.40
> .rec
> Apr 23 18:52:33 linux vdr[3989]: recording VDR file to

Here's that modified message again...

> '/video0/Star_Trek#3A_Raumschiff_Voyager/Kollektiv/2002-04-23.18.48.55.4
> 0.rec/003.vdr'
> Apr 23 18:52:33 linux vdr[4154]: output thread started (pid=4154)
> Apr 23 18:52:33 linux vdr[4155]: input thread started (pid=4155)
> Apr 23 18:52:34 linux vdr[3989]: max. latency time 1 seconds
> Apr 23 18:52:34 linux vdr[3989]: low disk space while recording, trying
> to remove a deleted recording...
> Apr 23 18:52:34 linux vdr[3989]: ...no deleted recording found, trying
> to delete an old recording...
> Apr 23 18:52:34 linux vdr[3989]: ...no old recording found, giving up
> Apr 23 18:52:34 linux vdr[3989]: confirm: Platte beinahe voll!
> Apr 23 18:53:05 linux vdr[3989]: not confirmed
> Apr 23 18:53:06 linux vdr[3989]: max. latency time 31 seconds

This time there was no attempt to switch channels...

> Apr 23 18:53:37 linux kernel: VFS: Disk change detected on device
> ide1(22,64)
> Apr 23 18:53:37 linux kernel: VFS: Disk change detected on device
> ide1(22,64)
> Apr 23 18:54:20 linux kernel: dvb0: ARM crashed!
> Apr 23 18:54:32 linux kernel: VFS: Disk change detected on device
> ide1(22,64)
> Apr 23 18:54:32 linux kernel: VFS: Disk change detected on device
> ide1(22,64)
> Apr 23 18:54:39 linux vdr[3989]: ERROR: Kanal blockiert (zeichnet auf)!

...oh, here is goes.

> Apr 23 18:54:43 linux kernel: VFS: Disk change detected on device
> ide1(22,64)
> Apr 23 18:54:49 linux last message repeated 3 times
> Apr 23 18:54:54 linux vdr[3989]: timer 1 first day set to 2002-04-24
> Apr 23 18:54:56 linux vdr[3989]: timer 1 deactivated
> Apr 23 18:55:01 linux vdr[3989]: buffer stats: 368856 (35%) used
> Apr 23 18:55:01 linux vdr[3989]: timer 1 stop
> 
> Hoping for answers....

This seems rather strange to me.
In case you are using any patches: can you try if this also happens
with plain vanilla VDR 1.01?

Klaus
-- 
_______________________________________________________________

Klaus Schmidinger                       Phone: +49-8635-6989-10
CadSoft Computer GmbH                   Fax:   +49-8635-6989-40
Hofmark 2                               Email:   kls@cadsoft.de
D-84568 Pleiskirchen, Germany           URL:     www.cadsoft.de
_______________________________________________________________