UNSOLVED
Is there overhead in the file system when viewing properties from windows?
We are in process of migrating from one Celerra to another. The issue we are seeing is a mismatch between what the File properties on the drive see's and the file properties on the folders when selected.
For instance we have a share called \\homeserver\shared that share when mapped to a drive letter lets say T: would say it has 500 gigs total and 450 gigs used and 50 gigs free. However when you go inside the T: folder and select all the folders and right click and go to properties it comes back and says it only has 374 gigs of space used. We were wondering if we have a permission error to some files or something else is going on? We are using a domain admin account and that account is also a member of backup operators so should have full access to everyting and no error messges. Does anyone have a clue as to what is going on? Thanks in advance.
Rainer_EMC
6 Operator
•
8645 Posts
205
0
Posted September 12th, 2011 16:00
if you arent able to ssh into the control station that needs to be fixed
Even if you cant ssh you can still execute CLI commands form UniSphere / Celerra Manager
Rainer_EMC
6 Operator
•
8645 Posts
298
0
Posted September 12th, 2011 16:00
the "drive" properties most likely show the file system stats - i.e. what server_df says
It doesnt go through all the files/dirs and counts the usage like directory properties
And yes - if you dont have permission to enter a directory you cant count its disk usage
As Claude said Backup Operator privilege doesnt mean anything if the application isnt programmed to use it.
Even then its very specific and a "super user"
Rainer
Rainer_EMC
6 Operator
•
8645 Posts
461
0
Posted September 12th, 2011 16:00
NO – this is specific for quota’s and you said you dont have quotas in use
A reliable alternative to count disk usage would be via NFS
Rainer
lunz3
41 Posts
461
0
Posted September 12th, 2011 11:00
Looks like it may be some kind of bug. Apparently they are having same issue they said they ran some script from the lab to fix it.
https://community.emc.com/message/382524
Intersting though I do not have the fix but curious to know what that might be.