From owner-freebsd-questions@freebsd.org Sat Jul 25 16:30:41 2015 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 694739AAAF1 for ; Sat, 25 Jul 2015 16:30:41 +0000 (UTC) (envelope-from tomek.cedro@gmail.com) Received: from mail-la0-x229.google.com (mail-la0-x229.google.com [IPv6:2a00:1450:4010:c03::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id E2B531DF2 for ; Sat, 25 Jul 2015 16:30:40 +0000 (UTC) (envelope-from tomek.cedro@gmail.com) Received: by lafd3 with SMTP id d3so18600233laf.1 for ; Sat, 25 Jul 2015 09:30:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=c1qr9TIWIAAOgQv7X9h9KMUk1RTeFkLAtrhAd5V1xUw=; b=ErsO7vKLXQwqp9Xv67dK1rMBDHuMqt21hNEbFgFcyfBWuFJMi8nvk7qZY9rgK7lNV6 +TJCsyTc4bUSxjdNcPmlOnvD/o8V60Y/6UNXIpKlrYD50Cb8sG/yS6z0F9sP4OfDW6/W 5FH8+FQzlIPSa+9u+spo6KlsY2ryL3gpRqTnaQaiyeXR44czJrM0vK2T1tJ7IS1bxG0f cWDgvY8nPKP1Fv9ABiq/1u1ImpHG8GyPOUQ8gv4PAjM0M0Vh0cFKM67O+3HGsaPANf+k 0+TNWnjT1sA138E+fdAa8yiuXr73kjQ8yQWGs+9K0Xyo7skwxoFvD2K5Hb9pPIJBFjwo vDVg== MIME-Version: 1.0 X-Received: by 10.112.161.197 with SMTP id xu5mr18987842lbb.69.1437841838096; Sat, 25 Jul 2015 09:30:38 -0700 (PDT) Sender: tomek.cedro@gmail.com Received: by 10.152.45.5 with HTTP; Sat, 25 Jul 2015 09:30:38 -0700 (PDT) Received: by 10.152.45.5 with HTTP; Sat, 25 Jul 2015 09:30:38 -0700 (PDT) In-Reply-To: <0MRCCJ-1ZUCcr1rAt-00UeQk@mail.gmx.com> References: <0MRCCJ-1ZUCcr1rAt-00UeQk@mail.gmx.com> Date: Sat, 25 Jul 2015 18:30:38 +0200 X-Google-Sender-Auth: CGcmB8QsGVGF2QzcLHmWNDmsmD0 Message-ID: Subject: Re: Endless Data Loss From: CeDeROM To: CK Cc: FreeBSD Questions Mailing List Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 25 Jul 2015 16:30:41 -0000 UFS2 SU+J has failed me several times as well. I also ocassionaly experienced root filesystem corruption that prevented valid boot. Even on a fresh install and new hardware I consider UFS2 SU+J unreliable.. I am not sure why this got into production :-( Performing forced fsck on a SU+J filesystem that was considered clean in J revealed inconsistency on fsck. Try to disable SU+J, maybe only J as mentioned in other reply. I will try that too. Try ZFS for good consistency. Or wait/force full fsck before system is up. Also, take a look at hard drive details - manufacturer and series (i.e. WD RED, BLACK, GREEN) - they can have totally different firmware with badblock correction that may cause troubles as well. Best regards :-) Tomek -- CeDeROM, SQ7MHZ, http://www.tomek.cedro.info