[mythtv-users] Why doesn't 'delete recording' actually mean 'delete recording'?

[Clay]

...
> Thanks for the info.  It is all becoming clear to me now.
> 
> Allow me to expand on what I already wrote.  I think the
> undelete
> function is a fine feature. But what I find annoying and
> counter
> intuitive is the false low amount of free space mythtv
> tells me I
> have.  When I look on MythWeb or the machine status page in
> mythfrontend I am told the recording partition has a very
> low amount
> of space available for new recordings.  Of coarse the
> reported
> estimate for recording time follows the free space amount. 
> So that is
> also very low (last night myth told me I had 8 hours at
> average
> bitrate, 3 hours at max bit rate).
> 
> But in reality I have over half a terabyte in deleted
> recordings.  I
> just think myth should report that as "free
> space" and calculate the
> available recording time accordingly.  I'm sure some
> people will say
> my way is counter intuitive because MythTV free space and
> free space
> on the recording partition are not equal.  But I think it
> would be
> better.  Does this make since to anybody else?  Or am I
> coo-coo for
> cocoa puffs?
> 

My slave backend does all the QAM recording. Maybe it's serendipity but when the drive gets over ¾ full, recordings start getting pixelated and corrupt.
Having space 'available' but not actually there would not be an option.
Glad to see this feature can be turned off... in the event I ever upgrade, that is.
-- 
(M be/fe) GA-8I945G-MF, P4 631, CNPS7000,(2)KVR667D2N5/1G, WD 250GB, Seagate 500GB, SHM-165H6S, 7300GS,(2)PVR-150, Feisty 7.04, MythTV 0.20.2
(S fe/be) GA-8IHXP, P4 3.06,(4)256mb pc1066,(3)WD 120GB, Seagate 500GB, 7600GS, Aver A180, Edgy 6.10.