[mythtv-users] Recent "pixelation" or "glitches" in recordings (HDHR related?)

[Joseph Fry]

> > I like the idea of an SSD drive for the recording drive. What is the
> > actual lifetime of these suckers anyway, if you made sure the only
> > thing being sent to them was recordings?
> >
> >
> >
> > On Tue, Apr 23, 2013 at 8:05 PM, Joseph Fry <joe at thefrys.com> wrote:
> >       If that's not possible, then I would consider getting a SSD to act
> > as your recording drive and create a user job (or cron) that runs
> > after a few days that moves the recording to the raid array.  Getting
> > an SSD for my recording drive is my next investment... it would allow
> > my magnetic drives to be spun down most of the time to save on
> > power/heat/noise.
>
> I believe you both mean "system drive".  A SSD as a recording drive would
> truly be a waste.  Expensive/GB, meaning those HDHR shows will cost a LOT
> more to store.
>

No, I meant recording drive.  But I clearly meant recording and not
storage.

I would estimate that about 80% of my recordings (to include live tv) are
watched and deleted within 1 week.  Using a 1 week delayed userjob or
cronjob that moves files older than 1 week to magnetic storage would allow
me to use a smallish SSD as temporary storage of recordings/livetv.  A
single SSD should be able to sustain enough throughput for all of my
tuners, commflagging, and watching several shows.


>
> If you're looking for opportunities to spin-down your magnetic drives,
> you'll use THOSE as recording drives.


Using a SSD as described above would allow the drives to remain spun down
except when transferring recordings from the SSD, or watching one that was
already transferred.  Because the transfers would occur faster than
recording directly and because only a fraction of all recordings would
actually make it to the magnetic drives, they would remain spun down far
more.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.mythtv.org/pipermail/mythtv-users/attachments/20130424/348fcbb3/attachment.html>