From owner-freebsd-stable@FreeBSD.ORG Sun Apr 13 12:03:33 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 4F9F1E9C; Sun, 13 Apr 2014 12:03:33 +0000 (UTC) Received: from mail-lb0-x232.google.com (mail-lb0-x232.google.com [IPv6:2a00:1450:4010:c04::232]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 16A68177F; Sun, 13 Apr 2014 12:03:31 +0000 (UTC) Received: by mail-lb0-f178.google.com with SMTP id s7so4965495lbd.9 for ; Sun, 13 Apr 2014 05:03:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=APZXUXJOOdiOORLHYcHE/aJlsdC35pYZlUEdeRkD/io=; b=mId54X3F1p3dapNnvHKlwnGeF3G4WOr2xX+V983Q7RV6L4FDYu9BNohNdacYsoyFd+ 8fRvv9cae6O0Yxbf9KG0FA76hxfWdT+wcHVGCrafu6SVG0JhDRCPtGEBHWo/1H2vBR5b awsLXaCTAODnF8xyw7sIXk+pTni0Myp4CUgjfSR41DklDgEEcVNG+9CUPVmAA6Z6g6ja h0ar95zzVYHkTReXyAcDxmzORpdP4JASu4YKrnf94n5wKyVXOrbxEBf2DNdRlJColJIV C8E0p7dIJJXCbkFsRyVjIPj+FQ+Klp0HslNot8NC5IbwJrK85OLtV9WYRAf6B/Cvy7q0 EFIw== X-Received: by 10.112.126.7 with SMTP id mu7mr23628864lbb.17.1397390609541; Sun, 13 Apr 2014 05:03:29 -0700 (PDT) Received: from [10.0.1.9] (ip-95-220-138-28.bb.netbynet.ru. [95.220.138.28]) by mx.google.com with ESMTPSA id d4sm11248713lbr.27.2014.04.13.05.03.27 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 13 Apr 2014 05:03:28 -0700 (PDT) Subject: Re: 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!) Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\)) Content-Type: text/plain; charset=utf-8 From: Dmitry Sivachenko X-Priority: 3 (Normal) In-Reply-To: <482103242.20140413141010@serebryakov.spb.ru> Date: Sun, 13 Apr 2014 16:03:26 +0400 Content-Transfer-Encoding: quoted-printable Message-Id: <8A3243EF-90D0-428A-99C1-8360DB402B86@gmail.com> References: <981154629.20140412170953@serebryakov.spb.ru> <482103242.20140413141010@serebryakov.spb.ru> To: lev@FreeBSD.org X-Mailer: Apple Mail (2.1874) Cc: freebsd-fs@FreeBSD.org, pfg@FreeBSD.org, freebsd-stable@freebsd.org, mckusick@FreeBSD.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list 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 12:03:33 -0000 Turn off journaling, it has many issues reported. I run hundreds of servers at work with UFS2+SU (w/o J), and never had a = single problem. On 13 =D0=B0=D0=BF=D1=80. 2014 =D0=B3., at 14:10, Lev Serebryakov = wrote: > Hello, Freebsd-fs. > You wrote 12 =D0=B0=D0=BF=D1=80=D0=B5=D0=BB=D1=8F 2014 =D0=B3., = 17:09:53: >=20 > 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! >=20 > WHY?! How could I trust to UFS2 now?! >=20 > Both filesystems have same scenario: >=20 > /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. >=20 > /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. >=20 > 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. >=20 > EVERY non-clean reboot of server leads to "RUN fsck MANUALLY". >=20 > --=20 > // Black Lion AKA Lev Serebryakov >=20 > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to = "freebsd-stable-unsubscribe@freebsd.org"