6.4 fstab (nfs) mounts.

[Tristis Oris]

After last changes to mountpoints, is it any way to get native auto discovery for fstab, nfs\cifs paths? Without agent or OS modifications and custom scripts.

Added monitoring of mount point options for Unix-like OSes

vfs.fs.get and vfs.fs.discovery, used for discovery of mounted filesystems, now additionally return filesystem mount options in the "options" and "{#FSOPTIONS}" property respectively. These options allow to detect filesystems that remounted as read-only (e.g. on VMs) or to filter bind mounts or .dmg volumes on macOS.

[Tristis Oris]

yes, got it.
not that at macro tabs.

{$VFS.FS.FSTYPE.MATCHES} just need to add

|nfs|nfs3|nfs4|cifs|smb

[Tristis Oris]

Next step to check is folder mounted or not.

[cyber]

Next step to check is folder mounted or not.

If your discovery finds them, then they are mounted... both vfs.fs.get and vfs.fs.discovery return data about "mounted filesystems"...

[Tristis Oris]

not sure how to to make it.

need something like

find(/hostname/vfs.fs.get[{#FSNAME}],1,"like","failed")=0

but got

Incorrect item key "vfs.fs.get[{#FSNAME}]"

or that work only for trigger prototypes?


well, trigger doesn't matter right now. After any first umount, history for this item stop working.

from latest data:

Preprocessing failed for: [{"fsname":"/sys","fstype":"sysfs","bytes":{"total":0,"free":0,"used":0,"pfree":0,"pused":0},"ino...
1. Failed: cannot extract value from json by path "$.[?(@.fsname=='/mnt/kopia-backup/')].first()": no data matches the specified path

so with prototype

find(/kopia/vfs.fs.dependent[{#FSNAME},data],1,"like","Failed")=1

host trigger

 Cannot evaluate function find(/kopia/vfs.fs.dependent[/mnt/kopia-backup/,data],1,"like","Failed"): item is not supported.​

after umount.