orphaned inodes

[Thomas Templin]

Binary package hint: mythtv

After a while mythbackend needs a restart.
If not the whole partition get's filled up with orphaned inodes.

Paket Name: mythtv
Release: Ubuntu 9.04 jaunty (same on Intrepid)
Version: 0.21.0+fixes19136-0ubuntu2 (also with the Intrepid packages)

- Filesystem is ext3
- deleting recordings from the mythtv menu it shows that only ~100kB from a several GigB recording
  is shown as new free space on that drive
- the same shows a df -h
- after
    sudo /etc/init.d/mythbackend stop
  and
    sudo /etc/init.d/mythbackend start
  most of the orphaned inodes are free again, most of them not all of them
- after a reboot fschk reports and repairs the last orphaned inodes
   (uid and gid is of the inodes is the mythtv users / group id)

I remember this misbehaviour of mythbackend was reported long ago (myth 0.17? 0.18?)
IMO It is not a filsystem related problem due to the fact that a restart of mythbackend solves the problem.

[Mario Limonciello (superm1)]

Hi, thanks for the bug report. Upstream has stopped focusing on 0.21 based reports in preparation for a 0.22 release later this year. Can you please try to see if this bug is reproducible on 0.22? If it is, we can try to forward this bug upstream to get the right eyes focused on it.

We have builds of mythtv 0.22 available on a PPA to test. Please follow the directions at http://mythbuntu.org/auto-builds to enable them.

WARNING: If you intend to go back to 0.21, you will need to back up your database before upgrading.

Thanks!

[MarcRandolph (mrand)]

Howdy, we really do appreciate you opening this ticket to help improve Mythbuntu, but it needs to be closed for a number of reasons. The biggest one is that the MythTV developers have turned their efforts to the next version (0.22) and beyond and are no longer fixing bugs on 0.21.

The Mythbuntu team has builds of MythTV 0.22 available on a PPA if you are interested in upgrading. Please follow the directions at
http://mythbuntu.org/auto-builds to enable them. Please do not let the closing of this ticket dissuade you from opening a new ticket if this (or any other) problem occurs with 0.22.

WARNING: If you need to have the ability to revert back to 0.21, you will need to back up your database before upgrading since a 0.22
database can not be downgraded.

   Thanks!