<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Wed, Apr 24, 2013 at 12:25 PM, Joseph Fry <span dir="ltr"><<a href="mailto:joe@thefrys.com" target="_blank">joe@thefrys.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div dir="ltr"><br><div class="gmail_extra"><div class="gmail_quote"><div><div class="h5"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">
<div class="gmail_extra"><div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div><div><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><div><div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div><div>
>> > I like the idea of an SSD drive for the recording drive. What is the<br>
>> > actual lifetime of these suckers anyway, if you made sure the only<br>
>> > thing being sent to them was recordings?<br>
>> ><br>
>> ><br>
>> ><br>
>> > On Tue, Apr 23, 2013 at 8:05 PM, Joseph Fry <<a href="mailto:joe@thefrys.com" target="_blank">joe@thefrys.com</a>> wrote:<br>
>> > If that's not possible, then I would consider getting a SSD to act<br>
>> > as your recording drive and create a user job (or cron) that runs<br>
>> > after a few days that moves the recording to the raid array. Getting<br>
>> > an SSD for my recording drive is my next investment... it would allow<br>
>> > my magnetic drives to be spun down most of the time to save on<br>
>> > power/heat/noise.<br>
>><br>
>> I believe you both mean "system drive". A SSD as a recording drive would<br>
>> truly be a waste. Expensive/GB, meaning those HDHR shows will cost a LOT<br>
>> more to store.<br>
>><br>
><br>
>No, I meant recording drive. But I clearly meant recording and not<br>
>storage.<br>
><br>
>I would estimate that about 80% of my recordings (to include live tv) are<br>
>watched and deleted within 1 week. Using a 1 week delayed userjob or<br>
>cronjob that moves files older than 1 week to magnetic storage would allow<br>
>me to use a smallish SSD as temporary storage of recordings/livetv. A<br>
>single SSD should be able to sustain enough throughput for all of my<br>
>tuners, commflagging, and watching several shows.<br>
><br>
><br>
>><br>
>> If you're looking for opportunities to spin-down your magnetic drives,<br>
>> you'll use THOSE as recording drives.<br>
><br>
><br>
>Using a SSD as described above would allow the drives to remain spun down<br>
>except when transferring recordings from the SSD, or watching one that was<br>
>already transferred. Because the transfers would occur faster than<br>
>recording directly and because only a fraction of all recordings would<br>
>actually make it to the magnetic drives, they would remain spun down far<br>
>more.<br>
<br>
</div></div>Unfortunately, the storage drives in this scheme would be started more<br>
often than you would like. When mythfrontend displays a list of<br>
programs, it makes a check for the presence of the recording's file<br>
and displays an X icon for those it can not find. That checking<br>
process would start all the storage drives every time it happened as<br>
all partitions in all storage groups are scanned to find files. There<br>
is no way the current operation of MythTV would allow just the drive<br>
needed to play a specific recording to be started, as the actual<br>
locations for the files are not stored in the database.</blockquote><div><br></div></div></div><div>Interesting, I had never heard that before. Sounds like it would be worth lobbying to have changed, perhaps have it confirm they are available on some sort of schedule rather then every time the user opens the watch recordings screen.</div>
</div></div></div>
<br></div></div><div>_______________________________________________<br>
mythtv-users mailing list<br>
<a href="mailto:mythtv-users@mythtv.org" target="_blank">mythtv-users@mythtv.org</a><br>
<a href="http://www.mythtv.org/mailman/listinfo/mythtv-users" target="_blank">http://www.mythtv.org/mailman/listinfo/mythtv-users</a><br>
<br></div></blockquote></div><br><br></div><div class="gmail_extra">Queue bug report "Mythfrontend said a recording was there, but when I went to play it I received the error 'recording not available'"<br>
</div>
<div class="gmail_extra"><br></div></div></blockquote><div><br></div></div></div><div>I think it would be reasonable for it to do the normal scan upon opening watch recordings, but only if the last scan was more than X hours ago OR if the last scan revealed missing files.</div>
<div><br></div><div>I don't treat the red X icon as authoritative anyway... anything can happen between the time that the scan runs and I try to play a video; hell I could leave the watch recordings screen open and go and take my storage drives off line and it won't show the red x but I will get an error when I try to play the file.</div>
<div><br></div><div>The red x is simply an indicator that on the last check the file was missing... all I'm saying is that we shouldn't do so many checks.</div><div><br></div><div><br></div>
</div></div></div>
<br>_______________________________________________<br>
mythtv-users mailing list<br>
<a href="mailto:mythtv-users@mythtv.org">mythtv-users@mythtv.org</a><br>
<a href="http://www.mythtv.org/mailman/listinfo/mythtv-users" target="_blank">http://www.mythtv.org/mailman/listinfo/mythtv-users</a><br>
<br></blockquote></div><br><br></div><div class="gmail_extra">Why should we do ANY check? I think it's reasonable to expect that <br><br>A) Users shouldn't be touching recording files outside of MythTV<br><br>B) Recording drives are relatively static in their location.<br>
</div><div class="gmail_extra"><br clear="all"><div>Thanks,<br><br>Thomas Mashos</div>
<br></div></div>