[mythtv-users] Database / storage housekeeping

Michael T. Dean mtdean at thirdcontact.com
Fri Mar 31 05:13:15 UTC 2006


On 03/30/2006 03:41 PM, Brian Wood wrote:

>On Mar 30, 2006, at 1:20 PM, Bryan Halter wrote:
>
>>Jeff Simpson wrote:
>>
>>>I recently happened to come across this error in my database logs:
>>>
>>>ERROR when trying to autoexpire file:
>>>/mnt/store//1311_20060213220000_20060213220000.nuv. File doesn't
>>>exist. Database metadata will not be removed.
>>>
>>>Turns out that file didn't exist, but the entry was still in the  
>>>logs.
>>>
>>The thread runs when it finishes a recording and it tries to  
>>autoexpire
>>a recording.  I don't have my db in front of my but you could dome  
>>some
>>SQL to pull out all the file names the DB thinks exist and `ls` on the
>>storage drive then send them through diff and see what's in one but  
>>not
>>the other.
>>
>So did the OP correct the problem ? Just "touch" the missing file and  
>it will then have something to delete and can go ahead and delete the  
>metadata.
>
>I'm not sure if this behavior is a good thing or not, it alerts you  
>to a problem, *if* you read the logs, which most people don't.
>
>I suppose if you had a lot of files stored on an NFS filesystem and  
>the network failed you wouldn't want the system to delete all of the  
>metadata associated with those files.
>  
>

With 0.19, you simply highlight the show in the Watch Recordings or 
Delete Recordings page and hit 'D' to delete.  Then, select "Yes" when 
prompted whether to really delete the recording information even though 
the file doesn't exist.

In current SVN, you can use the INFO button to get the 
FileNotFoundAction popup and select either Delete or get the detailed 
info about the recording.

Mike



More information about the mythtv-users mailing list