mtdean at thirdcontact
May 2, 2012, 11:45 AM
On 05/02/2012 02:39 PM, Ryan McDonald wrote:
Re: Myth 0.21 expiring ALL shows too soon with TONS of disk space available
[In reply to]
>> 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.
Yes, there were some issues fixed by Raymond Wagner before 0.25 release
that were caused by extremely-large single-filesystem sizes.
Upgrade to 0.25. Note that you can't do that in a single step--0.25
can't upgrade a 0.21-fixes database schema--so you'll have to go through
an intermediate version, such as installing current 0.24-fixes, running
mythtv-setup (and, perhaps mythfrontend) to upgrade your DB schema, then
installing current 0.25-fixes and running mythtv-setup to upgrade to
0.25 schema version.
mythtv-users mailing list
mythtv-users [at] mythtv