From owner-freebsd-current@FreeBSD.ORG Mon Sep 1 17:38:27 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D4D6A16A4BF for ; Mon, 1 Sep 2003 17:38:27 -0700 (PDT) Received: from postal2.es.net (proxy.es.net [198.128.3.206]) by mx1.FreeBSD.org (Postfix) with ESMTP id 06DBB43FDD for ; Mon, 1 Sep 2003 17:38:27 -0700 (PDT) (envelope-from oberman@es.net) Received: from ptavv.es.net ([198.128.4.29]) by postal2.es.net (Postal Node 2) with ESMTP (SSL) id MUA74016 for ; Mon, 01 Sep 2003 17:38:25 -0700 Received: from ptavv (localhost [127.0.0.1]) by ptavv.es.net (Tachyon Server) with ESMTP id 198B25D04 for ; Mon, 1 Sep 2003 17:38:25 -0700 (PDT) To: current@freebsd.org Date: Mon, 01 Sep 2003 17:38:25 -0700 From: "Kevin Oberman" Message-Id: <20030902003825.198B25D04@ptavv.es.net> Subject: Syncer failure after fsck on all partitions X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 Sep 2003 00:38:28 -0000 This is really sort of two problems, but I'll focus on the primary concern here and maybe the more basic (but less significant) problem will get addressed at some point. (Or I'll PR it.) I have noticed that my stable system never seems to leave the filesystems clean after a crash on CURRENT. I get a message that background FSCK is starting in 60 seconds, but I see no indication that it is ever run. All partitions are UFS and have soft-update. After I notice that re-boots are reporting all ufs partitions as unclean, I shut down and boot standalone. I then do "fsck -y" on all partitions. Many simply mark the partition clean with no fixes while others do find the typical problems and fix them. Finally I do a reboot. No partition has ever been mounted except root which is read-only. Syncer reports 1 or more buffers remain and reports this until it gives up. After the reboot, all partitions mount cleanly and all seems normal. I really feel uncomfortable about this and can't understand why the syncer should have any buffers to handle when no partition has been mounted RW. Do I need to worry? -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman@es.net Phone: +1 510 486-8634