From owner-freebsd-stable@FreeBSD.ORG Mon Jan 12 12:57:17 2009 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1837E1065758 for ; Mon, 12 Jan 2009 12:57:17 +0000 (UTC) (envelope-from avg@icyb.net.ua) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 2AC2C8FC17 for ; Mon, 12 Jan 2009 12:57:15 +0000 (UTC) (envelope-from avg@icyb.net.ua) Received: from odyssey.starpoint.kiev.ua (alpha-e.starpoint.kiev.ua [212.40.38.101]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id OAA11785 for ; Mon, 12 Jan 2009 14:57:12 +0200 (EET) (envelope-from avg@icyb.net.ua) Message-ID: <496B3E28.3070902@icyb.net.ua> Date: Mon, 12 Jan 2009 14:57:12 +0200 From: Andriy Gapon User-Agent: Thunderbird 2.0.0.18 (X11/20081124) MIME-Version: 1.0 To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Subject: fsck_y_enable: suboptimal/odd? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Jan 2009 12:57:18 -0000 System: stable/7 some time before New Year (sorry if this issue has already been acted upon). I have a system with perhaps sufficiently rare configuration: it has fsck_y_enable="YES" and it has multiple filesystems mounted (UFS2), some RW, some RO. Today I had a chance to see fsck_y_enable in action. After a hard-lock followed by a reset normal fsck process started, several filesystems had "expected" inconsistencies and were successfully repaired, and then one filesystem had an unexpected inconsistency (partially truncated inode it was). After that normal fsck process was aborted and "fsck_y" process started. To much of my surprise it started all over - the filesystems that had been just successfully checked were being checked again. Even more - filesystems that had been mounted RO before the reset were also being checked. To me it seems like fsck_y passes suboptimal flags to fsck, it doesn't have to examine each and every filesystem in fstab. -- Andriy Gapon