From owner-freebsd-hackers  Wed Jul 19  5: 1:11 2000
Delivered-To: freebsd-hackers@freebsd.org
Received: from axl.ops.uunet.co.za (axl.ops.uunet.co.za [196.31.2.163])
	by hub.freebsd.org (Postfix) with ESMTP id 41BB637BA68
	for <hackers@freebsd.org>; Wed, 19 Jul 2000 05:00:57 -0700 (PDT)
	(envelope-from sheldonh@axl.ops.uunet.co.za)
Received: from sheldonh (helo=axl.ops.uunet.co.za)
	by axl.ops.uunet.co.za with local-esmtp (Exim 3.15 #1)
	id 13EsWu-00005b-00
	for hackers@FreeBSD.org; Wed, 19 Jul 2000 14:00:48 +0200
From: Sheldon Hearn <sheldonh@uunet.co.za>
To: hackers@FreeBSD.org
Subject: crash during sync(2) still damages filesystems
Date: Wed, 19 Jul 2000 14:00:48 +0200
Message-ID: <346.964008048@axl.ops.uunet.co.za>
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


Hi folks,

I recently added a syncer(4) manual page to 5.0-CURRENT, to replace the
obsolete update(4) page.  I want to know whether the BUGS section, which
I copied from update(4), is still true:

BUGS
     It is possible on some systems that a sync(2) occurring simultaneously
     with a crash may cause file system damage.  See fsck(8).

It seems reasonable that this would still be true, but I wouldn't have a
clue either way.  Anyone care to confirm or deny?

Ciao,
Sheldon.


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message