From owner-freebsd-stable@FreeBSD.ORG Sat Nov 3 22:55:06 2012 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 1300ACE1 for ; Sat, 3 Nov 2012 22:55:06 +0000 (UTC) (envelope-from freebsd@damnhippie.dyndns.org) Received: from duck.symmetricom.us (duck.symmetricom.us [206.168.13.214]) by mx1.freebsd.org (Postfix) with ESMTP id 878448FC15 for ; Sat, 3 Nov 2012 22:54:53 +0000 (UTC) Received: from damnhippie.dyndns.org (daffy.symmetricom.us [206.168.13.218]) by duck.symmetricom.us (8.14.5/8.14.5) with ESMTP id qA3MsqvO044529 for ; Sat, 3 Nov 2012 16:54:52 -0600 (MDT) (envelope-from freebsd@damnhippie.dyndns.org) Received: from [172.22.42.240] (revolution.hippie.lan [172.22.42.240]) by damnhippie.dyndns.org (8.14.3/8.14.3) with ESMTP id qA3MsTKU010353; Sat, 3 Nov 2012 16:54:30 -0600 (MDT) (envelope-from freebsd@damnhippie.dyndns.org) Subject: Re: Why is SU+J undesirable on SSDs? From: Ian Lepore To: Adam Vande More In-Reply-To: References: <201211032130.PAA04484@lariat.net> Content-Type: text/plain; charset="us-ascii" Date: Sat, 03 Nov 2012 16:54:29 -0600 Message-ID: <1351983269.1120.137.camel@revolution.hippie.lan> Mime-Version: 1.0 X-Mailer: Evolution 2.32.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit Cc: Brett Glass , stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 03 Nov 2012 22:55:06 -0000 On Sat, 2012-11-03 at 17:06 -0500, Adam Vande More wrote: > On Sat, Nov 3, 2012 at 4:30 PM, Brett Glass wrote: > > > Have been following the thread related to SU+J, and am wondering: why is it > > considered to be undesirable on SSDs (assuming that they have good wear > > leveling)? > > > Superstition > > Yeah, that's what it must be. Or... it could be well-informed choice. Journaling increases the number of writes. That puts wear on any disk, mechanical or SSD, and it takes time. What it buys you is better performance if you get into a crash recovery situation. It's perfectly reasonable for someone to make the decision that their SSD can finish an fsck so fast that there's no point in paying any penalty for the extra writes for journaling. I have a 256G SSD here with about 200G of data on it, and fsck without journaling takes about 3 minutes. I can live with that. With more data or a slower drive I might make a different choice. -- Ian