files_fs

The files_fs process creates and services the /files filesystem. The “/ files” file system provides a file-level view of the disk images in the “/export” file system

Unlike /export, which is exported via NFS/CIFS, /files is only exported via CIFS. It allows for file-level backup of VM files from other hosts (backup clients).

The files_fs process reads all of its data from /export filesystem and as such is a client process to vm_proxy_fs.

The “/files” area displays a “.volume” directory for each disk image in “/export”. So, for example a disk image called “xxx.vmdk” in “/export” will result in a corresponding “xxx.volume” directory in the “/files” area.

Whenever a “.volume” file is opened, the file-level view of the volume is mounted, and the partitions and files will appear as directories under the .volume directory. Once this mount is completed, all of the files on the volume can be listed and read.

Like “/export” filesystem “/files” is a read-only file system, and files cannot be written or modified in this filesystem.  The mount process is automatic, and is initiated whenever a “.volume” directory is opened. The file-level view is automatically un-mounted after several minutes of inactivity.

As with other vmPRO file systems, this one is also FUSE-based.

Troubleshooting

All files_fs process log entries are written to /var/log/files_fs. The daemon writes debug output to this file, when so enabled. Setting the registry key appliance.debug.level to a small positive integer will enable general debug output, which increases in verbosity with a higher value. Note that setting these keys can result in significant log output.

Process Communication Flow

/export     ->    files_fs daemon           ->    /files           ->   CIFS

-------          ----------------                ------

xxx.vmdk    ->    “mount” file-level view   ->    xxx.volume (file-level view) -> CIFS

What's Next?

 ls_bitmap_fs >