From owner-freebsd-stable@FreeBSD.ORG  Thu Jun  7 09:09:53 2012
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52])
	by hub.freebsd.org (Postfix) with ESMTP id C2884106564A
	for <freebsd-stable@freebsd.org>; Thu,  7 Jun 2012 09:09:53 +0000 (UTC)
	(envelope-from daniel@digsys.bg)
Received: from smtp-sofia.digsys.bg (smtp-sofia.digsys.bg [193.68.3.230])
	by mx1.freebsd.org (Postfix) with ESMTP id 477958FC08
	for <freebsd-stable@freebsd.org>; Thu,  7 Jun 2012 09:09:53 +0000 (UTC)
Received: from dcave.digsys.bg (dcave.digsys.bg [192.92.129.5])
	(authenticated bits=0)
	by smtp-sofia.digsys.bg (8.14.5/8.14.5) with ESMTP id q5799h0L064579
	(version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO)
	for <freebsd-stable@freebsd.org>; Thu, 7 Jun 2012 12:09:45 +0300 (EEST)
	(envelope-from daniel@digsys.bg)
Message-ID: <4FD06FD7.2000708@digsys.bg>
Date: Thu, 07 Jun 2012 12:09:43 +0300
From: Daniel Kalchev <daniel@digsys.bg>
User-Agent: Mozilla/5.0 (X11; FreeBSD amd64;
	rv:10.0.4) Gecko/20120528 Thunderbird/10.0.4
MIME-Version: 1.0
To: freebsd-stable@freebsd.org
References: <CAMYW4Zi4y16EL1=+sfz1XATc9ZnQpocUD_Xf9Jg=LR=c1AgaKA@mail.gmail.com>
	<3CEF3B39-BE1E-4FC4-81F3-D26049C83313@netflix.com>
In-Reply-To: <3CEF3B39-BE1E-4FC4-81F3-D26049C83313@netflix.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: Netflix's New Peering Appliance Uses FreeBSD
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, 
	<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
	<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Jun 2012 09:09:53 -0000



On 06.06.12 03:16, Scott Long wrote:

[...]
> Each disk has its own UFS+J filesystem, except for
> the SSDs that are mirrored together with gmirror.  The SSDs hold the OS image
> and cache some of the busiest content.  The other disks hold nothing but the
> audio and video files for our content streams.

Could you please explain the rationale of using UFS+J for this large 
storage. Your published documentation states that you have reasonable 
redundancy in case of multiple disk failure and I wonder how you handle 
this with "plain" UFS. Things like avoiding hangs and panics when an 
disk is going to die.

Daniel