How to troubleshoot BoostFS Mount Offline issues for both Windows and Linux platforms

Summary: This KB explains the steps to troubleshoot an unexpected BoostFS mount going offline issue.

This article applies to This article does not apply to This article is not tied to any specific product. Not all product versions are identified in this article.

Instructions

In General, BoostFS runs in process level and stays running in the background while Boostfs Mount is mapped on both windows and linux platforms.

In certain cases, due to an unexpected issue, the process may get killed.

If the customer has not already recovered from the situation described above and needs assistance in restoring connectivity. Review the last command used in the following logs to manually start the process. 
 

Linux: /opt/emc/boostfs/log/boostfs_command.log


 

Windows : C:/BoostFS/Log/boostfs_commands.log

 

Logs to Collect:


1.Boostfs logs from directory path. 

/opt/emc/boostfs/log/ for Linux
 
C:/BoostFS/Log/ for Windows


2. Support Bundle from the Data Domain where the BoostFS mounts are associated with.

3. Application Logs around the time of the failure when the mount would have gone offline.

4, Core Files related to the incident if the core dump-logging facility is enabled. If not enabled, please refer to steps below that can be used to configure the setting.

Core Files Generally are located in.

/opt/emc/boostfs or /var/lib/systemd/coredump for Linux
C:\BoostFS directory for Windows installs
 
Note:  If BoostFS core file logging is disabled, enable it using the steps below to capture core files in case unexpected mount issues occur again.

For Linux:


Check the limits of ulimit for core using the following:
 

#ulimit -c


Ensure the value isn’t zero; if it returns 0 bytes, allocate space by setting size to unlimited or negotiate an appropriate size with the the customer.

In general core files for BoostFS are 2 GB or less and so setting it to unlimited should not hurt but please check with a customer.

#ulimit -c unlimited

 

For Windows:

1. Using `regedit` on the Windows BoostFS client system, look for the following Registry entry:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Windows Error Reporting\LocalDumps\boostfs.exe

 

2. The above Registry entry would have default parameters like the following:

DumpCount = 1

DumpFolder = "C:\BoostFS\

DumpType = 2

3. In the above BoostFS registry parameters, modify the value of "DumpCount" to a value of 10 (using Base as Decimal)

Doing this would prevent any BoostFS dump from overwriting previous dumps and there can be a maximum 10 BoostFS dump files created under folder "C:\BoostFS."
 





 

Affected Products

Data Domain Boost – File System
Article Properties
Article Number: 000198363
Article Type: How To
Last Modified: 09 يناير 2026
Version:  3
Find answers to your questions from other Dell users
Support Services
Check if your device is covered by Support Services.