PATROL for Unix and Linux: Unmounted filesystems still appearing and collecting the data |
This was observed that following pconfig rule have been applied through PCM for FSMountStatus parameter : /AS/EVENTSPRING/PARAM_SETTINGS/THRESHOLDS/FILESYSTEM/__ANYINST__/FSMountStatus: <0,0 0 0 0 0 0,0 0 0 0 0 2,0 0 0 0 0 0> If a filesystem gets unmounted, FSMountStatus will be set to 1 and DFColl will skip data collection for such filesystem instances. In this case, FSMountStatus was inactive hence DFColl failed to get its value and set data for instances. Changing the above rule to following rule, made FSMountStatus active and DFColl skipped data collection for unmounted instances. /AS/EVENTSPRING/PARAM_SETTINGS/THRESHOLDS/FILESYSTEM/__ANYINST__/FSMountStatus: <1,0 0 0 0 0 0,0 0 0 0 0 2,0 0 0 0 0 0> One more point: As per the functionality, one should provide a list of custom FileSystem types separated by 'space' and not by 'comma'. Please update the list of custom filesystem as : JFS2 JFS NAMEFS |