[mythtv-users] Database issue? Recordings not showing up in frontend

[Paul Stillwell]

> On Sep 15, 2015, at 6:30 AM, Michael T. Dean <mtdean at thirdcontact.com> wrote:
> 
> On 09/15/2015 09:26 AM, Michael T. Dean wrote:
>> On 09/14/2015 10:44 PM, Mike Holden wrote:
>>> But deletepending appears to be 1 for the records posted earlier? Not sure I understand the comments about corrupted databases?
>> 
>> Ah, you're right. I misread it because of the bad wrapping and thought the filesize values were the deletepending values.
>> 
>> So, a 1 means that the backend was in the process of deleting them. Because they're not actually deleting, that means that something very bad happened to the backend when it was in the process and they got stuck in a limbo state, where they're not deleted, but they're not available.
> 
> BTW, something very bad like a very ugly shutdown (power outage/kill -KILL/...) at a very bad time (the tiny amount of time when deletion is in a dangerous state) right after the recordings were deleted.
> 
> Mike
> _______________________________________________
> mythtv-users mailing list
> mythtv-users at mythtv.org
> http://lists.mythtv.org/mailman/listinfo/mythtv-users
> http://wiki.mythtv.org/Mailing_List_etiquette
> MythTV Forums: https://forum.mythtv.org
> 

OK, looks like this is resolved for me. It looks like the recordings were stuck somehow and I was able to recover them by cleaning up the deletepending flag.

The very bad thing that happened to my database was find_orphans.py. I’m not sure what went wrong with it, but everything was fine until I ran that and then everything wasn’t fine. Now that I think about it, wasn’t there some scripts that we were not supposed to use anymore when we went to 0.27? I have some nagging thought in the back of my head about something changing and some scripts not working anymore, but I can’t remember.

Thanks to everyone for their help!!

Paul