From owner-freebsd-fs@FreeBSD.ORG Wed Jun 6 07:49:37 2012 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id F311C1065689 for ; Wed, 6 Jun 2012 07:49:37 +0000 (UTC) (envelope-from jjuanino@gmail.com) Received: from mail-bk0-f54.google.com (mail-bk0-f54.google.com [209.85.214.54]) by mx1.freebsd.org (Postfix) with ESMTP id 790B18FC12 for ; Wed, 6 Jun 2012 07:49:37 +0000 (UTC) Received: by bkvi18 with SMTP id i18so6873382bkv.13 for ; Wed, 06 Jun 2012 00:49:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=fo4EZjLZhliCddXsCNL+OOr7Tcp+4QnJ2qyiJBN8rVk=; b=vRXGNLBpiCzg0qLb+f9M/Q/Hz8bgQfcDqODcPV8Rr4l7rcY9RJTOau7Ab0DqTO+lNW 0dTb6A5OCbI4JFzlhJR9sG92xL8PUg+Fr0b6eT7qCJlMP7iRAChHoC0ogu/YdVau8zBK Azpeoe6r7eBz/kaYAO8JhWBKnleZgw6nZR9+udgQvAlfzJZJlsAGiNr/7X/a0oNL6k+T x/CcPRDUoyzX8zpXqJwcF/MnnzGCs8nSQZqj3kKfKEroF/sUHVWYPAPIFHoDA2sQX6Mf 9Szjs9dEQH67oLJC1M5OFWNOFlCuN7TiwrPFGKyJ4nd1wosBSzQA4xemsyCH2uWYQQ1q GL9Q== MIME-Version: 1.0 Received: by 10.204.154.138 with SMTP id o10mr11095068bkw.34.1338968976450; Wed, 06 Jun 2012 00:49:36 -0700 (PDT) Received: by 10.205.114.140 with HTTP; Wed, 6 Jun 2012 00:49:36 -0700 (PDT) In-Reply-To: <20120606082412.bd21757e.lists@yamagi.org> References: <20120605203718.GA2630@banach> <20120606082412.bd21757e.lists@yamagi.org> Date: Wed, 6 Jun 2012 09:49:36 +0200 Message-ID: From: =?ISO-8859-1?Q?Jos=E9_Garc=EDa_Juanino?= To: freebsd-fs@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Subject: Re: "panic: snapblkfree: inconsistent block type" on FreeBSD 9.0 RELEASE X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 Jun 2012 07:49:38 -0000 On 6 June 2012 08:24, Yamagi Burmeister wrote: > On Tue, 5 Jun 2012 22:37:21 +0200 Jose Garcia Juanino wrote: > >> I am almost sure I have not hardware failures. Indeed, after that panic, >> I definitively removed all the remaining snapshots, and did a new fsck on >> the filesystems. The system now goes smoothly, and the computer does not >> panic anymore. > > If you're using SU+J this is a known problem. In 9.0-RELEASE creating > and removing snapshots on filesystems with SU+J has a high chance to > lead to panics, filesystem corruption and several more not so nice > things. While there were some commits in 9-STABLE in that area, > snapshots are still not working with SU+J. They are disabled and > an error messages is printed when you try to create one. Thanks for your reply. No, I have not journaling activated, are filesystems with soft updates, but no journal. I am watching the syslog, and after a crash (4 weeks ago) I see that a filesystem was not fully cleaned at startup: : UNEXPECTED SOFT UPDATE INCONSISTENCY; RUN fsck MANUALLY. The system stopped, and a single user shell opened. But the system administrator at this moment simply ignored that issue, and hit "exit" in the shell. I believe that error was the start of my headaches: never an unclean filesystem must be mounted. Regards