From owner-freebsd-fs@FreeBSD.ORG Fri Feb 17 19:14:10 2012 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B87361065672; Fri, 17 Feb 2012 19:14:10 +0000 (UTC) (envelope-from julian@freebsd.org) Received: from vps1.elischer.org (vps1.elischer.org [204.109.63.16]) by mx1.freebsd.org (Postfix) with ESMTP id 887058FC0C; Fri, 17 Feb 2012 19:14:10 +0000 (UTC) Received: from julian-mac.elischer.org (c-67-180-24-15.hsd1.ca.comcast.net [67.180.24.15]) (authenticated bits=0) by vps1.elischer.org (8.14.4/8.14.4) with ESMTP id q1HJE8SZ027481 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Fri, 17 Feb 2012 11:14:09 -0800 (PST) (envelope-from julian@freebsd.org) Message-ID: <4F3EA75C.6070407@freebsd.org> Date: Fri, 17 Feb 2012 11:15:40 -0800 From: Julian Elischer User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X 10.4; en-US; rv:1.9.2.26) Gecko/20120129 Thunderbird/3.1.18 MIME-Version: 1.0 To: Alexander Best References: <20120217141607.GA63659@freebsd.org> <4F3E9A14.3070605@freebsd.org> <20120217190921.GA26568@freebsd.org> In-Reply-To: <20120217190921.GA26568@freebsd.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-fs@freebsd.org Subject: Re: freebsd-swap on ssd X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 17 Feb 2012 19:14:10 -0000 On 2/17/12 11:09 AM, Alexander Best wrote: > On Fri Feb 17 12, Julian Elischer wrote: >> On 2/17/12 6:16 AM, Alexander Best wrote: >>> hi there, >>> >>> putting a freebsd-ufs partition on an ssd isn't recommended, since the ufs >>> structure (unlike zfs e.g.) requires certain data to be continuously >>> written to >>> a fixed location and thus will cause the ssd to quickly run out of >>> write-cycles >>> and die. >> nonsense. >> the SSD doesn't use the same flash for the same logical locatio each time! >> it maps it to different locations each time. > i simply repeated what kirk mckusick said in the SU+J introduction video. he > said for exactly this reason ufs should not be used on an ssd, since stuff like > inode entries live in a fixed location, whereas with zfs the ueberblock can > live in 128 locations. also in case of SU+J, where the journal only takes up a > very small part of the disk due to the fact that it's only tracking metadata > changes and isn't doing logging (like gjournal), there's also the chance to run > out of write-cycles. I think he meant ON A RAW FLASH DEVICE SSD's have all that taken care of transparently. There are special file systems for raw flash devices that take all that into account, and ffs is not one of them.