Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

VMware Cloud Foundation SDDC-Manager nfs-mount 100% Full (79353)

Last Updated: 2/27/2024Categories: TroubleshootingTotal Views: 2895Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

The nfs repo on SDDC manager is either full or getting close to it. When you run prechecks you will see errors about it being less than required (OR)

 LCM-Bundle-repo, datastore usage on disk alert: only 25GB free out of 502GB.  Need help in expanding the NFS share in SDDC manager to resolve the errors

Purpose

To resolve the issue of SDDC-Manager nfs-mount 100% full

Cause

/dev/mapper/lcmmount_vg-nfs--mount 503G 478G 0 100% /nfs/vmware/vcf/nfs-mount

As per the retention policy properties, cron job should delete the nsx backup files more than 2 weeks also lcm backup files should not exceed more than 5 files.

This can be checked by looking at the following file:

root@sddcmgr-1 [ /nfs/vmware/vcf/nfs-mount/backup/scripts ]# cat nsx_backup_config.properties
# All properties are mandatory.
# Property BACKUP.RETENTION.HOURS is used for retention policy. All backup files past # 'N' hours will be retained and rest will be deleted in current day.
# Constraints : Min 2
BACKUP.RETENTION.HOURS=6

# Property BACKUP.RETENTION.DAYS is used for retention policy. A single latest backup file # for a day for 'N' number of days will be retained and rest will be deleted in that day.
# Example, if there are hourly backups configured and say there are backups for each hour, # files will be evo-nsx-******-23_0-****.backupproperties,
# evo-nsx-******-22_0-****.backupproperties, evo-nsx-******-21_0-****.backupproperties,....
# In above file list latest would be at 23:00, so file evo-nsx-******-23_0-**** # will be retained.
# Constraints : Min 1
BACKUP.RETENTION.DAYS=7

# Property BACKUP.RETENTION.WEEKS is used for retention policy. A single latest backup # file for a week for 'N' number of weeks will be retained and rest will be deleted in # that week.
# Example, if there are hourly backups configured and say there are backups for each hour, # files on the last day of the week ie on Sunday will be evo-nsx-******-23_0-Sun***.backupproperties,
# evo-nsx-******-22_0-Sun***.backupproperties, evo-nsx-******-21_0-Sun***.backupproperties,....
# In above file list latest would be at 23:00, so file evo-nsx-******-23_0-Sun*** # If there is no file available on Sunday then previous day will be checked until # start day of the week.
BACKUP.RETENTION.WEEKS=2

# Enable log LEVEL
# Allowed levels INFO and DEBUG
BACKUP.LOGGER.LEVEL=INFO

Backup is taking most of the space in the directory.

The cronjob for cleaning the nsxbackup files is failing due to an issue with the script nsxbackupcleaner.py and fills the space of NFS share

Impact / Risks

Pre-checks can have issues.

Data may not be displayed or SDDC is not responding

Resolution

Make a copy of the file nsxbackupcleaner.py before making necessary changes.

cat the file nsxbackupcleaner.py and copy the contents into Note++ so you can see the line number to help with making the changes.

Edit file:

root@sddcmgr-1 [ /nfs/vmware/vcf/nfs-mount/backup/scripts ]# vi nsxbackupcleaner.py

Here is what needs to be changed, there are 3 lines:
Line #142 -->> backup_files_for_day.sort(key=lambda x: os.path.getctime(x), reverse=True)
Change to -->>
backup_files_for_day = sorted(backup_files_for_day, key=lambda x: os.path.getctime(x), reverse=True)

Line # 190 -->> backupfilesForDay.sort(key=lambda x: os.path.getctime(x), reverse=True)
Change to -->> backupfilesForDay = sorted(backupfilesForDay, key=lambda x: os.path.getctime(x), reverse=True)

Line #260 -->> files.sort(key=lambda x: os.path.getctime(x), reverse=True)
Change to -->> files = sorted(files, key=lambda x: os.path.getctime(x), reverse=True)Once, the file is updated then rerun the command to cleanup the backup files.
root@sddcmgr-1 [ /nfs/vmware/vcf/nfs-mount/backup/scripts ]# ./nsx_backup_cleanup.sh

Run df -h again and it should be less Use% space

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

nsxbackupcleaner

Additional Resources

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

KB
•
Download and Install VMware Fusion (2014097)

KB
•
几个网卡已关闭，出现错误 "[vmnicX：0x45021b04c000] 无法打开链接 (76656)

KB
•
由于 vCenter Server 部署期间 CEIP 设置不匹配，VMware Directory Service (VMDIRD) 进入不可恢复的状态 (76646)

Results 1-4 of 4

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware Cloud Foundation

Related Versions:

VMware Cloud Foundation 3.9.x

Take Our Survey

Support Assistant