<div class="gmail_quote">On Fri, Feb 3, 2012 at 11:15 AM, Michael T. Dean <span dir="ltr"><<a href="mailto:mtdean@thirdcontact.com">mtdean@thirdcontact.com</a>></span> wrote:<br><blockquote style="margin:0px 0px 0px 0.8ex;padding-left:1ex;border-left-color:rgb(204,204,204);border-left-width:1px;border-left-style:solid" class="gmail_quote">
<div class="im">In theory you'll never get any orphans unless "someone" does something bad.<br>
a) Something deletes MythTV recording files via the file system<br>
rather than using MythTV to delete them.<br>
b) Something edits the database directly.<br>
c) A HDD dies and you lose files as a result (in this case, running<br>
find_orphans.py is a good idea).<br>
<br>
So, really, there's no reason to run it unless someone does bad things<br>
or you lose a HDD.<br>
<br>
FWIW, I've never had any orphaned recording files (files without<br>
metadata in my database) and the only orphaned recording metadata (with<br>
missing files on the file system) I've ever had were due to losing files<br>
when HDDs fail. I do, occasionally, get a few orphaned preview images,<br>
but their total size is always tiny compared to recordings and, we'll<br>
likely prevent that from occurring with changes coming for 0.26.</div><div class="im"> </div></blockquote><div> </div><div>That's pretty awesome, this fixed my problem! Thanks for the help guys! </div></div>