Forum: CFEngine Help
Subject: Anomoly in files changes => detect_content on NFS mounted data
Author: GFLehr
Link to topic: https://cfengine.com/forum/read.php?3,24414,24414#msg-24414
If I create an agent bundle like the one below where /data1 is the mount point
for an NFS volume (from a NetApp filer) I get "file or directory not found"
errors. This behavior changes if I match the directory contents explicitly with
a regex. Is this the expected results, and if so why?
bundle agent data_change_bundle
{
files:
"/data1" -> "data1"
changes => detect_content,
action => background,
depth_search => recurse("inf");
}
Results in messages like this:
cf3> Recurse was looking at
/data1/QLogic-Linux-SuperInstaller-20110930-3.tar when an error occurred:
cf3> !!! System error for lstat: "No such file or directory"
If I make a change to the directory specification so that "/data1" is now
/data1/.*" I get (mostly) the results I was hoping for.
bundle agent data_change_bundle
{
files:
"/data1/.*" -> "data1"
changes => detect_content,
action => background,
depth_search => recurse("inf");
}
Results in messages like these:
cf3> -> Handling file existence constraints on
/data1/backup/Edgecraft/chef_rec_texmex.html
cf3> -> File hash for /data1/backup/Edgecraft/chef_rec_texmex.html is
correct
cf3> -> File permissions on /data1/backup/Edgecraft/chef_rec_texmex.html as
promised
Additional observations:
1 - Cf3 seems to be checking the perms on each file even though I have not
asked it to by using detect_content.
2 - The depth_search also descends into the .snapshot directories which I was
hoping to avoid based on "Depth searches (recursion) during searches" section
of the Cf3 reference. What is the most efficient way to exclude these from
searches?
Thanks,
Gary F Lehr
_______________________________________________
Help-cfengine mailing list
[email protected]
https://cfengine.org/mailman/listinfo/help-cfengine
