From owner-freebsd-stable@FreeBSD.ORG Sun Apr 13 10:10:20 2014 Return-Path: Delivered-To: freebsd-stable@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 ESMTPS id A4EA28E8; Sun, 13 Apr 2014 10:10:20 +0000 (UTC) Received: from onlyone.friendlyhosting.spb.ru (onlyone.friendlyhosting.spb.ru [IPv6:2a01:4f8:131:60a2::2]) by mx1.freebsd.org (Postfix) with ESMTP id 6689E1CBE; Sun, 13 Apr 2014 10:10:20 +0000 (UTC) Received: from lion.home.serebryakov.spb.ru (unknown [IPv6:2001:470:923f:1:5803:a51e:6ee3:b101]) (Authenticated sender: lev@serebryakov.spb.ru) by onlyone.friendlyhosting.spb.ru (Postfix) with ESMTPSA id 907124AC32; Sun, 13 Apr 2014 14:10:11 +0400 (MSK) Date: Sun, 13 Apr 2014 14:10:10 +0400 From: Lev Serebryakov Organization: FreeBSD X-Priority: 3 (Normal) Message-ID: <482103242.20140413141010@serebryakov.spb.ru> To: freebsd-fs@FreeBSD.org, freebsd-stable@freebsd.org Subject: UFS2 SU+J could not recover after power-off sgain (was: One process which would not die force me to power-cycle server and ALL UFS SUJ FSes are completely broken after that AGAIN!) In-Reply-To: <981154629.20140412170953@serebryakov.spb.ru> References: <981154629.20140412170953@serebryakov.spb.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Cc: pfg@FreeBSD.org, mckusick@FreeBSD.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list Reply-To: lev@FreeBSD.org List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Apr 2014 10:10:20 -0000 Hello, Freebsd-fs. You wrote 12 =D0=B0=D0=BF=D1=80=D0=B5=D0=BB=D1=8F 2014 =D0=B3., 17:09:53: LS> All UFS2 filesystems can not be recovered with using of automated fsck= , due LS> to journal/softupdate inconsistencies. I need to run "fsck -f" TWICE for LS> each of them (as first run ask to re-run fsck). "shutdown -h" reboots system, UPS switch power off after that (with delay), 2 out of 5 FSes could not be checked with journal automatically. Manual full "fsck" run didn't find any serious problems, only one or two unlinked files (recovered to lost+found) free block bitmaps! WHY?! How could I trust to UFS2 now?! Both filesystems have same scenario: /dev/ufs/tmp: Journal file sequence mismatch 233263 !=3D 231707 /dev/ufs/tmp: UNEXPECTED SU+J INCONSISTENCY /dev/ufs/tmp: INTERNAL ERROR: GOT TO reply() /dev/ufs/tmp: UNEXPECTED SOFT UPDATE INCONSISTENCY. RUN fsck MANUALLY. /dev/ufs/usr: Journal file sequence mismatch 287936 !=3D 282572 /dev/ufs/usr: UNEXPECTED SU+J INCONSISTENCY /dev/ufs/usr: INTERNAL ERROR: GOT TO reply() /dev/ufs/usr: UNEXPECTED SOFT UPDATE INCONSISTENCY. RUN fsck MANUALLY. Again: these FSes were checked with full fsck two days ago. They reside at SATA HDD without any non-standard or complex geom modules (only geonm_part), and HDD is attahed to chipset SATA port, there is no any RAID controllers or things like that. EVERY non-clean reboot of server leads to "RUN fsck MANUALLY". --=20 // Black Lion AKA Lev Serebryakov