linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stan Hoeppner <stan@hardwarefreak.com>
To: Carabetta Giulio <g.carabetta@abi.it>
Cc: "'Mathias Burén'" <mathias.buren@gmail.com>,
	"'Linux RAID'" <linux-raid@vger.kernel.org>
Subject: Re: Offtopic: on case
Date: Fri, 19 Oct 2012 11:44:58 -0500	[thread overview]
Message-ID: <5081838A.1020006@hardwarefreak.com> (raw)
In-Reply-To: <4FDB990B62C2D849BA8EADBDD1C5928E1372362B18@CCRMBX.abiad.abi.lan>

On 10/19/2012 9:32 AM, Carabetta Giulio wrote:
> Sorry for the OT, but...
...
> You are right, I know that very well... 
> Also I'm looking for a compromise between temperature and noise: what do you think about this case?
> http://www.lian-li.com/v2/en/product/product06.php?pr_index=480&cl_index=1&sc_index=26&ss_index=67&g=f

It should keep six 3.5" SATA drives within normal operating temp range,
even though the hole punched cage frame is inefficient, along with the
lateral vs longitudinal orientation.  Going lateral saved them 2" on
case depth, which is critical to their aesthetics.  They could have
eliminated the side and bottom intake grilles and the top exhaust fan,
by rotating the PSU 180 degrees, reversing its fan, and adding a small
director vane on the back of the case.  This would decrease total noise
by 3-5 dB without impacting cooling capacity.

There are two reasons I've never been big on Lian Li cases:

1.  You pay a 3-5x premium for aesthetics and the name
2.  Airflow is an engineering afterthought--aesthetics comes first

Point 2 is interesting regarding this case.  I'm surprised to see a huge
blue glowing front intake grille on a Lian Li.  They've heretofore
always been about the Apple clean lines look, brushed aluminum with as
few interruptions as possible, which is they they had typically located
media bays and device connectors on the sides, not the front.

-- 
Stan


  reply	other threads:[~2012-10-19 16:44 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-16 22:57 RAID6 reshape, 2 disk failures Mathias Burén
2012-10-17  2:29 ` Stan Hoeppner
2012-10-17  3:06 ` Chris Murphy
2012-10-17  8:03   ` Mathias Burén
2012-10-17  9:09     ` Chris Murphy
     [not found]       ` <CADNH=7GaGCLdK2Rk_A6vPN+Th0z0QYT7mRV0KJH=CoAffuvb6w@mail.gmail.com>
2012-10-17 18:46         ` Chris Murphy
2012-10-17 19:03           ` Mathias Burén
2012-10-17 19:35             ` Chris Murphy
2012-10-18 11:56             ` Stan Hoeppner
2012-10-18 12:17               ` Mathias Burén
2012-10-18 17:11                 ` Mathias Burén
2012-10-18 19:54                   ` Chris Murphy
2012-10-18 20:17                     ` Mathias Burén
2012-10-18 20:58                       ` Stan Hoeppner
2012-10-19 14:32                         ` Offtopic: on case (was: R: RAID6 reshape, 2 disk failures) Carabetta Giulio
2012-10-19 16:44                           ` Stan Hoeppner [this message]
2012-10-18 21:28                       ` RAID6 reshape, 2 disk failures Chris Murphy
2012-10-21 22:31     ` NeilBrown

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=5081838A.1020006@hardwarefreak.com \
    --to=stan@hardwarefreak.com \
    --cc=g.carabetta@abi.it \
    --cc=linux-raid@vger.kernel.org \
    --cc=mathias.buren@gmail.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;
as well as URLs for NNTP newsgroup(s).