FS_DIRNAME_ALLOCATED(Windows) not updated when disk extended
When a Windows drive is extended, the metric FS_DIRNAME_ALLOCATED is not re-evaluated. This causes false alerts from the SI disk space monitoring policies which read this value.
When I restarted the agent, the disk size was re-calculated correctly. Obviously I don't want to have to restart the agent every time a disk is extended (which we frequently do, now that is quite easy with a SAN).
Re: FS_DIRNAME_ALLOCATED(Windows) not updated when disk extended
Thanks Ram. I did look at the release notes for 11.11 and 11.12 but nothing there.
[ and of course I meant FS_MAX_SIZE ..]
But - I did find the following in the OAWIN_00030 patch notes (we have not implemented 11.11/11.12 yet because we are waiting to move to OMW9). Upgrading to 11.12 might be the solution but it's a bit drastic for us at present and I'd rather have a patch or hotfix for 11.05.... Do you think this is related?-
Change Request: QCCR1A158028
The "SI_DiskCapacityMonitor" policy is reporting
incorrect disk space utilization on some of the file
servers. It is reporting "Free space on disk = 0 MB" when
there are plenty of disk space available on the drive.
When "ovcodautil -dumpds SCOPE" is run on the server, the
results for the drive in question is:
FS_BLOCK_SIE = 4096
FS_MAX_SIZE = 819200
FS_SPACE_UTIL = 100.00
FS_SPACE_USED = 16731957
Here the FS_SPACE_USED is higher than FS_MAX_SIZE.This is
causing the "SI_DiskCapacityMonitor" policy to generate
an alert for zero disk space when there are more then 400
GB of disk space available.