[mythtv-users] Backend Deleting Files for no Reason

Hika van den Hoven hikavdh at gmail.com
Sun Nov 10 13:12:40 UTC 2019


Hoi Greg,

Friday, November 8, 2019, 10:30:55 PM, you wrote:

> This has been happening to me sine I upgraded to v30, but it has
> always been shows I do not really care about, but it happened to me
> just a second ago while I was watching, so it bothered me.

> A recording that was there 5 minutes before just got deleted (but
> not from the recording list - just the file)..

> Nov  8 15:13:43 mythtv mythbackend: mythbackend[1020]: N
> DeleteThread mainserver.cpp:2502 (DeleteRecordedFiles)
> DeleteRecordedFiles - recording id 9940 filename
> /ramdisk/mythtv/recordings/10501_20191107020000.ts
> Nov  8 15:13:43 mythtv mythbackend: mythbackend[1020]: N
> DeleteThread mainserver.cpp:2579 (DoDeleteInDB) DoDeleteINDB -
> recording id 9940 (chanid 10501 at 2019-11-08T05:37:00Z)

> I know it also says doDeleteInDB, but it did not and the show had
> not been watched yet and just turned blue in the theme, so I know it happened.


> mythbackend.log:Nov  6 20:00:01 mythtv mythbackend:
> mythbackend[1020]: I TVRecEvent tv_rec.cpp:4231 (TuningNewRecorder)
> TVRec[5]: rec->GetPathname():
> '/ramdisk/mythtv/recordings/10501_20191107020000.ts'
> mythbackend.log:Nov  6 20:56:35 mythtv mythbackend:
> mythbackend[1020]: W TFWWrite threadedfilewriter.cpp:568 (DiskLoop)
> TFW(/ramdisk/mythtv/recordings/10501_20191107020000.ts:94):
> write(65424) cnt 41 total 2468440 -- took a long time, 1484 ms
> mythbackend.log:Nov  6 20:59:33 mythtv mythbackend:
> mythbackend[1020]: W TFWWrite threadedfilewriter.cpp:568 (DiskLoop)
> TFW(/ramdisk/mythtv/recordings/10501_20191107020000.ts:94):
> write(65424) cnt 49 total 3051804 -- took a long time, 1755 ms
> mythbackend.log:Nov  8 15:13:43 mythtv mythbackend:
> mythbackend[1020]: N DeleteThread mainserver.cpp:2502
> (DeleteRecordedFiles) DeleteRecordedFiles - recording id 9940
> filename /ramdisk/mythtv/recordings/10501_20191107020000.ts
> mythbackend.log:Nov  8 15:15:52 mythtv mythbackend:
> mythbackend[1020]: E ProcessRequest programinfo.cpp:2781
> (GetPlaybackURL) ProgramInfo(10501_20191107020000.ts):
> GetPlaybackURL: '10501_20191107020000.ts' should be local, but it can not be found.
> mythbackend.log:Nov  8 15:15:52 mythtv mythbackend:
> mythbackend[1020]: E ProcessRequest programinfo.cpp:2781
> (GetPlaybackURL) ProgramInfo(10501_20191107020000.ts):
> GetPlaybackURL: '10501_20191107020000.ts' should be local, but it can not be found.
> mythbackend.log:Nov  8 15:16:02 mythtv mythbackend:
> mythbackend[1020]: E ProcessRequest programinfo.cpp:2781
> (GetPlaybackURL) ProgramInfo(10501_20191107020000.ts):
> GetPlaybackURL: '10501_20191107020000.ts' should be local, but it can not be found.
> mythbackend.log:Nov  8 15:16:03 mythtv mythbackend:
> mythbackend[1020]: E ProcessRequest programinfo.cpp:2781
> (GetPlaybackURL) ProgramInfo(10501_20191107020000.ts):
> GetPlaybackURL: '10501_20191107020000.ts' should be local, but it can not be found.
> mythbackend.log:Nov  8 15:17:33 mythtv mythbackend:
> mythbackend[1020]: E ProcessRequest programinfo.cpp:2781
> (GetPlaybackURL) ProgramInfo(10501_20191107020000.ts):
> GetPlaybackURL: '10501_20191107020000.ts' should be local, but it can not be found.
> mythbackend.log:Nov  8 15:21:15 mythtv mythbackend:
> mythbackend[1020]: E ProcessRequest programinfo.cpp:2781
> (GetPlaybackURL) ProgramInfo(10501_20191107020000.ts):
> GetPlaybackURL: '10501_20191107020000.ts' should be local, but it can not be found.

> I see there were a couple hiccups writing according tot he block
> message, but the recording was not yellow (damaged) in the
> recordings screen.  Like I said - this has happened on more than one
> occasion, but I am just checking into it.


> Anyone know why it would select this recording and just delete it
> and not remove the metadata too?  I mean both are wrong, but 

Be aware that if all your current recordings are not set to
auto-expire and then record one that is set to auto-expire it will
immediately jump to the top of the list of recordings to expire.

The order of groups is if I'm not mistaken:
    deleted recordings
    live recordings
    watched recordings set to auto-expire
    unwatched recordings set to auto expire
    other watched recordings
    other unwatched recordings

Within a group the order is basically set on base of age and priority
set on recording. You can watch the list of recordings set to expire
in your frontend in the Information Center => System Status

So if your drive is full and you before never set any to auto-expire,
check your recordings on which of them to set to auto-expire.
This is easiest done in mythweb as there it only requires you to check
a checkbox on a recording.

This is not the complete story as, as Stephen said, that is a lot more
complicated.

Tot mails,
  Hika                            mailto:hikavdh at gmail.com

"Zonder hoop kun je niet leven
Zonder leven is er geen hoop
Het eeuwige dilemma
Zeker als je hoop moet vernietigen om te kunnen overleven!"

De lerende Mens



More information about the mythtv-users mailing list