From owner-freebsd-hackers  Tue Jul 23 02:36:57 1996
Return-Path: owner-hackers
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id CAA02170
          for hackers-outgoing; Tue, 23 Jul 1996 02:36:57 -0700 (PDT)
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19])
          by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id CAA02158
          for <hackers@freebsd.org>; Tue, 23 Jul 1996 02:36:48 -0700 (PDT)
Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.12/8.6.9) id PAA20581; Tue, 23 Jul 1996 15:43:02 +1000
Date: Tue, 23 Jul 1996 15:43:02 +1000
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199607230543.PAA20581@godzilla.zeta.org.au>
To: hackers@freebsd.org, rhh@ct.picker.com
Subject: Re: EXT2FS fails to sync ("giving up")
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

>     Running 2.2-960612-SNAP, if I leave a EXT2FS file system mounted
>(read-write or read-only), reboot doesn't get past it ("Syncing disks ... 1
>1 1 1 1 ... giving up") and doesn't get around to syncing the other UFS
>partitions on my system (4 UFS slices).  Couple questions:

Other file systems get synced (otherwise there would be more than 1 dirty
block) but their clean flag doesn't get set (so they get checked on reboot,
and checking takes too long).

>     1) Has this been fixed in -current?  If so, any tips on hacking it
>        into 2.2-960612-SNAP?

No, it's still broken.

Bruce