public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Stan Hoeppner <stan@hardwarefreak.com>
To: xfs@oss.sgi.com
Subject: Re: XFS recovery resumes...
Date: Mon, 26 Aug 2013 00:45:18 -0500	[thread overview]
Message-ID: <521AEB6E.4040101@hardwarefreak.com> (raw)
In-Reply-To: <17070299.5038.1377462440867.JavaMail.root@benjamin.baylink.com>

On 8/25/2013 3:27 PM, Jay Ashworth wrote:
...
> But yes, an upgrade was planned; I just wanted to upgrade the damn tuners
> first...  

I'm not really into the DIY DVR scene, but I'd think with over the air,
cable, and sat all being digital now that you should be able to get a
single board to do the job, multi-channel simultaneous recording and all.

> Thanks for the homework with NewEgg; 

No problem.  I have a rep to maintain after all.  Maybe you didn't
notice the right hand side of my email address. :)

> I don't mind buying stuff from 
> them as long as it isn't HDDs.  They can't pack worth a crap; it's
> Received Wisdom on the MythTV mailing list that you *never* buy 
> drives from them, if you want them to last more than a year.

Hadn't heard that before.  I've never had a problem with any of the
spinning drives I purchased from them.  I had a Corsair SSD die after ~4
months, no fault of Newegg.  Of the few grand I've spent with them since
2003, on parts for many new systems, repairs and upgrades, the only
other problem I've had was a $20 four channel fan controller w/one dead
channel outta the box.

> My endgame is to replace the entire backend with an HP DL180g6, which
> has 12 SAS/SATA tray slots on the front, and proper cooling.  But that,
> too, is down the road a bit.

Are you still talking about your sister's DVR here?  Build another PC
and spend some of the $$ you'd save on a 65" Panasonic Plasma.  Save the
rest for a rainy day.  The DL180G6 (discontinued BTW) with a handful of
drives will cost more than the PC and plasma TV combined.

-- 
Stan

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  reply	other threads:[~2013-08-26  5:45 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <29874428.3384.1376259762936.JavaMail.root@benjamin.baylink.com>
2013-08-11 22:36 ` XFS recovery resumes Jay Ashworth
2013-08-18 21:38   ` Jay Ashworth
2013-08-18 21:51     ` Joe Landman
2013-08-18 22:11       ` Jay Ashworth
2013-08-18 22:57         ` Joe Landman
2013-08-18 23:21           ` Jay Ashworth
2013-08-18 22:06     ` Stan Hoeppner
2013-08-19  3:55       ` Jay Ashworth
2013-08-19  6:47         ` Stan Hoeppner
2013-08-24 23:43           ` Jay Ashworth
2013-08-25  3:44             ` Stan Hoeppner
2013-08-25 15:29               ` Jay Ashworth
2013-08-25 17:45                 ` Stan Hoeppner
2013-08-25 20:27                   ` Jay Ashworth
2013-08-26  5:45                     ` Stan Hoeppner [this message]
2013-08-26 15:42                       ` Jay Ashworth
2013-08-24 23:48           ` Default mkfs parms for my DVR drive Jay Ashworth
2013-08-25  0:00             ` Joe Landman
2013-08-25  0:41               ` Jay Ashworth
2013-08-25  3:41                 ` Jay Ashworth
2013-08-22  9:16   ` XFS recovery resumes Stefan Ring
2013-08-27 23:59     ` Dave Chinner
2013-08-28  0:19       ` Jay Ashworth

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=521AEB6E.4040101@hardwarefreak.com \
    --to=stan@hardwarefreak.com \
    --cc=xfs@oss.sgi.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox