From ken@cac.washington.edu Thu Sep 4 20:18:02 1997 Received: from mx2.u.washington.edu (mx2.u.washington.edu [140.142.32.7]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id UAA42298 for ; Thu, 4 Sep 1997 20:18:00 -0700 Received: from dewey.cac.washington.edu (dewey.cac.washington.edu [128.95.135.7]) by mx2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.04) with SMTP id UAA29083 for ; Thu, 4 Sep 1997 20:17:57 -0700 Received: by dewey.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA08787; Thu, 4 Sep 97 20:17:54 -0700 Date: Thu, 4 Sep 97 20:17:54 -0700 From: Ken Lowe Message-Id: <9709050317.AA08787@dewey.cac.washington.edu> To: change-l@u.washington.edu Subject: 09/10: 100MB quota support The "100 megabyte quotas" project as it was given to me was described as: 1) People will get 100MB disk quotas 2) The 100MB disk quotas will be overall, not 100 for homer plus 100 for saul... 3) We'll be able to up homer's quota soon, but dante and saul will have to wait for additional disk units. In order to implement item #2 quite a few internal pieces have to change. I'd like to install those changes on Wednesday Sept 10th. The disks are not yet available (not even homer's) so no one will see increases in quotas yet, but the underlying mechanisms will be there to support it. There are a couple user-visable changes that should be noted: x) The global limit will initially be set to 100MB or your maximum quota on any one galaxy, whichever is larger. Your maximum usage on any filesystem is the lesser of your limit for that galaxy minus the usage on all other filesystems on that galaxy or your global limit minus the usage on all other filesystem. Some people have combined limits that exceed 100MB. These people will get an entry in a special grandfather pseudo-galaxy with a limit of the sum of all their quotas on the current real galaxies (which will also be the global limit). The end result of this is "business as usual" for now. When your limit on homer is raised to 100MB, however, incoming mail there could cause you to run out of space on your mead/saul account. x) The output of the "assets -q" command will now list all disks that affect the user's quota allocation. The old assets -q only shows the quota for mounted filesystems (plus your mailer). Thus an "assets -q" on homer will show your usage on your saul home directory as well as your homer and mailer home directories. x) Assets -q will no longer show chkout space. The "quota" command will continue to just show the locally mounted disks including the chkout disks. x) A new option "assets -m" will show your maximum disk usage on each galaxy and overall. The overquota is labelled "global", the grandfather entry is labelled "maximum". x) Adjquota will only update disk quotas where you actually have files. In the past an adjquota on saul had to update 46 /uaNN filesystems when you probably only had files on one of them. This should speed things up, in particular the nightly adjquota that adjusts everyone's disk quotas. -Ken ------ Example: User "susan" currently has: homer 20MB saul 20MB becker 6MB This user will get a global quota of 100MB, but the sum of all her limits is only 46MB so the global quota won't come into effect. She will continue to be able to use the above limits on the respective galaxies. When her homer limit gets bumped to 100MB she'll be able to use up to 100MB on homer. As long as her homer usage stays below 74MB it won't affect saul or becker. If she subscribes to the GIF-of- the-month mailing list, and goes up to 90MB on homer, she'll only have 10MB left. She could use 6 of it on becker or up to 10 on either saul or homer, but not both. .