[mythtv-users] Myth 0.21 expiring ALL shows too soon with TONS of disk space available

[Ryan McDonald]

>It is quite likely a case of 32bit vs 64bit

Might be true.  4T can be expressed as a 32-bit number whereas 5.5T 
can't.  Is there a change-log or bug-report anywhere that shows a 32/64 
problem has been fixed with the file system?  (The normal change-logs 
don't mention it). Upgrading is be a *HUGE* pain in this case.  I'd like 
to confirm an upgrade is known to fix this problem before upgrading.  
This system is used in the enterprise by about 180 people (literally) 
with a custom front end.  Downtime (or possible loss of media) is not 
practical.

-Ryan






On 05/02/12 13:28, Gavin Hurlbut wrote:
> On Wed, May 2, 2012 at 10:34 AM, Ryan McDonald<mcdonald.ryan at gmail.com>  wrote:
>> I have a myth 0.21 system that has been working perfectly for quite a while.
>>   I recently lost the 4TB internal array I was running due to a drive
>> failure.  I replaced it with a 5.5TB internal array.  I did this simply by:
>
> Seriously?  0.21 is about 4 years old.  I'm sure this bug has been
> fixed since.  It is quite likely a case of 32bit vs 64bit on the disk
> free.  I seem to recall having fixed this in the last year or two.
>
> Unless you have a burning desire to stay with 0.21, I would strongly
> suggest upgrading to something newer.
> _______________________________________________
> mythtv-users mailing list
> mythtv-users at mythtv.org
> http://www.mythtv.org/mailman/listinfo/mythtv-users