Questions about Quotas on VNX CIFS shares and not closing CIFS connections
I am in the process of setting up Quotas on an existing CIFS File System. I had enabled Quotas prior to the system being used for Production, but did not have the time to really think about how they should work. I have opened up a Ticket with EMC with the following Questions on April 4th. I am working from the Document "Using Quotas on VNX". Our file system Version is 7.0.53-2.
1. Question on the quota Policy (Block or File Size) and will changing that
setting effect access to data already on the system? It mentions in the
Document that you reboot the Data Mover, how does that effect current attached
users. My issue, is I had not changed this from the default and need to change it to
File Size so my quotas for users report the actual file sizes.
2. I can not manage the Quotas from a Windows System. I have tried
to map a drive letter to several places on the VNX from 3 Different Operating
systems and non of them show the Quota's Tab. I followed several articles in the forums
and have not found my piece of missing information, can some one explain the correct way to do this?
(You must map the root/mountpoint of the filesystem
to a drive letter and not a subdirectory (unless it was created as a tree quota), and even though you may
be tempted to try, neither of the following will expose the "Quotas" tab)
3. The storage reported by the different Quotas is not adding up.
On the Documentation it mentions to use the online Quota Update tool.
How does that effect users connecting to the system?
4. I have Several invalid Group Quotas that I would like to remove
from the system. I have tried to put a Zero in the Group Quota, and
also leave the values blank, but the Group Quota still shows up.
I don't want to disable group quotas, I just want to remove
the ones that are no longer valid groups or Users.
5. There is also a strange Error with attached Home Directories. The File system is
reading open files after users shut down there system (Start Shutdown). This is causing a pause during the logon
script when reconnecting the drives becasue of open files (the net use p: /delete command). The Error is "There are open files and or incomplete directory searches pending on the connection to p:" This has never happened prior when we had the User data on DAS attached to a windows server.
I am not sure I understand. If I map a share from a Windows Server and it is not persistant it goes away. If I map a share and it is persistant it returns when I log in. I have not tried to work as a user from a windows server on documents and files to see if the log on script pauses. It does not happen every time, so I am not sure what it is exactly that triggers the error.
Rainer_EMC
6 Operator
•
8645 Posts
714
0
Posted April 16th, 2013 07:00
If you have mapped a share from a Windows server and that gets rebooted - what effect does that have on your connection ?