From owner-freebsd-current@freebsd.org  Sun Oct 28 11:16:14 2018
Return-Path: <owner-freebsd-current@freebsd.org>
Delivered-To: freebsd-current@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id DD78C1086A92
 for <freebsd-current@mailman.ysv.freebsd.org>;
 Sun, 28 Oct 2018 11:16:14 +0000 (UTC) (envelope-from ml@netfence.it)
Received: from soth.netfence.it (net-2-44-121-52.cust.vodafonedsl.it
 [2.44.121.52])
 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
 (Client CN "mailserver.netfence.it",
 Issuer "Let's Encrypt Authority X3" (verified OK))
 by mx1.freebsd.org (Postfix) with ESMTPS id 4D5BB7D013
 for <freebsd-current@freebsd.org>; Sun, 28 Oct 2018 11:16:13 +0000 (UTC)
 (envelope-from ml@netfence.it)
Received: from alamar.ventu (alamar.local.netfence.it [10.1.2.18])
 (authenticated bits=0)
 by soth.netfence.it (8.15.2/8.15.2) with ESMTPSA id w9SBFv8A060852
 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO)
 for <freebsd-current@freebsd.org>; Sun, 28 Oct 2018 12:16:04 +0100 (CET)
 (envelope-from ml@netfence.it)
X-Authentication-Warning: soth.netfence.it: Host alamar.local.netfence.it
 [10.1.2.18] claimed to be alamar.ventu
Subject: Re: UFS panics
To: freebsd-current@freebsd.org
References: <CAC7XEcKqscy78Evb7Z66388fG8mvKTgJZfHpmct=nuFgU+pJ1A@mail.gmail.com>
 <20181027062357.GE75530@funkthat.com>
 <CAC7XEcKPV=kr0DEaci6Ln0YevYqcv8Oypd3b8jk-ZnT81gs0eA@mail.gmail.com>
From: Andrea Venturoli <ml@netfence.it>
Message-ID: <c26ac141-1607-a11f-6d01-17f605fdd790@netfence.it>
Date: Sun, 28 Oct 2018 12:15:57 +0100
User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:60.0) Gecko/20100101
 Thunderbird/60.2.1
MIME-Version: 1.0
In-Reply-To: <CAC7XEcKPV=kr0DEaci6Ln0YevYqcv8Oypd3b8jk-ZnT81gs0eA@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
 <freebsd-current.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current/>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 28 Oct 2018 11:16:15 -0000

On 10/27/18 5:34 PM, Leandro wrote:

> I just wanted to confirm if panics on UFS were expected if the file
> system had errors

This is no official answer, but yes, basing on my nearly 20 years of 
experience with UFS, I've come to expect them.

Several times after some boxes of mine crashed, they kept crashing every 
day or every few days. Only solution is to reboot in single user mode, 
fsck the filesystems (notice, not "fsck -p") and restart.
I guess softupdates let something bad slip through and won't fix it at 
reboot.

Just my 2c.

  bye
	av.