From owner-freebsd-current@FreeBSD.ORG  Tue Jan 20 18:50:09 2004
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
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 3D83516A4CE
	for <freebsd-current@freebsd.org>;
	Tue, 20 Jan 2004 18:50:09 -0800 (PST)
Received: from mail.dt.e-technik.uni-dortmund.de
	(krusty.dt.E-Technik.Uni-Dortmund.DE [129.217.163.1])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 8EFE943D2D
	for <freebsd-current@freebsd.org>;
	Tue, 20 Jan 2004 18:50:07 -0800 (PST)
	(envelope-from ma@dt.e-technik.uni-dortmund.de)
Received: from m2a2.dyndns.org (krusty.dt.e-technik.uni-dortmund.de
	[129.217.163.1])9404F1AF9B	for <freebsd-current@freebsd.org>;
	Wed, 21 Jan 2004 03:50:06 +0100 (CET)
Received: by merlin.emma.line.org (Postfix, from userid 500)
	id 24E38A1497; Wed, 21 Jan 2004 03:50:04 +0100 (CET)
To: freebsd-current@freebsd.org
From: Matthias Andree <ma@dt.e-technik.uni-dortmund.de>
Date: Wed, 21 Jan 2004 03:50:04 +0100
Message-ID: <m37jzmdnhf.fsf@merlin.emma.line.org>
User-Agent: Gnus/5.110002 (No Gnus v0.2) Emacs/21.2 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Subject: How to fsck -CURRENT on next reboot [ext2fs]
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Jan 2004 02:50:09 -0000

To have your FreeBSD -CURRENT fsck all ufs file systems at next reboot, do:

1. mount_ext2fs an ext2 or ext3 file system for read/write
2. change a file (or touch or rm one)
3. umount that ext2fs again

4. See how it complains about giving up on fsync first for the ext2fs, then
   for devfs.

5. Now reboot.

6. syncher gives up on 3 buffers (I have / /var and /usr - coincidence?)

7. At boot, fsck complains about non-cleanly umounted file systems

For added fun, try instead of 5., try:

5B. umount -f on the ext2fs that you modified instead of reboot
6B. See the kernel panic
7B. savecore logs "reboot after panic: vinvalbuf: dirty bufs"

e2fsprogs (with mke2fs, the ext2fs newfs tool) are available as port
from http://mandree.home.pages.de/freebsd/e2fsprogs/ while Tytso
(e2fsprogs maintainer) reviews my changes - feedback on my port is
appreciated. The e2fsprogs stuff from official ports doesn't work
because it assumes that block devices are buffered.

-- 
Matthias Andree

Encrypt your mail: my GnuPG key ID is 0x052E7D95