That very similar to our architecture, only we don’t move the user’s home share we use DFM to manage the quota size and upgrade them in place thus avoiding needing to migrate dozens of users every day (We used to migrate users into a new quota bucket but it became too labor intensive as we have over 80,000+ home shares, and 50,000+ users) .

Do you use CIFS homedir to make the username$ share, or do you manually make the shares? Are you shared user folders Qtrees?

From: Warkentin, Grant [mailto:Grant.Warkentin@calgary.ca]
Sent: Friday, August 07, 2009 8:06 AM
To: Langdon, Laughlin T. (Lock); 'toasters@mathworks.com'
Subject: RE: User based Quotas - Why don't they show up correctly when mapped?

Don’t know if this will help but …

in a nut shell, Have you tried setting a default user quota on the home qtree then assigning each user a specific quota in addition to the default?

Have no issues with user quotas showing up properly here.

Our structure is like:

/cifsvolume/homeqtree2

/cifsvolume/homeqtree5

/cifsvolume/homeqtree10

Each of the home qtrees has a default user quota applied

- Container one defaults to 250 meg per user

- Container two = 500 meg default

The last container has a default quota of 2 gig.

If someone needs a larger quota we move the home directory to the next container. We then have to run NTFSchown to set the file ownership. If someone exceeds the largest default, I apply a specific user quota only to that person. Manage by exception thing.

Moving home folders and chowning is a bit of a pain but I could not think of a better way to do this without having to apply specific quotas to all 12,000 accounts. We don’t get a lot of requests for larger home quotas - about ½ a dozen or less per week.

Our home drive shares are set to the hidden style. When each user connects they map to \\filer\username$ to get their H: I made a mistake when setting this up. We can assign a home drive mapping to the user in the Active directory MMC but the MMC will not create the H drive. We have to create the home folder manually. Not a big issue as we are not allowed to create user accounts manually. Our IDM system has a script that runs to create and ACL the home folder when the account is created.

One other thing:

We use windows folder redirection here to ensure that the “my documents” folder is saved to the user’s H: drive. Could not make this work until we gave each user full-control on their own H:. This has nothing to do with quotas not showing up properly. Quotas worked fine before this change. Thought I’d mention it though.

From: owner-toasters@mathworks.com [mailto:owner-toasters@mathworks.com] On Behalf Of Langdon, Laughlin T. (Lock)
Sent: 2009 August 05 9:47 AM
To: toasters@mathworks.com
Subject: User based Quotas - Why don't they show up correctly when mapped?

More fun with user based quotas. When a user has a mapped CIFS share to their home drive the size of the entire volume shows up when they map the drive. I thought user quotas used to just show the "quotaed" space for that user.

I.E. I have a 11TB volume. I create a user quota of 500MB and apply it to a user (say xyz99). When XYZ99's home share is mapped they see 11TB available to them, not 500MB. A tree based quota with a hard limit works just fine in showing only 500MB available.

I've worked with Netapp support and did get an obscure bug (88541) that has no information and a reply that there isn’t much information on this issue. (Maybe the functionality just isn’t there? I could swear we used to have that function.)

Does anyone use user quotas and have this same problem?

Are there better ways to do user home share type CIFS shares?

Thanks
lock

p.s. (Also posted on the NetApp Support Community if you want “points” for answering) J

https://forums.netapp.com/thread/2900

NOTICE -
This communication is intended ONLY for the use of the person or entity named above and may contain information that is confidential or legally privileged. If you are not the intended recipient named above or a person responsible for delivering messages or communications to the intended recipient, YOU ARE HEREBY NOTIFIED that any use, distribution, or copying of this communication or any of the information contained in it is strictly prohibited. If you have received this communication in error, please notify us immediately by telephone and then destroy or delete this communication, or return it to us by mail if requested by us. The City of Calgary thanks you for your attention and co-operation.