ISILON SMB - file in Use error

users behind firewall ? As far as disconnecting users from a file:

isi smb file list

and

isi smb file close --file-id #

Try this post from MS (Especially Registry keys): The Definitive 'Locked File' Post (updated 6/28/2012) - The Microsoft Excel Support Team Blog - Site Home - TechNet Blog…

i logged into that specific node and killed the open session.. Question how to find under which user this file is in locked state but still this is a misleading message bec no one else opened that file while its in lock state

isi smb openfiles close 7932

Oh got this ...

nas4# isi_for_array isi smb openfiles list | grep -i prodfile

uspnas4: 7932  C:\onefs\ifs\xxx\prodfile

how to kill this ? below doesn't work so i have to use isi_for_xxx  or how should i know on which node the file is open in above  cmd that way i login to that node and kill it

isi smb file close --file-id 7932

next time try this:  isi_for_array "isi smb file list" | grep -A1 filename

this should display username as well.

when i use the quotes for "isi smb file list" its giving me bad command error

nas4# isi_for_array "isi smb file list" | grep -A1 prodfile

nas4: bad subcommand file

nas4# isi_for_array "isi smb file list"

nas4: bad subcommand file

nas4: bad subcommand file

nas4: bad subcommand file

I believe the syntax is either:

1. isi smb openfiles or # isi smb session

Isilon OneFS v7.0.1.4

haisilon-1# isi smb openfiles

log-level openfiles sessions settings shares

1. isi smb sessions list --

--format -- Display smb sessions in the given format

--limit -- Number of smb sessions to display.

--no-footer -- Do not display table summary footer information.

--no-header -- Do not display headers in CSV or table formats.

--verbose -- Display more detailed information.

i am on 6.5.5.12 so the syntax probably changed in 7.x

looks like it changed. i tried yestarday cmd with --verbose option its telling us the user who locked it cool ...thanks all

isi_for_array isi smb openfiles list --verbose

Contact support and ask about "patch-101597". Issue is solved in 7.0.1.5 but for any below you can use this patch.

SUMMARY

This patch addresses the issue where one user closes an Excel file and a

different user will not be able to open the file because the file is still

opened by the first user. This problem persists after the Microsoft KB 942146

has been appiled to the client.  http://support.microsoft.com/kb/942146

(Windows XP KB 812937 http://support.microsoft.com/kb/942146)

RESOLVED ISSUES

* Race condition where a file close and an oplock break response was causing

  the software to sometimes miss closing a file.  This seems to happen

mostly with Excel file closes.

CHANGED FILES

* /usr/likewise/lib/lwio-driver/srv.so

  (MD5 = 9db346b3eab63f66cb8640c79db6d9c5)

Soetingr,

thank you for the very useful info and thats what i am looking for . i heard 7.0.1.6 is coming this week end or next week  is that true ?? if so i go for it rather doing 2 upgrades.

From my information 7.0.2 is coming out in 7 days. I would suggest you wait for that release.

will do thank you for the info.