[mythtv-commits] Ticket #7936: MythTV is expiring just recorded recordings instead of older recordings

Tue Jan 19 19:38:50 UTC 2010

#7936: MythTV is expiring just recorded recordings instead of older recordings
----------------------------------------------------+-----------------------
 Reporter:  Jonathan Martens <jonathan@…>           |       Owner:  ijr       
     Type:  defect                                  |      Status:  new       
 Priority:  major                                   |   Milestone:  unknown   
Component:  MythTV - General                        |     Version:  0.22-fixes
 Severity:  high                                    |     Mlocked:  0         
----------------------------------------------------+-----------------------
 Since a few days I noticed I was loosing recordings (so it seemed).
 Yesterday I seem to have missed another. While grepping through my logfile
 I discovered that it was recorded, commercial flagged and after a while
 auto-expired:

 {{{
 [root at mythtv mythtv]# grep -i 'private practice' mythbackend.log
 2010-01-18 20:28:02.038 Started recording: Private Practice "Strange
 Bedfellows": channel 1062 on cardid 2, sourceid 1
 2010-01-18 20:28:02.051 scheduler: Started recording: Private Practice
 "Strange Bedfellows": channel 1062 on cardid 2, sourceid 1
 2010-01-18 21:25:02.689 Finished recording Private Practice "Strange
 Bedfellows": channel 1062
 2010-01-18 21:25:02.703 scheduler: Finished recording: Private Practice
 "Strange Bedfellows": channel 1062
 2010-01-18 21:25:02.973 Finished recording Private Practice "Strange
 Bedfellows": channel 1062
 2010-01-18 21:25:04.082 scheduler: Last message repeated 1 times: Finished
 recording: Private Practice "Strange Bedfellows": channel 1062
 2010-01-18 21:32:39.799 JobQueue: Commercial Flagging Starting for Private
 Practice "Strange Bedfellows" recorded from channel 1062 at Mon Jan 18
 20:28:00 2010
 2010-01-18 21:32:39.817 commflag: Commercial Flagging Starting: Private
 Practice "Strange Bedfellows" recorded from channel 1062 at Mon Jan 18
 20:28:00 2010
 2010-01-18 21:57:03.204 commflag: Commercial Flagging Finished: Private
 Practice "Strange Bedfellows" recorded from channel 1062 at Mon Jan 18
 20:28:00 2010 (3 commercial break(s))
 2010-01-18 22:06:39.408 Expiring 2186 MBytes for 1062 @ Mon Jan 18
 20:30:00 2010 => Private Practice "Strange Bedfellows"
 2010-01-18 22:06:39.784 autoexpire: Expiring Program: Expiring 2186 MBytes
 for 1062 @ Mon Jan 18 20:30:00 2010 => Private Practice "Strange
 Bedfellows"
 [root at mythtv mythtv]#
 }}}

 I just had a look at my disk capacity and it seemed almost full (99% of
 over 800Gb), so I can understand why MythTV is auto-expiring, however I am
 a bit puzzled that a recent recording is expired as I seem to have a lot
 of other recordings that can be expired (and should have expired first
 IMHO):

 {{{
 mysql> SELECT COUNT(*) FROM recorded WHERE autoexpire=1 AND preserve=0\G
 *************************** 1. row ***************************
 count(*): 187
 }}}

 I seem to have a lot of older recordings that are eligible for auto-
 expiring and fail to understand why the just recorded show was auto-
 expired before I even had a change to watch it.

 {{{
 mysql> SELECT starttime, endtime FROM recorded WHERE autoexpire=1 AND
 preserve=0 ORDER BY starttime ASC LIMIT 20;
 +---------------------+---------------------+
 | starttime           | endtime             |
 +---------------------+---------------------+
 | 2008-07-13 10:40:00 | 2008-07-13 11:08:00 |
 | 2008-07-13 11:00:00 | 2008-07-13 11:13:00 |
 | 2008-07-20 10:40:00 | 2008-07-20 11:16:00 |
 | 2008-07-20 23:33:00 | 2008-07-21 00:10:00 |
 | 2008-07-27 10:39:00 | 2008-07-27 11:14:00 |
 | 2008-08-02 20:23:00 | 2008-08-02 22:07:00 |
 | 2008-08-02 22:40:00 | 2008-08-03 00:50:00 |
 | 2008-08-16 22:45:00 | 2008-08-17 00:45:00 |
 | 2008-08-16 23:28:00 | 2008-08-17 06:33:00 |
 | 2008-08-17 23:35:00 | 2008-08-18 01:50:00 |
 | 2009-01-17 23:28:00 | 2009-01-18 01:40:00 |
 | 2009-01-19 20:23:00 | 2009-01-19 21:25:00 |
 | 2009-01-26 20:23:00 | 2009-01-26 21:25:00 |
 | 2009-01-28 13:58:00 | 2009-01-28 15:46:00 |
 | 2009-02-02 20:28:00 | 2009-02-02 21:25:00 |
 | 2009-02-09 20:28:00 | 2009-02-09 21:25:00 |
 | 2009-02-21 23:28:00 | 2009-02-22 00:25:00 |
 | 2009-02-27 22:48:00 | 2009-02-27 23:55:00 |
 | 2009-03-19 23:38:00 | 2009-03-20 00:43:00 |
 | 2009-04-16 22:48:00 | 2009-04-17 00:02:00 |
 +---------------------+---------------------+
 20 rows in set (0.00 sec)
 }}}

 If you need more information please let me know. I am willing to provide
 it as I am a bit disappointed by loosing recordings like this.

 I have taken the liberty of setting severity to high and upped priority to
 major as I think it can not be the intention of MythTV to work like this.
 Unfortunately I have this problem since a few weeks, but can not pinpoint
 exactly when it started.

 Current versions running (for both mythfrontend and mythbackend):

 {{{
 Please include all output in bug reports.
 MythTV Version   : 23074
 MythTV Branch    : branches/release-0-22-fixes/mythtv/
 Network Protocol : 50
 Library API      : 0.22.20091023-1
 QT Version       : 4.4.3
 Options compiled in:
  linux release using_oss using_alsa using_arts using_jack using_backend
 using_dvb using_firewire using_frontend using_hdhomerun using_hdpvr
 using_iptv using_ivtv using_joystick_menu using_libfftw3 using_lirc
 using_mheg using_opengl_video using_opengl_vsync using_qtwebkit using_v4l
 using_x11 using_xrandr using_xv using_xvmc using_xvmc_vld using_xvmcw
 using_bindings_perl using_bindings_python using_opengl using_vdpau
 using_ffmpeg_threads using_libavc_5_3 using_live using_mheg
 }}}

 These are installed as RPM from ATrpms.

-- 
Ticket URL: <http://svn.mythtv.org/trac/ticket/7936>
MythTV <http://www.mythtv.org/>
MythTV