Message-ID: <40DC62BD.3010607@techsource.com>
Date: Fri, 25 Jun 2004 13:37:01 -0400
From: Timothy Miller <miller@techsource.com>
MIME-Version: 1.0
To: Pavel Machek <pavel@suse.cz>
CC: alan <alan@clueserver.org>, "Fao, Sean" <Sean.Fao@dynextechnologies.com>,
       linux-kernel@vger.kernel.org, Amit Gud <gud@eth.net>
Subject: Re: Elastic Quota File System (EQFS)
References: <20040624220318.GE20649@elf.ucw.cz> <Pine.LNX.4.44.0406241544010.19187-100000@www.fnordora.org> <20040625001545.GI20649@elf.ucw.cz>
In-Reply-To: <20040625001545.GI20649@elf.ucw.cz>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1076
Lines: 24


I have a much simpler idea that both implements the EQFS and doesn't 
touch the kernel.

Each user is given a quota which applies to their home directory.  (This 
quota is not elastic and if everyone met their quota, everything would 
fit.)  In addition, there is another directory or file system (could be 
on the same disk or even the same partition) to which their quota 
doesn't apply AT ALL.  Let's call this "scratch" space.

Periodically, a daemon checks the disk usage, and whenever the disk 
usage approaches, say, 90%, its starts deleting the oldest files from 
the scratch space until its gets below the watermark.

So anything in "/scratch/$USER/" is free to be deleted by the daemon.

BTW, they did something similar to this when I was in college (I 
graduated in 1996), although they deleted from /scratch manually.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/