SaunaFS Integration with logging tool via NFS Ganesha bad behavior - empty buckets creation

[Michprac]

Overview

We attempted to integrate SaunaFS as an archive solution with the logging tool using the NFS Ganesha Client. However, we encountered several issues that led us to abandon SaunaFS in favor of a traditional storage solution.

Issues Identified

1. Capacity Mismatch

   • The capacity values displayed in the CGI interface differed from those shown in the terminal.

2. Mounting Failure

   • The SaunaFS storage did not mount automatically to the logging tool when using the mount command.

3. Behavior at Full Capacity

   • Once SaunaFS reached full capacity, logging tool continued to write empty buckets instead of ceasing logging operations.

Alternative Solution Implemented

Due to these issues, we opted to use a traditional storage approach by deploying a VM and utilizing NFS Ganesha (FSAL_VFS) to export a VFS-based filesystem. Instead of exporting SaunaFS, we exported a local folder via NFS Ganesha.

Results of Alternative Solution

1. Logging tool correctly stopped writing logs when storage reached full capacity (no empty buckets were written).
2. The storage mounted automatically when using the mount command.
3. Capacity values were accurately reflected.

Conclusion

The alternative solution resolved all issues we encountered with SaunaFS. To consider SaunaFS in the future, the following improvements would be necessary:

• Ensure consistency in capacity reporting between CGI and terminal.
• Implement correct behavior when storage reaches full capacity, preventing unnecessary writes of empty buckets.

[uristdwarf]

What was the filesystem you used for the local folder you exported through NFS Ganesha?

[Michprac]

The filesystem used for the local folder exported through NFS Ganesha was ext4.