today I am wondering about the CLI output of the 'isi smb sessions list' and 'isi smb openfiles list' commands on OneFS 184.108.40.206.
Although there are some open SMB connections with Windows clients copying files to/from the cluster, the list of open files or open sessions is always empty.
I made some further investigation to that topic. It seems that these commands are only related to the System Zone, not to all other Access Zones. When I have mounted the cluster through the System Zone I can see the SMB session and open files. But when I mount the cluster through another than the System Zone I cannot see SMB session or open files.
Does anyone figured out the same issue?
> But when I mount the cluster through another than the System Zone I cannot see SMB session or open files.
Any chance those mounts landed on a different node, and
the isi smb sessions and openfiles commands are just local to
the node where issued?
I also have this problem on 220.127.116.11 and now 18.104.22.168.
No files are displayed via the CLI. Using the MMC plugin only shows the file opened on the node to show open files.
One reason I could think of this happening is that it is only showing the default zone, System. So in isi smb sessions list, I can see a couple sessions that are opened in the System zone, but none in the other zones. However, you can't specify zone in isi smb openfiles or sessions commands.
Workaround provided by support until they can fix the non-zone-aware nature of isi smb.
isi_run -z 2 isi_classic smb file list | less
(2 is the relevant zone in our case, pipe to less to give you chance to read the output)
Or for searching across the cluster:
isi_for_array 'isi_run -z 2 isi_classic smb file list | grep partoffilename'
As I don't see a --zone flag on the command, I would not expect it to be zone aware. It is tied to the local node and, as was states earlier, isi_for_array is a way around that on the CLI.
Has anyone gotten a fix for this yet? The isi_for_array 'isi_classic -z <zoneIDforSMB> smb file list| grep <filename>' command doesn't list the ID so there is no way to close the file if you find it.
Running it without grep gives you file IDs but that will list everything which is also not helpful.
I found another solution to this issue.
I was able to access each node from Computer Management on a Windows system using the IP we assigned it for the SMB access zone. From there I was able to look at open files on that node and close them if needed.
you can use the "B" option on grep to show the line(s) before the match.
isi_for_array 'isi_classic -z <zoneIDforSMB> smb file list | grep <filename> -B1' shows you the path of the file an the ID.
if you want to see who is using the file you can also add the -A1 (after) option to the the lines after the match.
The number behind the option defines the number of lines to show.
If you upgrade to 22.214.171.124, the isi smb openfilles and isi smb sessions command will show all zones like they did prior to 8.x. This was a bug. At some point a --zone flag may be added, but this is the short-term fix to get the command working again.