From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <3B073602.5B439C05@princeton.edu>
From: Martin Harriss <martin@Princeton.EDU>
MIME-Version: 1.0
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Worm consumption (was: Re: tracking file modifiers)
References: <20010519234657.4A6FC199C1@mail.cse.psu.edu>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Date: Sat, 19 May 2001 23:12:02 -0400
Topicbox-Message-UUID: a33580a2-eac9-11e9-9e20-41e7f4b1d025

Paul C Lustgarten wrote:

>
> Also, on the topic of managing WORM consumption,
> is there some way to protect the WORM from excess
> consumption, using the new muid or otherwise?
> I'm thinking of scenarios such as programming mistakes
> where a user accidentally writes a bunch of stuff that
> they didn't intend and don't notice, or where they do
> something stupid like copying over the entire project's
> source tree in order to make a personal build with
> a couple of modified files.  I keep thinking of being
> able to impose per-user quotas that would be enforced
> by the system itself (as part of the nightly dumps?),
> as a safety measure complementing the economic
> incentive created by charging the projects for what
> their users do consume.

You might consider having a separate "scratch" file system not backed up by
a WORM.  Anything transient you put in scratch.  Anything precious you put
in the WORMed file system.

Martin