Network and Storage Protocols
Network and Storage Protocols
stumbled on a hidden file lock today. oplocks are set to On on the FAS2050, Ontap version 7.3.1.1
In windows server management console, file doesn't list as open for reading or writing. In filer console, locks status at the filer or folder level don't show a lock on the file, as in:
Prolific> lock status -f /vol/projects/00001ma-pm
No locks
but if i check at the file level,
Prolific> lock status -f /vol/projects/00001ma-pm/file.xlsx
========013e0239:01038182
CIFS path=\00001ma-pm\Morphpm-global.xlsx(/vol/projects/00001ma-pm/file.xlsx) host=x.x.x.x() owner=user state=GRANTED mode=RdWr-denyW oplock=None
CIFS path=\00001ma-pm\Morphpm-global.xlsx(/vol/projects/00001ma-pm/file.xlsx) host=x.x.x.x() owner=user pid=65279 offset=2147483539 len=1 excl=yes state=GRANTED
CIFS path=\00001ma-pm\Morphpm-global.xlsx(/vol/projects/00001ma-pm/file.xlsx) host=x.x.x.x() owner=user pid=65279 offset=2147483539 len=1 excl=yes state=GWAITING
CIFS path=\00001ma-pm\Morphpm-global.xlsx(/vol/projects/00001ma-pm/file.xlsx) host=x.x.x.x() owner=user pid=65279 offset=2147483559 len=1 excl=yes state=GRANTED
CIFS path=\00001ma-pm\Morphpm-global.xlsx(/vol/projects/00001ma-pm/file.xlsx) host=x.x.x.x() owner=user pid=65279 offset=2147483599 len=1 excl=yes state=GRANTED
to break the lock, i used
Prolific> lock break -f /vol/projects/00001ma-pm/file.xlsx
just wanted to share this because i couldn't find any pointers to this on the supprot or community site, and support couldn't find any documentation on it, and from a little googling, sounds like this might happen often with office2007.
Marty Doscher
Hi,
we are having a similar issues with Ontap 7.2.6.1 and Windows7/Office 2007, 5 cases in the last days.
Only way is to remove the lock with the "lock break -f file -p cifs" command
filer*> lock status -f "/vol/vol0/file.xls"
========0bced388:01332237
CIFS path=\vol\vol0\file.xls(/vol/vol0/file.xls) host=x.x.x.x() owner=user state=GRANTED mode=RdWr-denyW oplock=None type=waiting sharelock (llp=0x000000010ee915d8 fcb=0x000000007e4ac038 tree=0x000000015ff220d8)
CIFS path=\vol0\file.xls(/vol/vol0/.xls) host=x.x.x.x() owner=user pid=65279 offset=2147483539 len=1 excl=yes state=GRANTED type=excl covered recl-ok bytelock (llp=0x000000007c031398 fcb=0x000000007e4ac038 tree=0x000000015ff220d8)
CIFS path=\vol0\file.xls(/vol/vol0/file.xls) host=x.x.x.x() owner=user pid=65279 offset=2147483539 len=1 excl=yes state=GWAITING type=excl covered recl-ok bytelock (llp=0x00000001368dc4b8 fcb=0x000000007e4ac038 tree=0x000000015ff220d8)
CIFS path=\ vol0\file.xls(/vol/vol0/file.xls) host=x.x.x.x() owner=user pid=65279 offset=2147483559 len=1 excl=yes state=GRANTED type=excl covered recl-ok bytelock (llp=0x000000007686a278 fcb=0x000000007e4ac038 tree=0x000000015ff220d8)
CIFS path=\ vol0\file.xls(/vol/vol0/file.xls) host=x.x.x.x() owner=user pid=65279 offset=2147483599 len=1 excl=yes state=GRANTED type=excl covered recl-ok bytelock (llp=0x000000007cf434b8 fcb=0x000000007e4ac038 tree=0x000000015ff220d8)
Does anybody has similar experience and maybe a solution for this issues?
Best Regards,
Klaus
Hi,
we are having a very similar issues with Ontap 7.3.2P3 and Windows7/Office 2007.
Only way is to remove the lock with the "lock break" command.
filer> lock status -f
[....]
========d507d4e0:00d5131f
CIFS path=\....\CAUTION.doc(/vol/....../CAUTION.doc) host=x.x.x.x() owner=user1 state=GRANTED mode=RdWr-denyW oplock=None
CIFS path=\...\CAUTION.doc(/vol/...../CAUTION.doc) host=x.x.x.x() owner=user1 pid=65279 offset=2147483539 len=1 excl=yes state=GRANTED
CIFS path=\...\CAUTION.doc(/vol/...../CAUTION.doc) host=x.x.x.x() owner=user1 pid=65279 offset=2147483539 len=1 excl=yes state=GWAITING
CIFS path=\...\CAUTION.doc(/vol/...../CAUTION.doc) host=x.x.x.x() owner=user1 pid=65279 offset=2147483559 len=1 excl=yes state=GRANTED
CIFS path=\...\CAUTION.doc(/vol/....../CAUTION.doc) host=x.x.x.x() owner=user1 pid=65279 offset=2147483599 len=1 excl=yes state=GRANTED
[....]
========d507d4e0:00231a32
CIFS path=\.......\Cde_station_2010.xls(/vol/...../Cde_station_2010.xls) host=y.y.y.y() owner=user2 state=GRANTED mode=RdWr-denyW oplock=None
CIFS path=\.......\Cde_station_2010.xls(/vol/...../Cde_station_2010.xls) host=y.y.y.y() owner=user2 pid=65279 offset=2147483539 len=1 excl=yes state=GRANTED
CIFS path=\.......\Cde_station_2010.xls(/vol/...../Cde_station_2010.xls) host=y.y.y.y() owner=user2 pid=65279 offset=2147483539 len=1 excl=yes state=GWAITING
CIFS path=\.......\Cde_station_2010.xls(/vol/...../Cde_station_2010.xls) host=y.y.y.y() owner=user2 pid=65279 offset=2147483559 len=1 excl=yes state=GRANTED
CIFS path=\.......\Cde_station_2010.xls(/vol/...../Cde_station_2010.xls) host=y.y.y.y() owner=user2 pid=65279 offset=2147483599 len=1 excl=yes state=GRANTED
[......]
filer>
At this time we don't find any solution for this issue.
Pierrick
Hi,
as i have seen a fix to this issue should be out now in 7.3.2P6 (BUG: 374232)
http://now.netapp.com/NOW/download/software/ontap/7.3.2P6/
still untested from my side because we need to wait for the next scheduled downtime,
but if you get positive results with this release please give feedback
Best Regards,
Klaus
Thank for your answer.
I open a case with NetApp support. They directed me to the same bug (374232).
We will install release 7.3.2P6 on our filer in the days to come.
Sorry for my poor english (thank to Google).
Hi,
I am seeing the same issue. Did the bug fix resolve it? Is there anyway of reporducing the issue from say excel 2007 on the fly? I'd imagine a shared workbook on excel 2007 uses byte range locks?
We have recently upgraded Ontap from 7.3.2 P2 to & 7.3.5.1 P5 which fixed the excel file locking issues.