7020997: Filr Appliance – Out of disk space

This document (7020997) is provided subject to the disclaimer at the end of this document.


Novell Filr 3.1 Appliance

Novell Filr 3.1 Administration


Various problems can result from running out of disk space on the Filr Appliance, such as:

1. When attempting to access the appliance via port 9443 or 8443:
Error: HTTP Status 500
2. When attempting to view the details of a file, or preview a file:
Error: I/O error: Could not create directory [/vastorage/filr/cachefilestore/converted_html_files/kablink/<additional path to file>


The Filr service is stopped automatically if disk usage on the root drive goes above 90%. When this happens, /var/log/messages contains an entry about this.

Identify the disk space configuration and usage

Check storage using the command

df -m


df -h

Check inodes using the command

df -i

Expand the disk space available

NOTE: Ensure that you have a reliable backup before proceeding, as errors occurring when the disk is expanded can render the system unusable.

Important: The boot partition cannot be expanded.
To expand the storage space allocated for the /vastorage and /var partitions, do the following:
Use the tools provided by your virtualization platform vendor to expand the virtual disks that contain the partitions your are expanding.
Once you can again gain access to the Filr port 9443 Appliance Console, use the Appliance Configuration “Storage” tool to expand the partition(s) as needed. When expanding the disk from Filr port 9443 Appliance Console, please make sure all terminals to appliance are closed (including VMWare console).
Another method is to delete files directly from a terminal session on the Filr Appliance. This can be useful for deleting large log files, etc.
To view the largest 10 files on the device, use this command:
find /var -printf ‘%s %pn’| sort -nr | head -10
To view all files in ascending order of size, use this command:
find . -type f -exec du -h {} + | sort -h


Insufficient disk space can be caused by enabling “Content Indexing” at the Net Folder Server level when creating a Net Folder Server (Port 8443 Filr Admin Console > Management > Net Folder Servers). Context Indexing indexes any text within all files in order to be able to search within the content of files. This process involves writing temporary files on the Filr appliance, which get cleaned up about once a day. This can cause the disk to become full, resulting a failure of the Filr server before it has a chance to clean up the temporary files.

For this reason, the Filr Administrative User Interface Reference (8.1.2 Creating a Net Folder Server) states:
IMPORTANT: Enabling indexing at the Net Folder Server level is notusually a best practice. Rather, indexing should be confined to NetFolders. This is why disk space planning on the Planning Worksheets isdone at the Net Folder level.A possible exception to this rule is enabling content indexing of HomeNet Folder Servers.

Additional Information

If excessive Net Folder indexing results in running out of iNodes (as displayed by “df -i”), you can delete the files under /vastorage/filr/cachefilestore/kablink/ (but not the kablink directory itself), which should temporarily resolve the problem. Disabling the file indexing (or reducing indexing by limiting it to smaller Net Folders) may prevent a recurrence.


This Support Knowledgebase provides a valuable tool for NetIQ/Novell/SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented “AS IS” WITHOUT WARRANTY OF ANY KIND.


Leave a Reply