Having an issue I've had a long time ago; looks like it came back with 9.11.1 or 9.12.1; I have a Unix volume with a CIFS share, which use to collect metadata from. It stopped working. When I manually try a "dir /s" command, it shows the root of the volume but refused to traverse the directories. Anyone have any ideas?
#Dir "/s" will not traverse root directory of UNIX backed CIFS share
graceful nexus
hearty rampart
do you have actual permissions to enter the subdirectories? Do you see the subdirectories? There is an option that hides directories that you have no access rights to
sinful marsh
@graceful nexus what he said ^^^
If it’s a junction path you will need permissions. If you have ABE enabled you only see what you have permission to see
gaunt trellis
Looks like OP needs to do some Unix to Windows user mapping, if not done already. Assuming the "unix volume" is created with unix security style, windows user needs to be mapped to the unix user to get access
hearty rampart
If it’s a junction path you will need permissions. If you have ABE enabled you o...
ABE is for hiding shares themselves, there's another feature that hides folders inside shares. Or vice versa. I always mix those two up 😄
sinful marsh
Access based enumeration. Shows you what you’re eligible to access
Hides other stuff that your not allowed
sinful marsh
For shares, yes.
graceful nexus
No, I see everything. I can '
Cont'd, sorry; I can traverse to a subdirectory with 'CD' and then "dir /s" and see everything. I am connecting as root as well. It is only at the top level, 'dir /s' will not traverse from the top level, almost as if it thinks they are hard links. I remember having this issue a long time ago, but can't remember the resolution
hearty rampart
what's the optionvserver cifs options show -fields is-use-junctions-as-reparse-points-enabled (in advanced privilege mode) set to?
swift shadow
ABE is for hiding shares themselves, there's another feature that hides folders ...
Mixed up
swift shadow
Cont'd, sorry; I can traverse to a subdirectory with 'CD' and then "dir /s" and...
There are various options on how to handle or follow symlinks.
oak ingot
I have not seen this behavior that I can recall. I am not able to find anything when searching for the symptom, and I cannot reproduce the issue with the description provided. It may help to capture a packet trace to see what is being returned to the client, and possibly compare that to a trace from a "working" system, if necessary. Let me know if you create a Support case.