From owner-freebsd-fs@FreeBSD.ORG Mon Sep 23 12:21:12 2013 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id A328FB9C for ; Mon, 23 Sep 2013 12:21:12 +0000 (UTC) (envelope-from lev@FreeBSD.org) Received: from onlyone.friendlyhosting.spb.ru (onlyone.friendlyhosting.spb.ru [46.4.40.135]) by mx1.freebsd.org (Postfix) with ESMTP id 638302832 for ; Mon, 23 Sep 2013 12:21:12 +0000 (UTC) Received: from lion.home.serebryakov.spb.ru (unknown [IPv6:2001:470:923f:1:5b:71c5:b3bc:c366]) (Authenticated sender: lev@serebryakov.spb.ru) by onlyone.friendlyhosting.spb.ru (Postfix) with ESMTPSA id F30654AC58 for ; Mon, 23 Sep 2013 16:21:10 +0400 (MSK) Date: Mon, 23 Sep 2013 16:21:06 +0400 From: Lev Serebryakov Organization: FreeBSD Project X-Priority: 3 (Normal) Message-ID: <131058847.20130923162106@serebryakov.spb.ru> To: freebsd-fs Subject: Re: Strange UFS write problem & SU+J "unexpected inconsistences" on 9.1-STABLE r253105 after it on OTHER filesystems. In-Reply-To: <201309222224.r8MMO2o7025466@chez.mckusick.com> References: <724152380.20130921144811@serebryakov.spb.ru> <201309222224.r8MMO2o7025466@chez.mckusick.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: lev@FreeBSD.org List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Sep 2013 12:21:12 -0000 Hello, Kirk. You wrote 23 =D1=81=D0=B5=D0=BD=D1=82=D1=8F=D0=B1=D1=80=D1=8F 2013 =D0=B3.,= 2:24:02: [SEND THIS NOT ONLY DIRECTLY, BUT IN LIST TOO] >> I have dumped both FSes with "dumpfs" and "dumpfs -f" before manual che= ck >> and have block-dumped /tmp (as it is small enough). >>=20 >> You could find them at >>=20 >> http://lev.serebryakov.spb.ru/FreeBSD/suj-crash/ >>=20 >> --=20 >> // Black Lion AKA Lev Serebryakov KM> Have you run a manual (fsck -f) on the affected filesystems? If so, Hm. What do you mean by "Affected" here? I have 4 filesystems (/, /var, /tmp, /usr), 2 of them was affected before crash (/ and /var -- WRITE errors), but these were fixed by fsck automatically. And two of them (/tmp and /usr) were not affected before crash, but fsck refused to fix them automatically. I've run fsck -f /tmp and /usr, but not on / and /var, as I didn't see dmesg buffer when system was in single-user mode (I didn't know about WRITE errors yet) and I trust fsck, which says, that it repair them successfully with journal on boot after crash. And, yes, /tmp and /var were fixed with several questions like "invalid block count, fix or not". I didn't save output :( KM> was it able to clean them up? If not, please do so and save the output KM> of fsck (using script command is usually the easiest way to do this). It looks like I need to run manual fsck on / and /var (which are mentioned as WRITE ERROR in post-mortem dump), but I need to get physical access to this server, and it is hard for next two weeks :( --=20 // Black Lion AKA Lev Serebryakov