[mythtv-users] Myth 0.21 expiring ALL shows too soon with TONS of disk space available
mcdonald.ryan at gmail.com
Wed May 2 19:12:06 UTC 2012
Thanks for the replies everyone. Two questions though.
1 - For 32-bit hosts, the fix first appears in 0.25? (or in some 0.24
2 - The way I understand the issue is that there is a problem evaluating
the value that is returned by the "HowMuchSpaceIsLeft()" function.
Assuming this is true, if I *had* to stay at 0.21, couldn't I just dd a
bunch of 250MB /dev/zero files into the file system so that the disk
always has <1T remaining at any one given time? Then, I'd slowly remove
these dummy files until they are all replaced by actual media. Would
Also.... If I'm sitting at 0.21 right now, which versions do I need to
install BEFORE I upgrade to 0.25 to make sure all the schemas get updated?
On 05/02/12 13:56, Raymond Wagner wrote:
> On 5/2/2012 14:39, Ryan McDonald wrote:
>> Is there a change-log or bug-report anywhere that shows a 32/64
>> problem has been fixed with the file system?
> Note that as explained in the commit, the previous use of size_t means
> this problem only exists on systems where the maximum array size is
> 4B, which means those running 32-bit operating systems. The
> combination of someone running a RAID array, or modern hard drives,
> with more than 2TB of free space on a single filesystem, and still
> continuing to use antiquated 32-bit versions of Linux, is sufficiently
> rare that no one even noticed the problem until late last year.
> mythtv-users mailing list
> mythtv-users at mythtv.org
More information about the mythtv-users