From owner-freebsd-hackers  Sun Mar 19 08:57:09 1995
Return-Path: hackers-owner
Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id IAA13671 for hackers-outgoing; Sun, 19 Mar 1995 08:57:09 -0800
Received: from LOCALHOST (LOCALHOST [127.0.0.1]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id IAA13664; Sun, 19 Mar 1995 08:57:07 -0800
X-Authentication-Warning: freefall.cdrom.com: Host LOCALHOST didn't use HELO protocol
To: Remy.Card@masi.ibp.fr
cc: hackers@FreeBSD.org
Subject: Re: Filesystem clean flag 
In-reply-to: Your message of "Sun, 19 Mar 95 16:58:08 GMT."
             <199503191658.QAA00122@bbj.ibp.fr> 
Date: Sun, 19 Mar 1995 08:57:07 -0800
Message-ID: <13663.795632227@freefall.cdrom.com>
From: "Jordan K. Hubbard" <jkh@freefall.cdrom.com>
Sender: hackers-owner@FreeBSD.org
Precedence: bulk

> 	Correcting this problem is trivial: when a filesystem is mounted in
> read-write mode, store the value of the clean flag and restore this value in
> the superblock when the filesystem is unmounted.

This sounds interesting.

> 	Also, I have compared the clean flag implementation with my own
> implementation in the Linux Ext2 filesystem and I found that FreeBSD does
> not allow the administrator to request periodical checks of the filesystems.

I don't see how this buys us much, unless your ext2fs code works so
differently from FFS that in-situ filesystem checks yield anything but
bogus "corruption" errors that are really just the result of reading
filesystem operations in mid-progress.  Do you have a flag that locks
the filesystem out for write access while you're checking it (and
syncs it first, of course)?

> 	Please, no ``BSD vs Linux'' or ``UFS vs Ext2fs'' war! :-)

Naw, I'm more inclined to ask about Ext2FS on FreeBSD.  How is that
little project coming? :-)

						Jordan