Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.3 alpha 4/15/85; site elsie.UUCP
Path: utzoo!linus!philabs!cmcl2!seismo!elsie!ado
From: ado@elsie.UUCP (Arthur David Olson)
Newsgroups: net.unix-wizards
Subject: Re: Quelling Filesyustem Activity
Message-ID: <5130@elsie.UUCP>
Date: Mon, 20-May-85 09:41:57 EDT
Article-I.D.: elsie.5130
Posted: Mon May 20 09:41:57 1985
Date-Received: Tue, 21-May-85 04:46:13 EDT
References: <134@kontron.UUCP>
Organization: NIH-LEC, Bethesda, MD
Lines: 19

The usual way of doing file system backups is to identify processes using the
file system, doing in all such processes, unmounting the system, and proceeding
with the dump.

How about being able to "freeze" file systems instead?  Once a freeze system
call was issued for a file system, processes that attempted to write to it
would block until the appropriate "thaw" call was made.

Seems to me like a cleaner solution that the "fuser" and "ofile" approaches
that have been discussed.  And you can avoid doing in any processes.

(Question for those in the know:  could such an idea be implemented using any
of the file locking schemes that exist now?)
--
UNIX is an AT&T Bell Laboratories trademark.
Activity is the beaver's trademark.
--
	UUCP: ..decvax!seismo!elsie!ado    ARPA: elsie!ado@seismo.ARPA
	DEC, VAX and Elsie are Digital Equipment and Borden trademarks