From owner-freebsd-stable@FreeBSD.ORG  Sun Nov  4 08:05:42 2012
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
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 578B3114
 for <stable@freebsd.org>; Sun,  4 Nov 2012 08:05:42 +0000 (UTC)
 (envelope-from takeda@takeda.tk)
Received: from chinatsu.takeda.tk (mail.takeda.tk [74.0.89.210])
 by mx1.freebsd.org (Postfix) with ESMTP id EDD588FC0C
 for <stable@freebsd.org>; Sun,  4 Nov 2012 08:05:41 +0000 (UTC)
Received: from [10.188.2.241] (5.sub-70-197-141.myvzw.com [70.197.141.5])
 (authenticated bits=0)
 by chinatsu.takeda.tk (8.14.5/8.14.5) with ESMTP id qA4816Yi044789
 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO);
 Sun, 4 Nov 2012 01:01:07 -0700 (PDT) (envelope-from takeda@takeda.tk)
User-Agent: K-9 Mail for Android
In-Reply-To: <201211032130.PAA04484@lariat.net>
References: <201211032130.PAA04484@lariat.net>
MIME-Version: 1.0
Subject: Re: Why is SU+J undesirable on SSDs?
From: Derek Kulinski <takeda@takeda.tk>
Date: Sun, 04 Nov 2012 01:00:59 -0700
To: Brett Glass <brett@lariat.net>, stable@freebsd.org
Message-ID: <6a2843fd-1574-440d-a3c5-83aeb106b854@email.android.com>
X-Virus-Scanned: clamav-milter 0.97.6 at chinatsu.takeda.tk
X-Virus-Status: Clean
X-Bogosity: No, tests=bogofilter
Content-Type: text/plain;
 charset=UTF-8
Content-Transfer-Encoding: 8bit
X-Content-Filtered-By: Mailman/MimeDel 2.1.14
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/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: Sun, 04 Nov 2012 08:05:42 -0000

I personally let it be enabled during installation. I noticed that I was getting errors on fsck even after clean shutdown. After noticing it, I disabled it and the problems go away. Also, fsck works really fast so I don't see much advantage with SU+J.
-- 
Sent from my phone. Please excuse my brevity.

Brett Glass <brett@lariat.net> 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)? I have been enabling it on systems with SSDs, hoping that
>between
>the lack of rotating media and the journaling I would have very robust
>systems.
>
>--Brett Glass
>_______________________________________________
>freebsd-stable@freebsd.org mailing list
>http://lists.freebsd.org/mailman/listinfo/freebsd-stable
>To unsubscribe, send any mail to
>"freebsd-stable-unsubscribe@freebsd.org"