Sun Storage 5210 NAS Appliance
 
Sun Storage 5310 NAS Appliance
 
Sun Storage 5310 NAS Gateway System
 

GCS>Sun Microsystems>Storage - Disk>Network Attached Storage
 

The first step in identifying the session/user that has marked the file
as "InUse" is to make note of the file name.  In this example, the file
in question is 'open_file.rtf'
Next, telnet to the 5210, 5310 or 5310c, log in as admin and identify
all open sessions/files using the cat command as shown in the following
example.
This command will produce a listing that contains ALL of the current
sessions (Windows PC's) accessing shares from the 5210 or 5310 as well
as user and file information per session sorted by session.
This information can then be used to identify which Windows PC client
is actually accessing the file that has been marked as "InUse"
Once the PC client has been indentified, you must go to that PC  and check to
see if the file is indeed in use on that pc. Close the file, log the users out and/or reboot the pc to clear the "InUse" condition
EXAMPLE:
========
5310NAS > cat proc/cifs/sessions
workers=4 sessions=2 users=4 trees=2 ofiles=3 req pool=2
(0x43AD1F0:10): ADMINPC1 [192.168.2.101] 11 1 Tue May  9 11:46:07 2006
shares=1
[0xD121000:78:1]: /v1g
users=2
NAS5310.acme.COM\nobody uid=1 cruid=0 (ref=6) Tue May 9 11:46:07 2006
NAS5310.acme.COM\Administrator uid=2 cruid=0 (ref=2) Tue May  9 11:46:07 2006
files=0
(0x43AD000:7): DATAPC1 [192.168.2.102] 11 1 Fri Apr 28 07:15:16 2006
shares=1
[0xD04F000:60:1]: /v1g
users=2
NAS5310.acme.COM\Administrator uid=1 cruid=0 (ref=6) Fri Apr 28 07:15:16 2006
NAS5310.acme.COM\nobody uid=2 cruid=0 (ref=10) Tue May 9 11:13:02 2006
files=3
fid=1748 (ref=1) . (ndref=4)
fid=1749 (ref=1) . (ndref=4)
fid=1759 (ref=1) open_file.rtf (ndref=1)
Now that we have the listing of active sessions, lets begin to
understand what we are looking at.
The first line contains several useful bits of information:
workers=4 sessions=2 users=4 trees=2 ofiles=3 req pool=2
sessions=2   ---> There are 2 Windows clients connected to the NAS
users=4      ---> There are 4 PC users accessing files on the NAS
ofiles=3     ---> These 4 users have a total of 3 open files
Next we identify the session information for each individual PC accessing
the 5210 or 5310. In this example, we have 2 sessions (Windows PCs with
mounted shares)
ADMINPC1 [192.168.2.101]
DATAPC1  [192.168.2.102]
Reviewing the session information for ADMINPC1, we see that a single share
named /v1g is mounted to this pc, there are 2 users, 'nobody'
and 'administrator' accessing this share and that these 2 users have no files open on the share:
(0x43AD1F0:10): ADMINPC1 [192.168.2.101] 11 1 Tue May  9 11:46:07 2006
shares=1
[0xD121000:78:1]: /v1g
users=2
NAS5310.acme.COM\nobody uid=1 cruid=0 (ref=6) Tue May 9 11:46:07 2006
NAS5310.acme.COM\Administrator uid=2 cruid=0 (ref=2) Tue May  9 11:46:07 2006
files=0
Reviewing the session information for DATAPC1, we see that the same single share
named /v1g is mounted to this pc, there are 2 users, 'nobody'
and 'administrator' accessing this share and that these 2 users have 3 files open on the share. Looking at the 3 files that are open, we see the file
'open_file.rtf' which is the file being reported as "InUse":
(0x43AD000:7): DATAPC1 [192.168.2.102] 11 1 Fri Apr 28 07:15:16 2006
shares=1
[0xD04F000:60:1]: /v1g
users=2
NAS5310.acme.COM\Administrator uid=1 cruid=0 (ref=6) Fri Apr 28 07:15:16 2006
NAS5310.acme.COM\nobody uid=2 cruid=0 (ref=10) Tue May 9 11:13:02 2006
files=3
fid=1748 (ref=1) . (ndref=4)
fid=1749 (ref=1) . (ndref=4)
fid=1759 (ref=1) open_file.rtf (ndref=1)
Now that we have identified the PC client that actually has the file
'open_file.rtf' listed as open, you must go to the pc DATAPC1 and check to
see if the file is indeed in use on that pc. It is possible that either
the administrator or nobody user is holding the file locked.  Close the
file, log the users out and/or reboot the pc to clear the "InUse" condition.
Note: Due to CR 6464379 (Read buffer limit of 64K on proc entries) the
output of the 'cat proc/cifs/sessions' command may be truncated
and, in this case, not all entries are displayed.

This solution has no attachment