<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="HOEnZb"><div class="h5"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
1 - For 32-bit hosts, the fix first appears in 0.25? (or in some 0.24<br>
patchlevelX version)?<br>
</blockquote>
<br>
The fix actually exists in 0.24-fixes. You could choose to upgrade to that,<br>
though there's probably not a lot of reason to use 0.24-fixes over<br>
0.25-fixes--especially if anyone uses Live TV, you'll want 0.25-fixes. If you're<br>
upgrading, anyway, might as well go to current stable version.<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
2 - The way I understand the issue is that there is a problem evaluating the<br>
value that is returned by the "HowMuchSpaceIsLeft()" function. Assuming this<br>
is true, if I *had* to stay at 0.21, couldn't I just dd a bunch of 250MB<br>
/dev/zero files into the file system so that the disk always has <1T remaining<br>
at any one given time? Then, I'd slowly remove these dummy files until they<br>
are all replaced by actual media. Would this work?<br>
</blockquote>
<br>
Yes you could fill up some space to keep in the safe ranges. That would put you<br>
basically where you were before you lost the recordings.<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
Also.... If I'm sitting at 0.21 right now, which versions do I need to install<br>
BEFORE I upgrade to 0.25 to make sure all the schemas get updated?<br>
</blockquote>
<br>
You could upgrade from 0.21 to 0.24-fixes, then upgrade from 0.24-fixes to<br>
0.25-fixes.<br>
<br>
Basically, 0.25-fixes requires a database version from 0.22 or higher--it can't<br>
upgrade any older database versions. The main reason I'm recommending upgrading<br>
to 0.24-fixes (rather than an earlier version) is because it has some fixes for<br>
some random issues that can occur during database upgrade--especially with newer<br>
Qt and/or newer MySQL versions.<br>
</blockquote>
<br>
Ryan: Before you start the upgrade to 0.24, please be aware that there are some circumstances where the upgrade from schema 1215 to 1216 apparently does nothing for nearly 8 hours before it finally finishes the upgrade.<br>
</blockquote>
<br></div></div>
If you use current 0.24-fixes to do the upgrade, you shouldn't have that problem (and, assuming your database schema/data isn't corrupt--i.e. due to invalid encoding, i.e. if you had been running a MySQL server set up with UTF-8 as the default character set--shouldn't have other problems).<br>
<br></blockquote><div> </div><div>If you have the space, why not just partition your array? Depending on the filesystem you might even be able to shrink a partition without going through a backup/restore.<br><br>Of course, I too recommend upgrading... but if you have a lot of development into your custom frontend and whatnot, it may not be something you can do in the short term... so shrink for short term then perform your upgrade in a test environment until its ready for release.<br>
<br> <br></div></div><br>