Friends,
We have an F-740 with 14 - 18GB drives (2 hot spares) configured as one large volume. OnTap version 5.3.4R2. Security style is mixed. Currently it is being used by mostly UNIX users, with some Windows users, for Home directories and Project directories. There are only about 15 total active users on the Filer currently. The plan is to move the home directories for the remaining 60 or so mostly Windows users onto the Filer.
We would like to implement quotas on the Home directories, e.g. 150MB per user. At the same time, we would like to implement quotas on the Project directories -- my thinking is we would do this via a group quota, e.g. 5GB for Group A, 15GB for Group B, etc.
My questions are as follows:
1. Will we need to create separate volumes for Home dir's and Projects, so that the quotas will work as we intend (e.g. a user can own files in his Project directory without it counting against his User quota) -- or can we get away with qtrees? My suspicion is that we will need to start from scratch and create at least two volumes to do this.
2. Suggestions for the best strategy to accomplish this, maintaining all CIFS & NFS metadata? We are currently dumping the filer as one big volume to DLT (<35GB). Does the filer's dump command support dump from a directory, so that we could restore to our new volumes or qtrees? Any other strategies?
Thanks in advance!
Daniel Oxenhandler Network Engineer Sprint Laboratories 650-375-4281
daniel@sprintlabs.com (Daniel Oxenhandler) writes:
We have an F-740 with 14 - 18GB drives (2 hot spares) configured as one large volume. OnTap version 5.3.4R2. Security style is mixed. Currently it is being used by mostly UNIX users, with some Windows users, for Home directories and Project directories. There are only about 15 total active users on the Filer currently. The plan is to move the home directories for the remaining 60 or so mostly Windows users onto the Filer.
We would like to implement quotas on the Home directories, e.g. 150MB per user. At the same time, we would like to implement quotas on the Project directories -- my thinking is we would do this via a group quota, e.g. 5GB for Group A, 15GB for Group B, etc.
My questions are as follows:
- Will we need to create separate volumes for Home dir's and Projects, so
that the quotas will work as we intend (e.g. a user can own files in his Project directory without it counting against his User quota) -- or can we get away with qtrees? My suspicion is that we will need to start from scratch and create at least two volumes to do this.
You don't need separate volumes: separate qtrees will do everything you need. You can make specific or default per-uid or per-gid quotas that apply only within a particular qtree: see the na_quotas man page for the syntax.
That's what we do with our home directories: they are all in a qtree named (imaginatively) /home, in which per-uid quotas apply, while other qtrees on the same volume contain "group filespaces" (much like your Projects) and applications software, and are all controlled by tree quota only.
We don't use per-gid quotas because early experiments with this led us to the conclusion that the gids of files are too easily changed, either deliberately or accidentally, even with g+s on the top directories. This has caused us to end up with rather a lot of piddling little qtrees, though (and there's a limit of 254 per volume).
One possibility that occurs to me is that you could put several of your "Projects" in one qtree, control them by gid, *and* have a default quota of zero for all gids you aren't associated with any Project. We've used zero default quotas for *uids* in this way to keep unwanted users out of our /home, and it works fine.
- Suggestions for the best strategy to accomplish this, maintaining all
CIFS & NFS metadata? We are currently dumping the filer as one big volume to DLT (<35GB). Does the filer's dump command support dump from a directory, so that we could restore to our new volumes or qtrees? Any other strategies?
Sure you can dump any directory tree, or even several different ones at once (if they are in the same volume). See the na_dump man page: it's all described there. Dumping whole qtrees can be somewhat more efficient than dumping arbitrary directory trees, but they both work.
Chris Thompson University of Cambridge Computing Service, Email: cet1@ucs.cam.ac.uk New Museums Site, Cambridge CB2 3QG, Phone: +44 1223 334715 United Kingdom.
Another point you would like to take into consideration is the future growth of your data. One serious drawback to having one large volume is that in the event of a disaster, recovering one large volume is much more time consuming than recovering two smaller volumes. We try keeping our volumes under 200-250 GB. Splitting a large volume in to smaller ones is very time consuming, requires redundent resources (disks) and requires user downtime while you sync the data.
daniel@sprintlabs.com (Daniel Oxenhandler) writes:
We have an F-740 with 14 - 18GB drives (2 hot spares) configured as one large volume. OnTap version 5.3.4R2. Security style is mixed. Currently it is being used by mostly UNIX users, with some Windows users, for Home directories and Project directories. There are only about 15 total active users on the Filer currently. The plan is to move the home directories for the remaining 60 or so mostly Windows users onto the Filer.
We would like to implement quotas on the Home directories, e.g. 150MB per user. At the same time, we would like to implement quotas on the Project directories -- my thinking is we would do this via a group quota, e.g. 5GB for Group A, 15GB for Group B, etc.
My questions are as follows:
- Will we need to create separate volumes for Home dir's and Projects, so
that the quotas will work as we intend (e.g. a user can own files in his Project directory without it counting against his User quota) -- or can we get away with qtrees? My suspicion is that we will need to start from scratch and create at least two volumes to do this.
- Suggestions for the best strategy to accomplish this, maintaining all
CIFS & NFS metadata? We are currently dumping the filer as one big volume to DLT (<35GB). Does the filer's dump command support dump from a directory, so that we could restore to our new volumes or qtrees? Any other strategies?
On Tue, Jun 27, 2000 at 09:50:01PM +0100, Chris Thompson wrote:
daniel@sprintlabs.com (Daniel Oxenhandler) writes:
- Will we need to create separate volumes for Home dir's and Projects, so
that the quotas will work as we intend (e.g. a user can own files in his Project directory without it counting against his User quota) -- or can we get away with qtrees? My suspicion is that we will need to start from scratch and create at least two volumes to do this.
You don't need separate volumes: separate qtrees will do everything you need. You can make specific or default per-uid or per-gid quotas that apply only within a particular qtree: see the na_quotas man page for the syntax.
it will of course be cleaner to create separate volumes, and in some situations make more sense and reduce operational overhead. user quotas apply on a per volume basis, not on a qtree basis. this means that users may be prevented from writing to 'project' directories once their home dir starts to fill up. depending on your clients, files may be truncated as they are opened ( Older versions on FreeBSD did this ) if a user is over their quota. in order to add a new qtree/user quota ( if you don't use a default user quota) you have to toggle quotas off/on.
-s
User & Group quotas may exist at either the Volume level and/or the qtree level:
/etc/quotas: #volume tree quotas /vol/vol0 tree 50G - /vol/vol1 tree 20G - #default tree quotas * tree@/vol/vol0 - - * tree@/vol/vol1 - - #qtree quotas /vol/vol0/dir1 tree 15G - /vol/vol1/dir1 tree 5G - #user quotas per volume tmac user@/vol/vol0 5M - john user@/vol/vol1 5M - #default user quota per volume * user@/vol/vol0 3M - * user@/vol/vol1 3M - #user quotas per qtree tmac user@/vol/vol0/dir1 3M - john user@/vol/vol1/dir1 3M - #default user quotas per qtree * user@/vol/vol0/dir1 2M - * user@/vol/vol1/dir1 2M -
For group quotas, simply replace user with group. The first column can be a UNIX UID(user) or GID(group). It can also be a name if you use /etc/passwd or NIS.
--tmac
Steve Armijo wrote:
On Tue, Jun 27, 2000 at 09:50:01PM +0100, Chris Thompson wrote:
daniel@sprintlabs.com (Daniel Oxenhandler) writes:
- Will we need to create separate volumes for Home dir's and Projects, so
that the quotas will work as we intend (e.g. a user can own files in his Project directory without it counting against his User quota) -- or can we get away with qtrees? My suspicion is that we will need to start from scratch and create at least two volumes to do this.
You don't need separate volumes: separate qtrees will do everything you need. You can make specific or default per-uid or per-gid quotas that apply only within a particular qtree: see the na_quotas man page for the syntax.
it will of course be cleaner to create separate volumes, and in some situations make more sense and reduce operational overhead. user quotas apply on a per volume basis, not on a qtree basis. this means that users may be prevented from writing to 'project' directories once their home dir starts to fill up. depending on your clients, files may be truncated as they are opened ( Older versions on FreeBSD did this ) if a user is over their quota. in order to add a new qtree/user quota ( if you don't use a default user quota) you have to toggle quotas off/on.
-s
-- Cue the music, fade to black, no such thing as no payback. -PWEI
[ armijo@cs.unm.edu ]
-- ******All New Numbers!!!****** ************* *************
Timothy A. McCarthy --> System Engineer, Eastern Region Network Appliance http://www.netapp.com 240-268-2034 Office \ / Page Me at: 240-268-2001 Fax / 888-971-4468
-
Chris Thompson -
Daniel Oxenhandler -
Menachem Kaiser -
Steve Armijo -
Timothy A. McCarthy