The article explains how to determine if the file system on a client is supported for On Access Scanning in VSEL 1.9.x
 

1. Identify if a xen kernel is in use:
    
   1. Log on as root.
   2. Type the following command and press Enter:
      
       #uname -r
      
      If the output ends with .xen continue to step 2.
      
      If the output does not end with .xen, VSEL supports the file system mounted on the computer.
       
2. Identify if CONFIG_DEBUG_RODATA is set to y:
    
   1. Type the following command and press Enter:
      
      #grep CONFIG_DEBUG_RODATA /boot/config-`uname -r
       
   2. If the output contains the following entry, continue to step 3 to identify the file systems that are not supported by VSEL.
      
      CONFIG_DEBUG_RODATA=y
      
      If the output does not contain this entry, VSEL supports the mounted file system.
       
3. Identify the file system names that are not supported:
    
   1.  Log on as root.
   2. Type the following command and press Enter:
      
      #grep _FS=y /boot/config-`uname -r`
      
      This command lists the unsupported file systems on the computer.

IMPORTANT: On Access scanning does not work on unsupported file systems. But, if a file is copied from an unsupported file system to a supported file system, VSEL detects the infection when it is written to the supported file system.


File systems explicitly not supported:

File system	Notes
Microsoft Services for Network File System (NFS)	File Systems exported via Microsoft Services for NFS.
BTRFS	Not supported on remote file systems and root partition.
TMPFS	VSEL does not hook into this file system.