YDroid

updated

11 years ago

Y

YDroid

1 Rookie

•

61 Posts

0

7547

August 6th, 2008 09:00

Tree Quotas

Hi,

I am trying to enable tree quotas and having some problems. I created a file system "qtree_fs" then mounted it to "qtree_mp" mountpoint. And exported it to "qtree" cifs share. Then i created a "qtree_data" directory in there. unexported the share and re-exported to "/qtree_mp/qtree_data" this step was to hide lost+found and etc directories.

I tried enabling tree quotas using both CLI and celerra manager and getting error on both. at CLI i am using the following command

$$ nas_quotas -on -tree -fs qtree_fs -path /qtree_mp/qtree_data/dir1 comment "Tree quota test"

I get following error
Error 5005: server_2: file quota "/root_vdm_10/qtree_mp/qtree_mp/QTREE_DATA/dir1

I think its the path i am not entring correctly, but i changed every possible path. forexample

$$ nas_quotas -on -tree -fs qtree_fs -path /qtree/DATA/dir1 comment "Tree quota test"
Where DATA is another directory i created manually in qtree mountpoint.

Any help on this will be appreciated.

Thanks
  • nandas

    6 Operator

    •

    1473 Posts

    2251

    0

    Posted August 6th, 2008 12:00

    User/Group Quota is based on the file system - it works only on the file system not on any folder within a file system. In your case, you created a share on the folder under the root of the file system in order to avoid the visibility of the lost+found and .etc folders - so the mapped drive is not on the file system thus you are not seeing the quota tab in the property page of the mapped drive.

    You may create another share (may keep it hidden and available to you and/or administrators only) on the entire file system (at the root of the file system - in this case the path being /qtree_mp) - and then map a drive to this share. You 'll be able to see the Quota tab on this mapped drive property page if User Quota is turned ON on this file system.

    Hope this helps,
    Sandip
  • dynamox

    11 Legend

    •

    20419 Posts

    •

    87439 Points

    2250

    0

    Posted August 6th, 2008 10:00

    try creating it without specifying the root directory, for example my file system is mounted

    /HOME

    and underneath HOME i want to create a directory for Bob so i would do this:

    nas_quotas -on -tree -fs fs_name -path /Bob
  • richcrompton

    1 Rookie

    •

    21 Posts

    2250

    0

    Posted August 6th, 2008 10:00

    I believe the "comment" option requires a "-" in front ("-comment"), but that probably isn't causing this error.

    I think the path should begin with "/qtree_data". That's the directory in the root of the "qtree_fs" file system. Try the following:

    $$ nas_quotas -on -tree -fs qtree_fs -path /qtree_data/dir1

    (given "dir1" doesn't already exist).
  • Rainer_EMC

    6 Operator

    •

    8645 Posts

    2250

    0

    Posted August 6th, 2008 10:00

    please post the output of "server_mount ALL | grep qtree"

    the -path in nas_qoutas has to start from the fs root

    in lab case:

    [nasadmin@ns20 log]$ server_mount ALL | grep home
    fs_home on /root_vdm_1/fs_home uxfs,perm,rw
    fs_home on /fs_home uxfs,perm,rw

    I have create a directory named qtree_data in the root of the fs and the following worked

    nas_quotas -tree -on -fs id=59 -path /qtree_data/dir1

    when in doubt a good trick to figure out the CLI syntax is to do it using the GUI and then do a "tail /nas/log/cmd_log" and see what it actually did :-)
  • YDroid

    1 Rookie

    •

    61 Posts

    2250

    0

    Posted August 6th, 2008 12:00

    Thanks Rainer that worked. In contiunation to the same problem......

    I have tree quotas enabled, then i enabled user quotas too. It works fine but i cant see the quota tab when i go to properties of the mapped drive of my file system. Any suggestions on what am i missing here
  • YDroid

    1 Rookie

    •

    61 Posts

    2251

    0

    Posted August 6th, 2008 13:00

    Sandip,

    I couldnt get this, can you please tell me steps on how to acheive this.

    -- create a file system
    -- create a mountpoint
    -- mount the file system
    -- ??


    Thanks
  • nandas

    6 Operator

    •

    1473 Posts

    2251

    0

    Posted August 6th, 2008 14:00

    I mean to say - you need to create a CIFS share on the entire file system (on the root of the file system). A share on a directory or sub-directory will not provide you the Quota tab in the Windows Mapped Drive property page.

    So only thing you need to create is a CIFS share on the entire file system "qtree_fs" (path of the share will be "/qtree_mp" and then map a drive to this share - you will be able to view the quota tab.

    You may make this share hidden by adding $ at the end of the share name - say give a name "qtree$".

    Only difference is your existing CIFS share named qtree_data is on a folder - not on the root of the file system - the share path being "/qtree_mp/qtree_data" - thus you are not getting the quota tab when you map this share to a drive on windows client.

    Hope this provides more clarification.
    Thanks,
    Sandip
  • Rainer_EMC

    6 Operator

    •

    8645 Posts

    2251

    0

    Posted August 6th, 2008 14:00

    And that is actually due to Microsoft's implementation

    From the MS Quota App Help:

    To manage disk quotas on a remote computer

    1. Right-click My Computer, and then click Map Network Drive.

    2. In the Map Network Drive dialog box, in the Folder box, type the path to the volume on the remote computer for which you want
    to manage disk quotas, and then click Finish.

    3. After you connect to the remote computer's volume, open My Computer.

    4. Right-click the remote volume for which you want to manage disk quotas, and then click Properties.
    In the Properties dialog box, click the Quota tab.

    5. On the Quota property page, click Quota Entries.
    The Quota Entries window appears. Each row in the list contains information for a user of the volume.

    Notes

    To open My Computer, click Start, and then click My Computer.

    If the volume is not formatted with the NTFS file system, or if you are not a member of the Administrators group,
    the Quota tab is not displayed in the volume's Properties dialog box.

    To manage disk quotas on a remote computer volume, it must be shared from the volume's root directory and
    you must be a member of the Administrators group on the remote computer.
  • YDroid

    1 Rookie

    •

    61 Posts

    2251

    0

    Posted August 7th, 2008 08:00

    Sandip,

    This worked just like you said. Now i am trying to understand how windows management works if i set up quotas using celerra, can i still view quota entries etc from windows quota managment tab. I enabled quotas as follow

    i mounted the "qtree_fs" to a share "qtree$"
    i enabled tree quota for "qtree$" (with no limits)
    then i enabled user quotas for qtree$
    i created a folder in qtree$ and created cifs share for that to make etc and lost+found not visiable for end users

    I moved data for test users and users quota limits worked fine. But when i look at windows quota management for the root share "qtree$" i dont see the limits that i set through celerra manager, instead quotas arent enabled in windows quota managments. why is that? shouldnt it take the limits what i set in celerra manager?

    Message was edited by:
    technicolor
  • nandas

    6 Operator

    •

    1473 Posts

    514

    0

    Posted August 7th, 2008 09:00

    From Windows Quota tab - you can only see the User Quota not Tree quota. You can set the user quota same for all users using the Celerra Manager under User Quota settings - but if you want more granularity on the user quota limits, you can do the user quota settings from the Windows quota tab - where you can select different user quota settings for different users.

    But for tree quota - it is all done through the Celerra Manager or CLI - windows quota tab will not be able to show or handle the tree quota.

    I have not played with both user and tree quota for a while, so things may be little different with newer codes - but I hope my statement is true and you can also confirm the same.

    Regards,
    Sandip