- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Re: SAMBA/CIFS issue
Operating System - OpenVMS
1753428
Members
4864
Online
108793
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-23-2010 12:57 PM
05-23-2010 12:57 PM
Re: SAMBA/CIFS issue
Tim, Ross,
Clash of world views... *ix vs VMS?
I don't have a SAMBA/CIFS system to test, but something that might help, depending on how the files are written.
When a file is created, the creation date is written, and the modification date set the same. On closing the file, the modification date is updated.
So, one way you may be able to find when those 0 block files are complete, is to check that RDT > CDT. Lots of caveats, but it's easy to check, and may be sufficiently accurate for your purposes.
Clash of world views... *ix vs VMS?
I don't have a SAMBA/CIFS system to test, but something that might help, depending on how the files are written.
When a file is created, the creation date is written, and the modification date set the same. On closing the file, the modification date is updated.
So, one way you may be able to find when those 0 block files are complete, is to check that RDT > CDT. Lots of caveats, but it's easy to check, and may be sufficiently accurate for your purposes.
A crucible of informative mistakes
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-24-2010 04:01 AM
05-24-2010 04:01 AM
Re: SAMBA/CIFS issue
Hi,
Just did a little test, copying a large zip file to a share on a CIFS v1.1 eco1 ps010 server and then tried to delete/unzip/open for read, the zip file using DCL commands and each attempt produced the expected "file currently locked by another user" error.
If your file is large enough, you can see the lock and sharing modes the client is using by doing $ SMBSTATUS during the copy operation (use "$ smbstatus --locks" to see just the lock info).
There are some smb.conf parameters which affect data buffering such as "strict sync" and "sync always".
Also, a new parameter "vms file flush" was added in v1.1 eco1 ps008. It will cause CIFS to flush the file buffers to disk if/when a client sends an SMB Flush request.
You may need to get a network trace and look at the NT Create AndX SMB request to see what locking and share modes are being requested.
On the other hand, as Volker pointed out, we do try to retain Advanced Server behavior as much as possible (if the Advanced Server behavior is deemed appropriate). Thus, if there's not an option in CIFS to replicate that behavior, an new parameter is usually added to enable the desired behavior.
OPLOCKS aren't a locking mechanism, so don't recommend changing OPLOCK related smb.conf parameters.
HTH,
Paul
Just did a little test, copying a large zip file to a share on a CIFS v1.1 eco1 ps010 server and then tried to delete/unzip/open for read, the zip file using DCL commands and each attempt produced the expected "file currently locked by another user" error.
If your file is large enough, you can see the lock and sharing modes the client is using by doing $ SMBSTATUS during the copy operation (use "$ smbstatus --locks" to see just the lock info).
There are some smb.conf parameters which affect data buffering such as "strict sync" and "sync always".
Also, a new parameter "vms file flush" was added in v1.1 eco1 ps008. It will cause CIFS to flush the file buffers to disk if/when a client sends an SMB Flush request.
You may need to get a network trace and look at the NT Create AndX SMB request to see what locking and share modes are being requested.
On the other hand, as Volker pointed out, we do try to retain Advanced Server behavior as much as possible (if the Advanced Server behavior is deemed appropriate). Thus, if there's not an option in CIFS to replicate that behavior, an new parameter is usually added to enable the desired behavior.
OPLOCKS aren't a locking mechanism, so don't recommend changing OPLOCK related smb.conf parameters.
HTH,
Paul
- « Previous
-
- 1
- 2
- Next »
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP