[mythtv-users] Mythtv filling up disk space?

[Jonathan Seawright]

Well, I think I have my problem resolved now.... after my 3rd install of MythDora... I decided to let IT decide how to do the partitions and all seems to be working now! (oops)

I have a feeling it was simply filling up my main hdd space and ran out of memory.... 

However, I"ve gotten my system to freeze in cases where I tried to rip a copy protected CD/DVD ... I"m not sure about regular DVDs though, I"ll try that soon and let you guys know what happens in this thread.

Thanks for all the help so far! Through this list, i've gotten further in the past week than I have gotten in the past say... few months on my own ! :P

Jonathan Seawright
  ----- Original Message ----- 
  From: Brett Kosinski 
  To: Discussion about mythtv 
  Sent: Wednesday, June 06, 2007 10:02 AM
  Subject: Re: [mythtv-users] Mythtv filling up disk space?





  On 6/6/07, Michael T. Dean <mtdean at thirdcontact.com> wrote:
    On 06/06/2007 03:19 AM, Stefan van der Eijk wrote:
    > I'm also seeing that my disk is filling up, but it's not due to the
    > mysql database. I think it's due to recorded programs that have been
    > deleted, but the mythbackend process is still holding onto them: 
    >
    > # lsof | grep myth | grep deleted
    > mythbacke 23174     mythtv   18r      REG                8,3
    > 2894512128   28181291
    > /var/lib/mythtv/recordings/1028_20070604212500.mpg (deleted)
    >
    > Restarting the mythbackend process releases the diskspace.

    So disable slow deletes.

    Delete files slowly
    Some filesystems use a lot of resources when deleting large recording
    files.  This option makes Myth delete the file slowly on this backend to 
    lessen the impact.

    in mythtv-setup (on each backend).


  No, what he's describing, here, is something else.  On any Unix machine, if multiple processes have a file open, and someone comes along and makes an unlink() call on that file, the file won't actually be deleted until all processes close their file handles.  In this case, mythbackend has opened the file, for whatever reason, and has unlinked the file, but isn't closing it's currently opened file handle, and so the filesystem can't actually free the underlying disk space.  If this is true, it seems like a pretty serious bug. 

  To the original poster, what version of mythbackend are you running?  What's your use case, here?  Is there some sequence of operations which produces this behaviour 100% of the time?

  Brett.



------------------------------------------------------------------------------


  _______________________________________________
  mythtv-users mailing list
  mythtv-users at mythtv.org
  http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mythtv.org/pipermail/mythtv-users/attachments/20070606/1a1c8b24/attachment-0001.htm