From owner-freebsd-fs@FreeBSD.ORG Fri Feb 15 10:58:36 2008 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id ED55416A417 for ; Fri, 15 Feb 2008 10:58:36 +0000 (UTC) (envelope-from jhs@berklix.org) Received: from flat.berklix.org (flat.berklix.org [83.236.223.115]) by mx1.freebsd.org (Postfix) with ESMTP id 48DD513C44B for ; Fri, 15 Feb 2008 10:58:35 +0000 (UTC) (envelope-from jhs@berklix.org) Received: from js.berklix.net (p549A491F.dip.t-dialin.net [84.154.73.31]) (authenticated bits=0) by flat.berklix.org (8.13.8/8.13.8) with ESMTP id m1FAwYD0084318; Fri, 15 Feb 2008 11:58:34 +0100 (CET) (envelope-from jhs@berklix.org) Received: from fire.js.berklix.net (fire.js.berklix.net [192.168.91.41]) by js.berklix.net (8.13.8/8.13.8) with ESMTP id m1FB0i2a086538; Fri, 15 Feb 2008 12:00:44 +0100 (CET) (envelope-from jhs@berklix.org) Received: from fire.js.berklix.net (localhost [127.0.0.1]) by fire.js.berklix.net (8.13.8/8.13.8) with ESMTP id m1FB0TvO054046; Fri, 15 Feb 2008 12:00:34 +0100 (CET) (envelope-from jhs@fire.js.berklix.net) Message-Id: <200802151100.m1FB0TvO054046@fire.js.berklix.net> To: Oliver Fromme In-reply-to: <200802150923.m1F9NHNI010776@lurza.secnetix.de> References: <200802150923.m1F9NHNI010776@lurza.secnetix.de> Comments: In-reply-to Oliver Fromme message dated "Fri, 15 Feb 2008 10:23:17 +0100." Date: Fri, 15 Feb 2008 12:00:29 +0100 From: "Julian H. Stacey" Cc: freebsd-fs@freebsd.org Subject: Re: UFS2 corruption (RELENG_7, amd64) 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: Fri, 15 Feb 2008 10:58:37 -0000 Oliver Fromme wrote: > Chris Dillon wrote: > > Oliver Fromme wrote: > > ...snip... > > > > > # fsck -y /dev/da45 > > > ** /dev/da45 > > > ** Last Mounted on [...] > > > ** Phase 1 - Check Blocks and Sizes > > > ** Phase 2 - Check Pathnames > > > UNALLOCATED I=2107428 OWNER=2283830233 MODE=0 > > > SIZE=0 MTIME=Feb 5 08:43 2008 > > > NAME=/D.0131ae2e/B.0786 > > > > > > UNEXPECTED SOFT UPDATE INCONSISTENCY > > > > > > REMOVE? yes > > > > I've been seeing "UNEXPECTED SOFT UPDATE INCONSISTENCY" fsck errors > > show up in some of my filesytem snapshots on a RELENG_6 AMD64 box for > > years (actually since RELENG_5), which will eventually lead to "panic: > > snapblkfree: inconsistent block type" if those snapshots are mounted > > and used. > > We do not use snapshots, and we don't see such panics. > So this is probably unrelated. > > Best regards > Oliver I've never enabled snapshots either, but was suprised to find one recently! Though I recall it had been around a long while, it was also certainly bigger than the physical disk it was on, (presumably a sparse file). I just deleted it, & guessed some flag or config file presence/ absence/ corruption etc had somehow triggered it. (No one else would have enabled snapshots on it). As it had hung, crashed or been troublesome lately, I did a foreground fsck rather background, & I think a 2nd fsck -y straight after 1st, which I think fixed some more, (sometimes does). Maybe schedule an outage, take off line & single user { foreground fsck, & repeat till you get a clean run where it fixes nothing || backup & newfs }. Good luck! Julian -- Julian Stacey: BSDUnixLinux C Prog Admin SysEng Consult Munich www.berklix.com