Re: Volume Managers in Linux

Brandon S. Allbery KF8NH (allbery@kf8nh.apk.net)
Thu, 05 Nov 1998 18:18:53 -0500


In message <Pine.LNX.3.96.981105095606.701A-100000@rainbow.studorg.tuwien.ac.
at
>, Andreas Kostyrka writes:
+-----
| > Bullshit. It's your fault for not putting quotas on it.
| Hmmm.Ok, for starters:
| -) How do you enable quotas >32bit?
| Say luser X may produce 5GB data trash *g*?
| -) How do you express with quotas that you don't care about files below x
| but REALLY care about the other ones. Example: I (with some of our
| clients) ``don't care'' about /var, because on these sites only lpr
| will be affected. WHAT I care about is /home, that contains data files
| from software that I didn't test for ``disk full'' conditions.
+--->8

How do you deal with space crunches caused by root daemons? I'm thinking
specifically of one which I usually end up finding and fixing on older ECE
machines: /{usr,var}/vice/cache fills up the filesystem it's on and both
the AFS client and the system start doing weird things. Nowadays we give
/var/vice/cache its own partition so the system doesn't go insane when AFS
oversteps its cache limits. (And even if a quota could be applied, its main
effect would likely be to confuse the AFS client even more. It's not very
smart about caching....)

Also, there's the question of quota overcommit: even with restrictive
quotas, one might still run out of disk space if the quotas add up to more
space than is available. Keeping track of that can be an administrative
nightmare even with decent tools.

Quotas are a possible answer for some situations, but not for all of them.

-- 
brandon s. allbery	[os/2][linux][solaris][japh]	 allbery@kf8nh.apk.net
system administrator	     [WAY too many hats]	   allbery@ece.cmu.edu
carnegie mellon / electrical and computer engineering			 KF8NH
			  Kiss my bits, Billy-boy.

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