Issue: Scanning failure with an error of "file is on a different filesystem" for crossing filesystem boundaries in Linux Security 64 when running the manual scan using "fsanalyze" command Resolution: Basically, scanning for crossing filesystem boundaries (files on a different filesystem) is not allowed by default.Thus, manual scan using "fsanalyze" command may fail for certain files because they are on different mounted partitions/filesystems (for example, /dev and etc).Currently, scanning of files on different filesystems/partitions for manual scan will only happen when the exclusion setting (ods exclude_paths) is configured either using command-line utility tool (lsctl) or exclusion setting for manual scan is configured via Policy Manager, which is explained in the user guides below. In this case, the filesystem boundaries are crossed.https://help.f-secure.com/product.html#business/linux-security-64/latest/en/task_6FF3CD0A72924F32A5B43E2600529C51-latest-enRelated information:====================================================Note: The exclusions that are set in the current policy for manual scanning are applied when you use manual scanning from the command line.If you have excluded any paths in the manual scanning policy, recursive scanning crosses file system boundaries.====================================================When the exclusion setting is not configured, the reported message may appear thus you could consider to add any path to the exclusion setting of manual scan to solve it.