From owner-freebsd-fs@FreeBSD.ORG Mon Feb 11 16:24:38 2013 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 87491468 for ; Mon, 11 Feb 2013 16:24:38 +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 22ED0CE1 for ; Mon, 11 Feb 2013 16:24:37 +0000 (UTC) Received: from [10.186.227.129] (238.sub-70-197-64.myvzw.com [70.197.64.238]) (authenticated bits=0) by chinatsu.takeda.tk (8.14.5/8.14.5) with ESMTP id r1BGEwFU041417 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO); Mon, 11 Feb 2013 08:14:59 -0800 (PST) (envelope-from takeda@takeda.tk) User-Agent: K-9 Mail for Android In-Reply-To: References: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Subject: Re: how much reliable is UFS2+SU/J From: Derek Kulinski Date: Mon, 11 Feb 2013 08:14:49 -0800 To: CeDeROM , freebsd-fs@freebsd.org Message-ID: <0affce66-f00b-4f16-9a57-4a3d71eedd99@email.android.com> X-Virus-Scanned: clamav-milter 0.97.6 at chinatsu.takeda.tk X-Virus-Status: Clean X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Feb 2013 16:24:38 -0000 CeDeROM wrote: >Hello :-) > >Some time ago I have switched to UFS2+SU/J. However on a crash I have >found some issues on a /home partition that SU/Journal seems to have >missed. This caused applications to misbehave or use default >configuration. Running "fsck" showed that filesystem is clean, but >running "fsck -fy" found some issues. This happended at least three >times in a short period of time, so I started to wonder how much >reliable if UFS2+SU/J? Should I expect some fixes in this area or >thing will stay like this forever for UFS2+SU/J? When I tried it first myself I found corrupted data even after clean shutdown. I turned off journaling. It was SSD, so fsck is very fast. Later I learned that SU/J is a bad idea on SSD. Not sure if that's why I got corrupted disk each time or because it writes to disk more. -- Sent from my Android phone with K-9 Mail. Please excuse my brevity.