03-18-2015 09:50 PM
Its urgent, provide the steps to do the clean up. Already requested OS team for FS extension.
Thanks,
Solved! Go to Solution.
03-20-2015 09:28 AM
Depends where the problem is. You'll need to breakdown the filesystem, hence how big is it in total and how does it break down?
One possible place to target would be logfiles which may or may not be in the same space. There are plenty other candidates. Jim
03-22-2015 03:14 AM
# du -ks /usr/openv
gives you a breakdown of how much spaces used up under each subdir.
If you find /usr/openv/logs is the one that has most HUGE files (usually so), then use this to delete it fast - of course be diligent that you don't need them first:
# vxlogmgr -d -e "2/28/2015 00:00:00 AM"
this will delete all files under that /usr/openv/logs which are dated before Feb28 2015. Don't worry, it will give you a list of what to delete first before you hit confirmation or cancel.
Finally, look at /usr/openv/netbackup/logs for other big logs.
03-20-2015 09:28 AM
Depends where the problem is. You'll need to breakdown the filesystem, hence how big is it in total and how does it break down?
One possible place to target would be logfiles which may or may not be in the same space. There are plenty other candidates. Jim
03-22-2015 03:14 AM
# du -ks /usr/openv
gives you a breakdown of how much spaces used up under each subdir.
If you find /usr/openv/logs is the one that has most HUGE files (usually so), then use this to delete it fast - of course be diligent that you don't need them first:
# vxlogmgr -d -e "2/28/2015 00:00:00 AM"
this will delete all files under that /usr/openv/logs which are dated before Feb28 2015. Don't worry, it will give you a list of what to delete first before you hit confirmation or cancel.
Finally, look at /usr/openv/netbackup/logs for other big logs.
03-25-2015 03:36 AM