<br><br><div><span class="gmail_quote">On 9/24/05, <b class="gmail_sendername">Todd Houle</b> <<a href="mailto:thoule@wesleyan.edu">thoule@wesleyan.edu</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
I was going to pull out my 80GB drive and put in a 180 that I have<br>it. I don't (yet) care about losing my recorded shows so I thought<br>I'd delete the recorded shows in Myth, then swap the drives. I found<br>that once I deleted the recorded shows in Myth, I still had about
<br>20GB of video still in the Myth directory! They looked like shows I<br>thought I deleted.. Sure enough, Myth said they were gone, but there<br>they were...<br><br>Is there a known problem where Myth doesn't delete what it thinks it
<br>does? That would account for lost disk space.<br> -t-<br><br><br>> > I started out with 150GB of disk space, but I recently increased<br>> that to<br>> > 300GB. Problem is, the machine information under mythweb is
<br>> still reporting<br>> > the old disk limit (150), not the new limit (300). I looked<br>> throught the<br>> > mysql database but was unable to find anything that suggests this<br>> number is<br>> > stored in the DB.
</blockquote><div><br>
<br>
There are occasional problems with that, probably due to some sort of
race condition when you delete files quickly. I've got an old
script I snagged from someone that will help find those files:<br>
<br>
#!/bin/sh<br>
for i in `mysql -u mythtv --password=mythtv mythconverg -e \<br>
'select chanid, starttime, endtime from recorded' |<br>
perl -wne 'next if $. == 1; s/|//g; s/-//g; s/://g; @_ = split;<br>
print join( '_', $_[0], $_[1].$_[2], $_[3].$_[4]) . ".nuv\n";'` \<br>
`ls *.nuv`;<br>
do echo $i; done | sort | uniq -u | xargs du -sh | grep nuv$<br>
<br>
<br>
It'll print a list of nuv files in the directory that aren't in the database.<br>
<br>
<br>
</div><br></div><br>