Data Domain: BoostFS plugin world-writable files
Summary: A BoostFS mount operation may create the /tmp/Boost_D4_Event.log file due to initialization of integrated DDBoost D4 libraries. On affected releases, the file may be created with world-writable permissions; this behavior has been corrected in later BoostFS releases that apply more restrictive permissions and automatically update existing files during installation or upgrade. ...
Symptoms
After a BoostFS mount operation, the file /tmp/Boost_D4_Event.log may be present on Linux clients.
The file may be observed with world-writable permissions.
The behavior may occur on only a subset of BoostFS clients, even when running the same BoostFS version.
The file is typically created during BoostFS initialization and mount activities.
Cause
BoostFS integrates with DDBoost D4 libraries during the build process.
During initialization of the DDBoost client library (ddp_init), the /tmp/Boost_D4_Event.log file may be created.
The behavior is associated with DDBoost library initialization and does not indicate a failure of the BoostFS mount operation.
D4 library integration is required for certain BoostFS workflows and therefore could not be removed as part of the fix.
Resolution
Upgrade BoostFS to a release containing the fix:
BOOSTFS-7.13.1.80 or later
BOOSTFS-8.3.1.40 or later
BOOSTFS-8.6.1.20 or later
The fix provides the following improvements:
The DDBoost client no longer creates the file with world-writable permissions.
The BoostFS installation and upgrade process detects an existing /tmp/Boost_D4_Event.log file and automatically updates its permissions to a more restrictive setting.
The fix applies to RHEL- and Debian-based Linux installations.
No action is required for Windows installations, as this behavior has not been observed on BoostFS for Windows.
Additional Information
Frequently Asked Questions
Why do only some clients show the Boost_D4_Event.log file?
The file is created during initialization of the DDBoost client libraries as part of a BoostFS mount operation. Depending on workload, usage patterns, and whether the initialization event occurs, some systems may create the file while others do not, even when running the same BoostFS version.
Can the log file be prevented from being created on affected releases?
Engineering does not recommend modifying or replacing DDBoost libraries after installation. The recommended solution is to upgrade to a BoostFS release that contains the fix.
Is this related to a BoostFS mount failure?
No. The presence of the file is a byproduct of DDBoost library initialization and does not indicate a mount failure or operational problem with BoostFS.
Why wasn't D4 library integration removed to resolve the issue?
D4 library integration supports additional BoostFS functionality and workflows, including features used by certain authentication and client operations. Because of these dependencies, the fix focused on correcting the file permissions behavior rather than removing the integration.
Which operating systems are affected?
The behavior has been observed on Linux-based BoostFS installations. The fix applies to RHEL- and Debian-based Linux clients. Windows installations are not affected.
Does the Boost_D4_Event.log file impact BoostFS functionality?
No. The file is created during DDBoost client library initialization and does not affect normal BoostFS operation.
What should customers do?
Customers who observe the /tmp/Boost_D4_Event.log file should upgrade to BOOSTFS-7.13.1.80, BOOSTFS-8.3.1.40, BOOSTFS-8.6.1.20, or any later supported release that includes the fix.
/tmp/Boost_D4_Event.log is associated with DDBoost library initialization during BoostFS operations and does not impact normal BoostFS functionality. Upgrading to a fixed BoostFS release is the recommended resolution.