WO1999030254A1 - Multi-protocol unified file-locking - Google Patents
Multi-protocol unified file-locking Download PDFInfo
- Publication number
- WO1999030254A1 WO1999030254A1 PCT/US1998/025388 US9825388W WO9930254A1 WO 1999030254 A1 WO1999030254 A1 WO 1999030254A1 US 9825388 W US9825388 W US 9825388W WO 9930254 A1 WO9930254 A1 WO 9930254A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- file
- protocol
- message
- lock
- client device
- Prior art date
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/10—File systems; File servers
- G06F16/17—Details of further file system functions
- G06F16/176—Support for shared access to files; File sharing support
- G06F16/1767—Concurrency control, e.g. optimistic or pessimistic approaches
- G06F16/1774—Locking methods, e.g. locking methods for file systems allowing shared and concurrent access to files
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y10—TECHNICAL SUBJECTS COVERED BY FORMER USPC
- Y10S—TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y10S707/00—Data processing: database and file management or data structures
- Y10S707/99931—Database or file accessing
Definitions
- the invention relates to locking in a multi-protocol file server.
- One known method is to provide a network file server for storing files, capable of receiving and responding to file server requests from those client devices. These file server requests are made using a file server protocol, which is recognized and adhered to by both the file server and the client device. Because the files are stored at the file server, multiple client devices have the opportunity to share simultaneous access to files.
- one protocol commonly used for devices using the Unix operating system is the NFS ("Network File System") protocol.
- Devices using the Windows operating system can also use the NFS protocol by means of the "PC NFS" implementation.
- the NFS protocol is designed to be stateless, and so does not provide any semantics for files to be locked against sharing or otherwise restricted to a single client device.
- one protocol commonly used for devices using the Windows operating system is the CIFS ("Common Internet File System”) protocol.
- the CIFS protocol has an extensive mandatory file-locking semantics, which CIFS client devices rely on and expect to be adhered to.
- NFS protocol has been augmented with an adjunct file- locking protocol, NLM ("Network Lock Manager”), but the NFS protocol treats NLM locks as merely advisory. While this method achieves the purpose of providing file-locking semantics to those NFS applications that use it, it does not prevent NFS applications from ignoring those file- locking semantics, nor does it allow client devices to rely on the file-locking semantics of multiple diverse file server protocols.
- NLM Network Lock Manager
- the invention provides a method and system for correct interoperation of multiple diverse file server protocols.
- a file server recognizing multiple diverse file server protocols provides a uniform multi-protocol lock management system (including a uniform file- locking semantics), which it enforces for all client devices and all recognized file server protocols.
- a first file server protocol such as CIFS
- CIFS mandatory file-open and file-locking semantics together with an opportunistic file-locking technique
- a second file server protocol such as NFS, together with an adjunct protocol NLM
- NLM adjunct protocol
- the uniform file-locking semantics provides that the file server determines, before allowing any client device to read or write data, or to obtain a new file lock or byte-range lock, whether that would be inconsistent with existing locks, regardless of originating client device and regardless of originating file server protocol or file-locking protocol for those existing locks.
- the file server performs this check when the client device opens the file.
- the file server performs this check when the client device requests the byte-range lock.
- the file server performs this check when the client device actually issues the read or write request, or when the NFS client device requests an NLM byte-range lock indicating intent to read or write that byte range. Enforcing file- locking semantics protects file data against corruption by NFS client devices.
- a CIFS client device upon opening a file, can obtain an "oplock" (opportunistic lock), an exclusive file lock that permits only that one client to read or write the file.
- oplock opportunistic lock
- the file server sends an oplock-break message to the CIFS client device, giving the CIFS client device the opportunity to flush any cached write operations and possibly close the file. Allowing NFS and NLM requests to break oplocks ensures that file data remains available to NFS client devices simultaneously with protecting integrity of that file data.
- a CIFS client device can obtain a "change- monitoring" lock for a directory in the file system, so as to be notified by the file server whenever there is a change to that directory.
- Changes to a directory include creating, deleting or renaming files within that directory, or moving files into or out of that directory.
- the file server notes changes to the directory by both CIFS client devices and non-CIFS client devices, and notifies those CIFS client devices with "change-monitoring" locks of those changes.
- Figure 1 shows a first block diagram of a system including a multi-protocol file server.
- Figure 2 shows a second block diagram of a system including a multi-protocol file server.
- Figure 3 shows a process flow diagram of a method of operating a multi-protocol file server.
- Figure 4 shows a process flow diagram of a method of operating a cross-protocol lock manager in a multi-protocol file server.
- Figure 5 shows a process flow diagram of a method of operating an oplock manager in a multi-protocol file server.
- Figure 6 shows a process flow diagram of a method of operating a change-notify manager in a multi-protocol file server.
- Figure 1 shows a first block diagram of a system including a multi-protocol file server.
- a system 100 includes a file server 1 10, a computer network 120, and a plurality of client devices 130.
- the file server 1 10 includes a processor 111 and mass storage 112.
- the mass storage 112 is capable of storing and retrieving a set of files 113 having data for storage and retrieval.
- the processor 1 11 is capable of receiving a sequence of request messages 121 from the network 120, parsing those messages as commands and data, and manipulating the files 113 on the mass storage 112, and sending response messages, in response to those commands and data.
- the file server 110 and the client devices 130 are coupled to the network 120 and communicate using messages 121 transmitted on the network 120.
- the messages 121 include file system requests transmitted by the client devices 130 to the file server 110 and file system responses transmitted by the file server 110 to the client devices 130.
- Figure 2 shows a second block diagram of a system including a multi-protocol file server.
- the system 100 includes the set of client devices 130, including Unix client devices 201, PC NFS Windows client devices 202. and CIFS Windows client devices 203.
- Unix client devices 201 execute the Unix operating system and use the Unix/NFS file server protocol.
- PC NFS Windows client devices 202 execute the Windows operating system and use the PC NFS file server protocol.
- CIFS Windows client devices 203 execute the Windows operating system and use the CIFS file server protocol.
- Unix client devices 201 and PC NFS Windows client devices 202 communicate with the file server 110 using the NFS file server protocol, which is recognized at the file server 110 by an NFS file server protocol parser 211.
- CIFS Windows client devices 203 communicate with the file server 110 using the CIFS file server protocol, which is recognized at the file server 110 by a CIFS file server protocol parser 212. Messages using either the NFS file server protocol or the CIFS file server protocol are parsed by the processor 111 and processed by an oplock manager 220.
- the oplock manager 220 manages access to files 113 having CIFS oplocks. Its operation is described in further detail with regard to figure 3 and figure 5.
- the oplock manager element 220 is coupled to a cross-protocol lock manager 230.
- the cross-protocol lock manager 230 manages the file-locking semantics of the file server 110. It processes and records infoimation regarding four types of locks — CIFS byte- range locks 241, CIFS file locks 242, PC NFS (NLM) file locks 243, and NLM byte-range locks 244. Its operation is described in further detail with regard to figure 3 and figure 4.
- file server request messages 140 can be received from Unix client devices 201, PC NFS Windows client devices 202, or CIFS Windows client devices 203, and can use the NFS file server protocol or the CIFS file server protocol. In addition to each using differing file server protocols, each of these types of client device 130 has a different model of file locking provided by the file server 110.
- NFS file seiver protocol provides for performing file system operations without any form of file-open or file-close semantics.
- NFS file system operations can include read or write operations to file data, or file system manipulation (that is, read and write operations to directories).
- File system manipulation can include creating files or directories, renaming files or directories, moving files from one directory to another, or removing (deleting) files or directories from the file system.
- the NLM adjunct protocol provides for obtaining and releasing byte-range locks for files. These byte-range locks can be "read locks.” which induce other compliant applications
- byte-range locks can alternatively be "write locks,” which induce other compliant applications to refrain from either reading from or writing to the specified byte-range.
- the CIFS file server protocol provides for performing file-open operations, and obtaining file locks on the files 113 to be opened, before attempting any read or write operations to data in those files 113.
- a CIFS client device 130 can specify the access- mode it desires (read-only, write-only, or read-write), and the deny-mode it desires to impose on other client devices 130 attempting to open the same file 113 (deny-none, deny-read, deny-write, or deny-all). Thereafter, CIFS file system operations need only be checked against the access- mode that the file-open obtained.
- a CIFS client device 130 can also specify a byte-range lock for a byte-range in a file the client device 130 holds open.
- the byte-range lock is either an exclusive lock, also called a "write lock” (having access-mode read-write and deny-mode deny- all), or a nonexclusive lock, also called a "read lock” (having access-mode read-only and deny- mode deny-write).
- the file server 110 determines a lock mode that combines the access-mode and the deny-mode.
- lock mode refers to a uniform lock mode imposed by the file server 110 which combines an access-mode and a deny-mode.
- CIFS client devices 130 can also obtain an oplock (opportunistic lock), which provides that the CIFS client device 130 opening the file has exclusive access to the file so long as another client device 130 does not attempt to use the file.
- oplock provides a higher degree of exclusivity to the file than strictly necessary for the client device 130, with the caveat that the exclusivity of the oplock can be broken by attempted access by another client device 130.
- the file server 1 10 provides for correct interoperation among client devices 130 using NFS (with or without the adjunct protocol NLM) or CIFS.
- the file server 110 provides a uniform file-locking semantics.
- the uniform file-locking semantics has the following effects:
- the file server 1 10 prevents Unix client devices 201 from performing NFS write operations that would overwrite data in a file 1 13 that is already opened and in use by a CIFS client with deny-modes deny-write or deny-all.
- the file server 1 10 prevents Unix client devices 201 and PC NFS Windows client devices 202 from performing NFS file system operations that would remove or rename a file 1 13 that is already opened and in use by a CIFS client.
- the file server 1 10 When a Unix client device 201 or a PC NFS Windows client device 202 makes an NFS request to remove, rename, or write data to a file 113 that is oplocked by a CIFS client, the file server 1 10 will enforce CIFS oplock semantics for the file 1 13. The file server 1 10 sends an oplock-break message 140 to the client device 130 holding the oplock, and receives a response from the client device 130. If the client device 130 closes the file
- the NFS request can proceed and the file server 110 allows it to.
- the file server 110 When a Unix client device 201 or a PC NFS Windows client device 202 makes an NFS request to read data from a file 1 13 that is oplocked by a CIFS client, the file server 110 will enforce CIFS oplock semantics for the file 113.
- the file server 1 10 sends an oplock- break message 140 to the client device 130 holding the oplock, and receives a response from the client device 130.
- the client device 130 either closes the file 1 13 or flushes its write cache to the file server 110.
- the NFS request can proceed and the file server 1 10 allows it to.
- the file server 110 tests for mutual compatibility for file-open requests from CIFS Windows client devices 203, and NLM file lock requests from PC NFS Windows client devices 202, with regard to their specified lock modes.
- NLM file lock
- the phrase NLM "file lock” is used herein in place of the known plrrase NLM “share lock,” further described in the following document: "X/Open CAE Specification: Protocols for X/Open Interworking:
- the specified lock mode is determined by the file server 1 10 by combining the requested access-mode and deny-mode.
- the file server 110 performs the following lock management operations:
- the file server 110 Upon receiving a CIFS file-open request message 140. the file server 110 tests the file- open request for conflict with existing CIFS and NLM file locks, and for conflict with existing NLM byte-range locks. For the purpose of comparison with newly requested file locks, the file server 110 treats existing NLM byte-range locks as having deny-mode deny-none, and as having access-mode read-only for nonexclusive locks and access- mode read-write for exclusive locks.
- the file server 110 Upon receiving a CIFS byte-range lock request message 140, the file server 110 tests the byte-range lock request for conflict with existing CIFS and NLM byte-range locks.
- the file server 1 10 Upon receiving an NLM byte-range lock request message 140, the file server 1 10 tests the byte-range lock request for conflict with existing CIFS and NLM byte-range locks, and for conflict with existing CIFS file locks.
- the file server 110 Upon receiving an NLM file lock request message 140 from a PC NFS client device 130 (used to simulate a file-open request message 140), the file server 110 tests the NLM file lock request for conflict with existing CIFS and NLM file locks, and for conflict with existing NLM byte-range locks. For the purpose of comparison with newly requested
- the file server 1 10 treats existing NLM byte-range locks as having deny- mode deny-none, and as having access-mode read-only for nonexclusive locks and access-mode read-write for exclusive locks.
- Method of Operation Multi-Protocol File Server
- Figure 3 shows a process flow diagram of a method of operating a multi-protocol file server.
- a method 300 of operating a multi-protocol file server includes a set of process steps and flow points as described herein, to be performed by the file server 110 in cooperation with at least one client device 130.
- the file server 110 is ready to receive the file server request message 140.
- the file server 110 receives and parses the file server request message 140.
- the file server 110 determines if the file server request message 140 uses the NFS file server protocol, the NLM file locking protocol, or the CIFS file server protocol. If the file server request message 140 uses the NFS file server protocol or the NLM file locking protocol, the method 300 continues with the step 312. If the file server request message 140 uses the CIFS file server protocol, the method 300 continues with the step 313.
- the file server 110 determines if the request message 140 includes an NFS file server request to perform a file s stem operation (such as to read or write data, or to modify a directory). Alternatively, the file server 110 determines if the request message 140 includes an NLM file-locking request to obtain an NLM byte-range lock. In either case, the method 300 continues at the flow point 320.
- the file server 110 determines if the file server request message 140 is to perform a CIFS read or write operation, to obtain a CIFS byte-range lock, or to perform a CIFS file-open operation.
- the method 300 continues at the flow-point 320. If the file server request message 140 is to perform a CIFS read or write operation, the method continues at the flow-point 330. If the file server request message 140 is a CIFS "change-notify" request, the method continues at the flow point 350 (the change-notify request is further described with regard to figure 6).
- the file server 110 is ready to compare the operation requested by the file server request message 140 with the file-locking status of the file 113.
- the file-locking status of the file 113 includes existing file locks and byte-range locks for the file 113.
- the file server 1 10 determines the file 113 that is the subject of the file server request message 140, and determines if the file 113 is oplocked. If the file 113 is oplocked. the method 300 continues with the step 322. If the file 113 is not oplocked, the method 300 continues with the step 323.
- the file server 110 breaks the oplock, as described herein. Performance of the step 322 is further described with regard to figure 5. Breaking the oplock can cause the file-locking status of the file 113 to change.
- the file server 110 compares the requested operation with the file- locking status of the file 113, using a uniform file-locking semantics.
- the requested operation can be an NFS read or write operation, an NFS or CIFS directory modification operation, an attempt to obtain an NLM file lock or byte-range lock, or a CIFS file-open operation.
- Performance of the step 323 and the uniform file-locking semantics are further described with regard to figure 4. If the comparison shows that the requested operation is allowable, the method 300 continues with the step 324. If the requested operation is not allowable, the method 300 continues with the step 325.
- the file server 110 performs the requested operation.
- the method 300 continues at the flow point 340.
- the file server 110 refuses to perform the requested operation and responds to the client device 130 with an error message.
- the method 300 continues at the flow point 340.
- the file server 110 is ready to compare the operation requested by the file server request message 140 with the file-locking status of the file 113.
- a first CIFS client device 130 requests a file lock for a directory (using a file system request message 140 to open the directory), and converts the file lock for the directory to a change-monitoring lock on the directory. Performance of this step 351 is further described with regard to figure 6.
- the file server 1 10 has responded to the file server request message 140, and the method 300 is complete with regard to that file server request message 140.
- Figure 4 shows a process flow diagram of a method of operating a cross-protocol lock manager in a multi-protocol file server.
- a method 400 of operating a cross-protocol lock manager in a multi-protocol file server includes a set of process steps and flow points as described herein, to be performed by the file server 110 in cooperation with at least one client device 130.
- the file server 110 is ready to compare the requested operation in the file server request message 140, with the file-locking status of the file 113.
- the file server 110 uses a uniform file-locking semantics, so as to model file- locking aspects of any requested operation from any file server protocol in the same way.
- the uniform file-locking semantics identifies a uniform set of file locks, each including an access- mode for the requesting client device 130 and a deny-mode for all other client devices 130.
- the access-mode can be one of three possibilities — read-only, write-only, or read-write.
- the deny-mode can be one of four possibilities — deny-none, deny-read, deny-write, or deny-all.
- a second client device 130 can only access that file 113 if the lock mode determined by the file server 110 to be requested by the second client device 130 is compatible with the file-locking status of the file
- a first client device 130 can obtain a file lock for a file 113 with a deny-mode deny-write.
- a second NFS client device 130 could attempt to write to the file 113, or a second CIFS client device 130 could attempt to open the file 1 13 with an access-mode including write access.
- the file server 1 10 will deny the request by the second client device 130.
- the file server 1 10 performs the comparison of the file lock with the access requested by the second client device 130 at differing times, in response to the file server protocol used by the second client device 130:
- the file server 1 10 checks the file-locking status of the file 1 13 at file-open time.
- the file server 1 10 checks the file-locking status of the file 1 13 at the time of the actual file system operation. This also applies to file system operations that have the effect of removing the file from view of the first client device 130, such as operations to move, remove, or rename the file 1 13.
- the file server 1 10 checks the file-locking status of the file 1 13 for conflict with other CIFS or NLM byte-range locks, at the time the byte-range lock is requested. The file server 1 10 does not check for conflict with other CIFS file locks at the time the byte- range lock is requested, because those were checked at file-open time.
- the file server 110 checks the file-locking status of the file 113 for conflict with existing
- the file server 1 10 determines if there is already more than one file lock associated with the file 1 13. If so. the method 400 continues with the step 422. If not, the method continues with the step 41 1.
- the file server 1 10 combines file locks already associated with the file 113 into a single equivalent file lock associated with the file 1 13.
- the file server 110 cross-indexes in table 1 a cumulative file lock with each pre-existing file lock, until all pre-existing file locks have been cumulated together.
- Table 1 shows a lock conversion table in a multi-protocol file server with unified file-locking semantics.
- the file server 110 determines the nature of the requested operation in the file server request message 140 If the requested operation is a CIFS file-open operation, the method 400 continues with the step 423 If the requested operation is an NFS file server operation, the method 400 continues with the step 431. If the requested operation is either a CIFS request an NLM request for a byte-range lock, the file system 110 continues with the step 441.
- the file server 1 10 compares the file lock already associated with the file 113 with the file open requested by the second client device 130. To perform this step 423, the file server 110 cross-indexes in table 2 the pre-existing file lock and the requested new access-mode and deny-mode, and allows or denies the requested new access-mode and deny- mode in response to the associated table entry.
- the method 400 performs the step 424. If the file server 110 denies the requested new access-mode and deny-mode, the method 400 does not perform the step 424.
- Table 2 shows a cross-index of attempted file locks in a multi-protocol file server with unified file-locking semantics.
- A Access Mode.
- D Deny Mode
- each pair of pre-existing file lock and requested new access- mode and deny-mode has an associated decision to allow or to deny the requested new access- mode and deny-mode.
- the file server 110 is checking for conflicts between an existing CIFS file lock and a new request to perform a file-open operation, the existing CIFS file lock is cross-indexed against the access-mode and deny-mode requested in the new file-open request.
- the aggregate lock mode (the combination of existing file locks) is cross-indexed against the access-mode required to perform the new request.
- the file server 110 If the file server 110 is checking for conflicts between existing file locks or byte- range locks, and a new request for a NLM byte-range lock, the existing file locks and byte-range locks are cross-indexed against a lock mode equivalent to the new NLM byte-range lock request. For the purpose of comparing with existing file locks, the file server 110 treats newly requested NLM byte-range locks as having deny-mode deny-none, and as having access-mode read-only for nonexclusive locks (also called “read locks”) and access-mode read-write for exclusive locks (also called “write locks").
- the file server 110 treats newly requested NLM byte-range locks as having access-mode read-only and deny-mode deny-write for read locks, and as having access-mode read-write and deny-mode deny-all for write locks.
- the method 400 then continues at the flow point 450.
- the file server 110 compares the file-locking status of the file 113 with the operation requested by the second client device 130. To perform this step 431, the file server 110 compares the deny-mode for the file lock with the requested operation, and allows or denies the requested operation in response thereto.
- the method 400 then continues at the flow point 450.
- the file server 110 compares the file-locking status of the file 113 with the NLM byte-range lock requested by the second client device 130.
- CIFS byte-range lock requests are only checked against byte-range locks because they require a prior CIFS file open operation at which existing file locks were already checked.
- the file server 1 10 cross-indexes in table 3 the pre-existing file-locking status and the requested byte-range lock, and allows or denies the requested byte-range lock in response to the associated table entry.
- the method 400 performs the step 442. If the file server 110 denies the requested new byte-range lock, the method 400 does not perform the step 442.
- Table 3 shows a cross-index of existing file locks and newly requested NLM byte-range locks in a multi-protocol file server with unified file-locking semantics.
- A Access Mode
- D Deny mode
- each pair of existing file lock and newly requested NLM byte-range lock has an associated decision to allow or to deny the requested new byte-range lock.
- the file server 1 10 associates the requested new byte-range lock with the file 113 as a new additional byte-range lock.
- the method 400 then continues at the flow point 450.
- the file server 1 10 has compared the requested operation in the file server request message 140 with the file-lockmg status of the file 1 13, and allowed or denied the requested operation.
- Figure 5 shows a process flow diagram of a method of operating an oplock manager in a multi-protocol file server.
- a method 500 of operating a oplock manager in a multi-protocol file server includes a set of process steps and flow points as described herein, to be performed by the file server 110 in cooperation with at least one client device 130.
- Oplocks are known in the art of file-locking in Windows operating system environments. They are further described in documentation available for the "Windows NT 4.0" operating system, available from Microsoft Corporation of Redmond, Washington, including for example the CIFS IETF specification, available via the FTP protocol at host ftp.microsoft.com, directory /developr/drg/CIFS, files cifs6.doc or cifs6.txt, hereby incorporated by reference as if fully set forth herein.
- the file server 110 is ready to receive a request from a CIFS first client device 130 to open a file 113.
- the file server 110 receives a file-open request for a file 113 from a CIFS first client device 130.
- the file-open request designates an access-mode and a deny-mode.
- the file server 1 10 determines that it should allow the request, and grants the first client device 130 a file lock with the designated access-mode and deny-mode.
- the file server 110 grants the first client device 130 an oplock at a level of exclusivity possibly greater than the first client device 130 actually requires.
- the file server 110 associates a file lock of that type with the file 113.
- the file server 1 1 further associates an oplock with the file 113 with the access-mode read- write and deny-mode deny-all.
- the file server 110 has responded to the request from the CIFS first client device 130 for a file lock for a file 113.
- a second client device 130 attempts to open the file 113.
- the file server 110 receives either a file-open request from a second CIFS client device 130 or a NLM file lock request from a PC NFS client device 130.
- the file server 110 suspends execution of the request by the second client device 130 while it breaks the oplock and obtains a response from the holder of the oplock, the first client device 130.
- the file server 1 10 breaks the oplock by sending an "oplock-break" message 140 to the CIFS first client device 130.
- the file server 110 delays its response to the NFS (or NLM) protocol request message 140 until the CIFS first client device 130 responds to the "oplock-break" message 140.
- the CIFS first client device 130 receives the "oplock-break" message 140, and can respond to the message 140 in one of two ways:
- the CIFS first client device 130 can close the file 1 13 (thus removing the file lock associated with the file-open); or
- the CIFS first client device 130 can flush all outstanding CIFS write and byte-range lock requests for the file 113 that are being cached locally at the client device 130 (that is, it can forward the results of those file system operations to the file server 110), and discard any read-ahead data it has obtained for the file 1 13. Read-ahead data should be discarded because the second client device 130 might subsequently write new data to the file, invalidating the read-ahead data.
- the file server 1 10 receives the response from the CIFS first client device 130.
- the file server 1 10 determines if the CIFS first client device 130 has maintained the file 113 open, and if so, compares the lock mode implied by the request by the second client device 130 against the new file-locking status of the file 113. If the file server 1 10 determines that the request by the second client device 130 is allowed to proceed, it continues with the flow point 540. If the file server 110 determines that the request by the second client device 130 is not allowed to proceed, it denies the request.
- the file server 110 is ready to proceed to allow the request from the second client device 130 noted in the step 531.
- Method of Operation (Change-Notify Manager)
- Figure 6 shows a process flow diagram of a method of operating a change-notify manager in a multi-protocol file server.
- a method 600 of operating a change-notify manager in a multi-protocol file server includes a set of process steps and flow points as described herein, to be performed by the file server 110 in cooperation with at least one client device 130.
- the file server 110 is ready to receive the file server request message 140.
- the file server 110 receives a file-open request message 140 from a first CIFS client device 130, designating a directory on the file server 110.
- the file server 110 determines that it should allow the file-open request and grants a CIFS file lock on the directory to the first CIFS client device 130.
- the file server 110 receives a change-notify request message from the first CIFS client device 130, referencing the open directory, to convert the file lock on the open directory to a change-monitoring lock.
- the file server 1 10 converts the file lock on the open directory to a change-monitoring lock on the designated directory.
- the "change-monitoring" lock has been associated with the designated directory, and the first CIFS client device 130 is ready to be notified of changes to that directory.
- the file server 1 10 receives a file server request message 140 from a second client device 130, requesting a change to the designated directory, and thus triggering a change notification to the first client device 130.
- Types of change include file creation, file deletion, file rename, file move between directories, file attribute change, and file modification time change.
- the file server request message 140 from the second client device 130 can be either CIFS or NFS.
- the second client device 130 can be any one of a Unix NFS client device 201 , a PC NFS client device 202, or a CIFS Windows client device 203.
- the file server 110 notifies the first client device 130, which holds the "change-monitoring" lock, of the changes noted in the step 621, containing possibly multiple entries, each of which specifies both the name of the changed file 113 or subdirectory within the monitored directory and the type of change. If there is more than one such first client device 130, the file server 110 notifies all of them.
- the file server 110 has notified the first CIFS client device 130 of changes to the designated directory, and is ready for a next message 140.
Abstract
Description
Claims
Priority Applications (4)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
JP2000524743A JP2001526426A (en) | 1997-12-05 | 1998-11-30 | Multi-protocol unified file locking |
CA002312492A CA2312492C (en) | 1997-12-05 | 1998-11-30 | Multi-protocol unified file-locking |
EP98961834A EP1034493A1 (en) | 1997-12-05 | 1998-11-30 | Multi-protocol unified file-locking |
US10/230,877 US7293097B2 (en) | 1997-12-05 | 2002-08-28 | Enforcing uniform file-locking for diverse file-locking protocols |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US98539897A | 1997-12-05 | 1997-12-05 | |
US08/985,398 | 1997-12-05 |
Related Child Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US10/230,877 Continuation US7293097B2 (en) | 1997-12-05 | 2002-08-28 | Enforcing uniform file-locking for diverse file-locking protocols |
Publications (1)
Publication Number | Publication Date |
---|---|
WO1999030254A1 true WO1999030254A1 (en) | 1999-06-17 |
Family
ID=25531449
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/US1998/025388 WO1999030254A1 (en) | 1997-12-05 | 1998-11-30 | Multi-protocol unified file-locking |
Country Status (5)
Country | Link |
---|---|
US (2) | US6516351B2 (en) |
EP (1) | EP1034493A1 (en) |
JP (2) | JP2001526426A (en) |
CA (1) | CA2312492C (en) |
WO (1) | WO1999030254A1 (en) |
Cited By (13)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
SG91903A1 (en) * | 2000-03-30 | 2002-10-15 | Ibm | File system locking |
US6516351B2 (en) | 1997-12-05 | 2003-02-04 | Network Appliance, Inc. | Enforcing uniform file-locking for diverse file-locking protocols |
JP2003513544A (en) * | 1999-11-04 | 2003-04-08 | ミラポイント インコーポレイテッド | Method and apparatus for electronic message communication system |
EP1335286A2 (en) * | 2002-02-07 | 2003-08-13 | Fujitsu Limited | Control device for file resources in a network |
EP1335285A2 (en) * | 2002-02-07 | 2003-08-13 | Fujitsu Limited | Control device for file resources in a network |
GB2394816A (en) * | 1999-10-18 | 2004-05-05 | Fisher Rosemount Systems Inc | Database server to provide concurrent access for multiple clients to the database uses a shared cache for holding copy of the data being accessed |
US6751637B1 (en) | 1995-05-31 | 2004-06-15 | Network Appliance, Inc. | Allocating files in a file system integrated with a raid disk sub-system |
EP1473632A2 (en) * | 2003-04-11 | 2004-11-03 | Sun Microsystems, Inc. | Generation interface for file interval lock |
US6826615B2 (en) | 1999-10-14 | 2004-11-30 | Bluearc Uk Limited | Apparatus and method for hardware implementation or acceleration of operating system functions |
US7127460B2 (en) | 1999-10-18 | 2006-10-24 | Fisher-Rosemount Systems, Inc. | Accessing and updating a configuration database from distributed physical locations within a process control system |
JP2014520343A (en) * | 2011-06-24 | 2014-08-21 | ネットアップ,インコーポレイテッド | System and method for providing an integrated storage system that supports file / object duality |
US9542310B2 (en) | 2002-11-01 | 2017-01-10 | Hitachi Data Systems Engineering UK Limited | File server node with non-volatile memory processing module coupled to cluster file server node |
EP3525127A4 (en) * | 2016-08-08 | 2020-05-20 | Namusoft Co., Ltd. | Method and system for blocking phishing or ransomware attack |
Families Citing this family (119)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7010532B1 (en) * | 1997-12-31 | 2006-03-07 | International Business Machines Corporation | Low overhead methods and apparatus for shared access storage devices |
US6279011B1 (en) * | 1998-06-19 | 2001-08-21 | Network Appliance, Inc. | Backup and restore for heterogeneous file server environment |
JP3786521B2 (en) * | 1998-07-01 | 2006-06-14 | 株式会社日立製作所 | Semiconductor integrated circuit and data processing system |
JP4745478B2 (en) * | 1999-01-29 | 2011-08-10 | キヤノン株式会社 | Network print system, information processing apparatus and control method therefor |
US6922729B1 (en) * | 1999-07-30 | 2005-07-26 | International Business Machines Corporation | Multi-connection control system |
US7840639B1 (en) * | 1999-09-21 | 2010-11-23 | G&H Nevada-Tek | Method and article of manufacture for an automatically executed application program associated with an electronic message |
US6360221B1 (en) | 1999-09-21 | 2002-03-19 | Neostar, Inc. | Method and apparatus for the production, delivery, and receipt of enhanced e-mail |
US9092535B1 (en) | 1999-09-21 | 2015-07-28 | Google Inc. | E-mail embedded textual hyperlink object |
US7043553B2 (en) * | 1999-10-07 | 2006-05-09 | Cisco Technology, Inc. | Method and apparatus for securing information access |
US7203735B1 (en) * | 1999-10-21 | 2007-04-10 | International Business Machines Corporation | Files transfer between a remote home server and a local server |
US6993131B1 (en) * | 2000-09-12 | 2006-01-31 | Nokia Corporation | Method and system for managing rights in digital information over a network |
US20020055923A1 (en) * | 2000-11-01 | 2002-05-09 | Sun Microsystems, Inc. | Mandatory locking mechanisms for UNIX file systems |
AU2002249939A1 (en) * | 2001-01-11 | 2002-07-24 | Z-Force Communications, Inc. | File switch and switched file system |
US7383288B2 (en) | 2001-01-11 | 2008-06-03 | Attune Systems, Inc. | Metadata based file switch and switched file system |
US20040133606A1 (en) * | 2003-01-02 | 2004-07-08 | Z-Force Communications, Inc. | Directory aggregation for files distributed over a plurality of servers in a switched file system |
US8195760B2 (en) * | 2001-01-11 | 2012-06-05 | F5 Networks, Inc. | File aggregation in a switched file system |
US8239354B2 (en) | 2005-03-03 | 2012-08-07 | F5 Networks, Inc. | System and method for managing small-size files in an aggregated file system |
US7512673B2 (en) | 2001-01-11 | 2009-03-31 | Attune Systems, Inc. | Rule based aggregation of files and transactions in a switched file system |
US7509322B2 (en) * | 2001-01-11 | 2009-03-24 | F5 Networks, Inc. | Aggregated lock management for locking aggregated files in a switched file system |
US7788335B2 (en) * | 2001-01-11 | 2010-08-31 | F5 Networks, Inc. | Aggregated opportunistic lock and aggregated implicit lock management for locking aggregated files in a switched file system |
US6779063B2 (en) | 2001-04-09 | 2004-08-17 | Hitachi, Ltd. | Direct access storage system having plural interfaces which permit receipt of block and file I/O requests |
US6959337B2 (en) * | 2001-04-23 | 2005-10-25 | Hewlett-Packard Development Company, L.P. | Networked system for assuring synchronous access to critical facilities |
US20020188697A1 (en) * | 2001-06-08 | 2002-12-12 | O'connor Michael A. | A method of allocating storage in a storage area network |
US7370217B2 (en) * | 2001-11-16 | 2008-05-06 | Intel Corporation | Regulating file system device access |
US7529778B1 (en) | 2001-12-12 | 2009-05-05 | Microsoft Corporation | System and method for providing access to consistent point-in-time file versions |
US7313557B1 (en) * | 2002-03-15 | 2007-12-25 | Network Appliance, Inc. | Multi-protocol lock manager |
US7051050B2 (en) * | 2002-03-19 | 2006-05-23 | Netwrok Appliance, Inc. | System and method for restoring a single file from a snapshot |
JP2003281140A (en) * | 2002-03-20 | 2003-10-03 | Hitachi Ltd | Contents delivery method and delivery system |
US6857001B2 (en) | 2002-06-07 | 2005-02-15 | Network Appliance, Inc. | Multiple concurrent active file systems |
US7024586B2 (en) * | 2002-06-24 | 2006-04-04 | Network Appliance, Inc. | Using file system information in raid data reconstruction and migration |
US7797392B2 (en) * | 2002-11-26 | 2010-09-14 | International Business Machines Corporation | System and method for efficiently supporting multiple native network protocol implementations in a single system |
US7877511B1 (en) | 2003-01-13 | 2011-01-25 | F5 Networks, Inc. | Method and apparatus for adaptive services networking |
US8706760B2 (en) | 2003-02-28 | 2014-04-22 | Microsoft Corporation | Method to delay locking of server files on edit |
JP2004280283A (en) * | 2003-03-13 | 2004-10-07 | Hitachi Ltd | Distributed file system, distributed file system server, and access method to distributed file system |
JP4320195B2 (en) * | 2003-03-19 | 2009-08-26 | 株式会社日立製作所 | File storage service system, file management apparatus, file management method, ID designation type NAS server, and file reading method |
US7409389B2 (en) * | 2003-04-29 | 2008-08-05 | International Business Machines Corporation | Managing access to objects of a computing environment |
CA2543746C (en) * | 2003-10-27 | 2018-01-16 | Archivas, Inc. | Policy-based management of a redundant array of independent nodes |
US7380246B2 (en) * | 2003-12-15 | 2008-05-27 | Lenovo (Singapore) Pte. Ltd. | Method and system of accessing at least one target file in a computer system with an operating system with file locking implemented with byte-range locking |
US7660882B2 (en) * | 2004-06-10 | 2010-02-09 | Cisco Technology, Inc. | Deploying network element management system provisioning services |
US20060015493A1 (en) * | 2004-07-15 | 2006-01-19 | International Business Machines Corporation | Enhanced records manager and related methods |
US7617256B2 (en) * | 2004-07-19 | 2009-11-10 | Microsoft Corporation | Remote file updates through remote protocol |
US7784088B2 (en) * | 2004-07-30 | 2010-08-24 | Research In Motion Limited | Method and system for managing delayed user authentication |
CN101002180B (en) * | 2004-07-30 | 2012-09-05 | 捷讯研究有限公司 | Method and system for coordinating client and host security modules |
US7315926B2 (en) * | 2004-09-21 | 2008-01-01 | Emc Corporation | Lock management for concurrent access to a single file from multiple data mover computers |
US7885970B2 (en) * | 2005-01-20 | 2011-02-08 | F5 Networks, Inc. | Scalable system for partitioning and accessing metadata over multiple servers |
US20060167838A1 (en) * | 2005-01-21 | 2006-07-27 | Z-Force Communications, Inc. | File-based hybrid file storage scheme supporting multiple file switches |
US7958347B1 (en) | 2005-02-04 | 2011-06-07 | F5 Networks, Inc. | Methods and apparatus for implementing authentication |
US8332485B1 (en) | 2005-03-04 | 2012-12-11 | Cisco Technology, Inc. | Lock optimization and lock prediction approaches for reducing client-server messages |
US8316129B2 (en) | 2005-05-25 | 2012-11-20 | Microsoft Corporation | Data communication coordination with sequence numbers |
US7853962B1 (en) | 2005-05-31 | 2010-12-14 | Cisco Technology, Inc. | Method and apparatus for optimization of remote procedure call communications |
US20060277221A1 (en) * | 2005-06-01 | 2006-12-07 | Green Hills Software, Inc. | Transactional file system with client partitioning |
US7716307B1 (en) * | 2005-10-21 | 2010-05-11 | Cisco Technology, Inc. | Method and apparatus for reducing client-server messages associated with opening a file |
US7636767B2 (en) * | 2005-11-29 | 2009-12-22 | Cisco Technology, Inc. | Method and apparatus for reducing network traffic over low bandwidth links |
US7644121B2 (en) * | 2005-11-30 | 2010-01-05 | Clickpath, Llc | Method and system for online session tracking |
US7581004B2 (en) * | 2006-02-15 | 2009-08-25 | Gabriel Jakobson | System and method for alerting on open file-share sessions on a user's electronic device |
US7904435B2 (en) * | 2006-03-10 | 2011-03-08 | Yahoo! Inc. | System and method for resource lock acquisition and reclamation in a network file system environment |
US8417746B1 (en) | 2006-04-03 | 2013-04-09 | F5 Networks, Inc. | File system management with enhanced searchability |
US8788685B1 (en) * | 2006-04-27 | 2014-07-22 | Netapp, Inc. | System and method for testing multi-protocol storage systems |
US8583596B2 (en) * | 2006-11-29 | 2013-11-12 | Red Hat, Inc. | Multi-master referential integrity |
US20080243847A1 (en) * | 2007-04-02 | 2008-10-02 | Microsoft Corporation | Separating central locking services from distributed data fulfillment services in a storage system |
US8433693B2 (en) * | 2007-04-02 | 2013-04-30 | Microsoft Corporation | Locking semantics for a storage system based on file types |
US20090077097A1 (en) * | 2007-04-16 | 2009-03-19 | Attune Systems, Inc. | File Aggregation in a Switched File System |
WO2008147973A2 (en) * | 2007-05-25 | 2008-12-04 | Attune Systems, Inc. | Remote file virtualization in a switched file system |
US8117244B2 (en) | 2007-11-12 | 2012-02-14 | F5 Networks, Inc. | Non-disruptive file migration |
US20090204705A1 (en) * | 2007-11-12 | 2009-08-13 | Attune Systems, Inc. | On Demand File Virtualization for Server Configuration Management with Limited Interruption |
US8180747B2 (en) | 2007-11-12 | 2012-05-15 | F5 Networks, Inc. | Load sharing cluster file systems |
US8548953B2 (en) * | 2007-11-12 | 2013-10-01 | F5 Networks, Inc. | File deduplication using storage tiers |
US20090204650A1 (en) * | 2007-11-15 | 2009-08-13 | Attune Systems, Inc. | File Deduplication using Copy-on-Write Storage Tiers |
US7809776B1 (en) * | 2007-11-30 | 2010-10-05 | Netapp, Inc. | System and method for supporting change notify watches for virtualized storage systems |
US8352785B1 (en) | 2007-12-13 | 2013-01-08 | F5 Networks, Inc. | Methods for generating a unified virtual snapshot and systems thereof |
US8549582B1 (en) | 2008-07-11 | 2013-10-01 | F5 Networks, Inc. | Methods for handling a multi-protocol content name and systems thereof |
US8230439B2 (en) * | 2008-08-22 | 2012-07-24 | International Business Machines Corporation | Green computing interchange switching function |
EP2352090B1 (en) * | 2008-10-06 | 2019-09-25 | International Business Machines Corporation | System accessing shared data by a plurality of application servers |
US9031990B2 (en) * | 2009-08-11 | 2015-05-12 | Q2 Management Inc. | Data processing system for manufacturing quality inspection management system |
US10721269B1 (en) | 2009-11-06 | 2020-07-21 | F5 Networks, Inc. | Methods and system for returning requests with javascript for clients before passing a request to a server |
JP5349269B2 (en) * | 2009-12-07 | 2013-11-20 | ブリヂストンスポーツ株式会社 | Tennis ball felt and tennis ball |
US9195500B1 (en) | 2010-02-09 | 2015-11-24 | F5 Networks, Inc. | Methods for seamless storage importing and devices thereof |
US8204860B1 (en) | 2010-02-09 | 2012-06-19 | F5 Networks, Inc. | Methods and systems for snapshot reconstitution |
US8347100B1 (en) | 2010-07-14 | 2013-01-01 | F5 Networks, Inc. | Methods for DNSSEC proxying and deployment amelioration and systems thereof |
US8965862B2 (en) | 2010-09-17 | 2015-02-24 | Microsoft Corporation | Directory oplock |
JP5539833B2 (en) * | 2010-09-29 | 2014-07-02 | キヤノン電子株式会社 | Information processing apparatus and control method therefor, computer program, and computer-readable storage medium |
US9286298B1 (en) | 2010-10-14 | 2016-03-15 | F5 Networks, Inc. | Methods for enhancing management of backup data sets and devices thereof |
US8631277B2 (en) | 2010-12-10 | 2014-01-14 | Microsoft Corporation | Providing transparent failover in a file system |
JP5249368B2 (en) * | 2011-01-31 | 2013-07-31 | 株式会社バッファロー | Network equipment |
US8849880B2 (en) | 2011-05-18 | 2014-09-30 | Hewlett-Packard Development Company, L.P. | Providing a shadow directory and virtual files to store metadata |
WO2012170004A1 (en) * | 2011-06-06 | 2012-12-13 | Hewlett-Packard Development Company, L.P. | Cross-protocol locking with a file system |
US9331955B2 (en) | 2011-06-29 | 2016-05-03 | Microsoft Technology Licensing, Llc | Transporting operations of arbitrary size over remote direct memory access |
US8856582B2 (en) | 2011-06-30 | 2014-10-07 | Microsoft Corporation | Transparent failover |
US8396836B1 (en) | 2011-06-30 | 2013-03-12 | F5 Networks, Inc. | System for mitigating file virtualization storage import latency |
US20130067095A1 (en) | 2011-09-09 | 2013-03-14 | Microsoft Corporation | Smb2 scaleout |
US8788579B2 (en) | 2011-09-09 | 2014-07-22 | Microsoft Corporation | Clustered client failover |
US8463850B1 (en) | 2011-10-26 | 2013-06-11 | F5 Networks, Inc. | System and method of algorithmically generating a server side transaction identifier |
US9020912B1 (en) | 2012-02-20 | 2015-04-28 | F5 Networks, Inc. | Methods for accessing data in a compressed file system and devices thereof |
US9519501B1 (en) | 2012-09-30 | 2016-12-13 | F5 Networks, Inc. | Hardware assisted flow acceleration and L2 SMAC management in a heterogeneous distributed multi-tenant virtualized clustered system |
US10375155B1 (en) | 2013-02-19 | 2019-08-06 | F5 Networks, Inc. | System and method for achieving hardware acceleration for asymmetric flow connections |
US9554418B1 (en) | 2013-02-28 | 2017-01-24 | F5 Networks, Inc. | Device for topology hiding of a visited network |
EP2853966A1 (en) * | 2013-09-30 | 2015-04-01 | Siemens Aktiengesellschaft | Industrial automation system with at least one controller and a memory |
US20150106298A1 (en) * | 2013-10-11 | 2015-04-16 | Prolifiq Sofware Inc. | Selective sharing of electronic information |
US9336406B2 (en) * | 2013-11-14 | 2016-05-10 | Futurewei Technologies, Inc. | Multiprotocol access control list with guaranteed protocol compliance |
US10536523B2 (en) * | 2014-05-11 | 2020-01-14 | Microsoft Technology Licensing, Llc | File service using a shared file access-rest interface |
US10169367B2 (en) * | 2014-06-06 | 2019-01-01 | Panzura, Inc. | Managing opportunistic locks in a distributed file system |
US11838851B1 (en) | 2014-07-15 | 2023-12-05 | F5, Inc. | Methods for managing L7 traffic classification and devices thereof |
US9917882B2 (en) * | 2014-11-30 | 2018-03-13 | Sonicwall Inc. | Transparent deferred spooling store and forward based on standard network system and client interface |
US10182013B1 (en) | 2014-12-01 | 2019-01-15 | F5 Networks, Inc. | Methods for managing progressive image delivery and devices thereof |
US10313486B2 (en) | 2015-01-07 | 2019-06-04 | Sonicwall Inc. | Optimizing transfer of fragmented packetized data |
US11895138B1 (en) | 2015-02-02 | 2024-02-06 | F5, Inc. | Methods for improving web scanner accuracy and devices thereof |
US10834065B1 (en) | 2015-03-31 | 2020-11-10 | F5 Networks, Inc. | Methods for SSL protected NTLM re-authentication and devices thereof |
US9813526B2 (en) | 2015-05-26 | 2017-11-07 | Sonicwall Inc. | Reducing transmission pathway lengths within a distributed network |
US10158735B2 (en) | 2015-08-07 | 2018-12-18 | Sonicwall Inc. | Read-ahead on signed connections with unsigning, inline, transparent proxies |
US10404698B1 (en) | 2016-01-15 | 2019-09-03 | F5 Networks, Inc. | Methods for adaptive organization of web application access points in webtops and devices thereof |
US10797888B1 (en) | 2016-01-20 | 2020-10-06 | F5 Networks, Inc. | Methods for secured SCEP enrollment for client devices and devices thereof |
US10412198B1 (en) | 2016-10-27 | 2019-09-10 | F5 Networks, Inc. | Methods for improved transmission control protocol (TCP) performance visibility and devices thereof |
US10567492B1 (en) | 2017-05-11 | 2020-02-18 | F5 Networks, Inc. | Methods for load balancing in a federated identity environment and devices thereof |
US11223689B1 (en) | 2018-01-05 | 2022-01-11 | F5 Networks, Inc. | Methods for multipath transmission control protocol (MPTCP) based session migration and devices thereof |
US10833943B1 (en) | 2018-03-01 | 2020-11-10 | F5 Networks, Inc. | Methods for service chaining and devices thereof |
US11082494B2 (en) | 2019-12-05 | 2021-08-03 | Western Digital Technologies, Inc. | Cross storage protocol access response for object data stores |
US11455213B2 (en) * | 2020-02-05 | 2022-09-27 | EMC IP Holding Company LLC | Method and system for parallel data transmission and cooperating backups |
CN115934743B (en) * | 2023-03-13 | 2023-06-02 | 浪潮电子信息产业股份有限公司 | File lock management method, system, equipment and computer readable storage medium |
CN115951844B (en) * | 2023-03-13 | 2023-06-06 | 浪潮电子信息产业股份有限公司 | File lock management method, equipment and medium of distributed file system |
Citations (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5261051A (en) * | 1989-08-14 | 1993-11-09 | Microsoft Corporation | Method and system for open file caching in a networked computer system |
Family Cites Families (76)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US4814971A (en) | 1985-09-11 | 1989-03-21 | Texas Instruments Incorporated | Virtual memory recovery system using persistent roots for selective garbage collection and sibling page timestamping for defining checkpoint state |
US4719569A (en) | 1985-10-11 | 1988-01-12 | Sun Microsystems, Inc. | Arbitrator for allocating access to data processing resources |
US4825354A (en) | 1985-11-12 | 1989-04-25 | American Telephone And Telegraph Company, At&T Bell Laboratories | Method of file access in a distributed processing computer network |
US4742450A (en) | 1986-01-16 | 1988-05-03 | International Business Machines Corporation | Method to share copy on write segment for mapped files |
US4780821A (en) | 1986-07-29 | 1988-10-25 | International Business Machines Corp. | Method for multiple programs management within a network having a server computer and a plurality of remote computers |
US4887204A (en) | 1987-02-13 | 1989-12-12 | International Business Machines Corporation | System and method for accessing remote files in a distributed networking environment |
CA1299757C (en) | 1987-08-28 | 1992-04-28 | Brent Cameron Beardsley | Device initiated partial system quiescing |
EP0306244B1 (en) | 1987-09-04 | 1995-06-21 | Digital Equipment Corporation | Fault tolerant computer system with fault isolation |
US5109515A (en) | 1987-09-28 | 1992-04-28 | At&T Bell Laboratories | User and application program transparent resource sharing multiple computer interface architecture with kernel process level transfer of user requested services |
US5319780A (en) * | 1987-10-19 | 1994-06-07 | International Business Machines Corporation | System that implicitly locks a subtree or explicitly locks a node based upon whether or not an explicit lock request is issued |
JP2625866B2 (en) | 1988-04-26 | 1997-07-02 | 日本電気株式会社 | Electronic device housing cooling structure |
US5043876A (en) | 1988-05-27 | 1991-08-27 | International Business Machines Corporation | N-level file shadowing and recovery in a shared file system |
US4937763A (en) | 1988-09-06 | 1990-06-26 | E I International, Inc. | Method of system state analysis |
US5065354A (en) | 1988-09-16 | 1991-11-12 | Compaq Computer Corporation | Queued posted-write disk write method with improved error handling |
US5067099A (en) | 1988-11-03 | 1991-11-19 | Allied-Signal Inc. | Methods and apparatus for monitoring system performance |
US4984272A (en) | 1988-11-30 | 1991-01-08 | At&T Bell Laboratories | Secure file handling in a computer operating system |
JPH02165241A (en) | 1988-12-19 | 1990-06-26 | Toshiba Corp | File access system |
US5222217A (en) | 1989-01-18 | 1993-06-22 | International Business Machines Corporation | System and method for implementing operating system message queues with recoverable shared virtual storage |
US5113442A (en) | 1989-03-06 | 1992-05-12 | Lachman Associates, Inc. | Method and apparatus for providing access control in a secure operating system |
US5144659A (en) | 1989-04-19 | 1992-09-01 | Richard P. Jones | Computer file protection system |
US5454099A (en) | 1989-07-25 | 1995-09-26 | International Business Machines Corporation | CPU implemented method for backing up modified data sets in non-volatile store for recovery in the event of CPU failure |
US5230047A (en) | 1990-04-16 | 1993-07-20 | International Business Machines Corporation | Method for balancing of distributed tree file structures in parallel computing systems to enable recovery after a failure |
JPH04130950A (en) | 1990-09-21 | 1992-05-01 | Toshiba Corp | Network system |
US5146588A (en) | 1990-11-26 | 1992-09-08 | Storage Technology Corporation | Redundancy accumulator for disk drive array memory |
US5321837A (en) | 1991-10-11 | 1994-06-14 | International Business Machines Corporation | Event handling mechanism having a process and an action association process |
GB9126779D0 (en) | 1991-12-17 | 1992-02-12 | Int Computers Ltd | Security mechanism for a computer system |
US5469566A (en) | 1992-03-12 | 1995-11-21 | Emc Corporation | Flexible parity generation circuit for intermittently generating a parity for a plurality of data channels in a redundant array of storage units |
US5448718A (en) | 1992-04-20 | 1995-09-05 | International Business Machines Corporation | Method and system for time zero backup session security |
JPH0619771A (en) * | 1992-04-20 | 1994-01-28 | Internatl Business Mach Corp <Ibm> | File management system of shared file by different kinds of clients |
US5335235A (en) | 1992-07-07 | 1994-08-02 | Digital Equipment Corporation | FIFO based parity generator |
US5596754A (en) * | 1992-10-29 | 1997-01-21 | Digital Equipment Corporation | Method for performing private lock management |
US5504883A (en) | 1993-02-01 | 1996-04-02 | Lsc, Inc. | Method and apparatus for insuring recovery of file control information for secondary storage systems |
US5522050A (en) | 1993-05-28 | 1996-05-28 | International Business Machines Corporation | Bus-to-bus bridge for a multiple bus information handling system that optimizes data transfers between a system bus and a peripheral bus |
US5963962A (en) | 1995-05-31 | 1999-10-05 | Network Appliance, Inc. | Write anywhere file-system layout |
DK0702815T3 (en) | 1993-06-03 | 2000-12-18 | Network Appliance Inc | Set up a file system for writing at any location |
DE69434381T2 (en) | 1993-06-04 | 2006-01-19 | Network Appliance, Inc., Sunnyvale | A method of parity representation in a RAID subsystem using nonvolatile memory |
ATE172309T1 (en) | 1993-07-01 | 1998-10-15 | Legent Corp | ARRANGEMENT AND METHOD FOR DISTRIBUTED DATA MANAGEMENT IN NETWORKED COMPUTER SYSTEMS |
US5572711A (en) | 1993-09-28 | 1996-11-05 | Bull Hn Information Systems Inc. | Mechanism for linking together the files of emulated and host system for access by emulated system users |
US5835953A (en) | 1994-10-13 | 1998-11-10 | Vinca Corporation | Backup system that takes a snapshot of the locations in a mass storage device that has been identified for updating prior to updating |
US5649152A (en) | 1994-10-13 | 1997-07-15 | Vinca Corporation | Method and system for providing a static snapshot of data stored on a mass storage system |
EP0713183A3 (en) | 1994-11-18 | 1996-10-02 | Microsoft Corp | Network independent file shadowing |
US6085234A (en) * | 1994-11-28 | 2000-07-04 | Inca Technology, Inc. | Remote file services network-infrastructure cache |
US5689701A (en) | 1994-12-14 | 1997-11-18 | International Business Machines Corporation | System and method for providing compatibility between distributed file system namespaces and operating system pathname syntax |
US5617568A (en) | 1994-12-14 | 1997-04-01 | International Business Machines Corporation | System and method for supporting file attributes on a distributed file system without native support therefor |
US5604862A (en) | 1995-03-14 | 1997-02-18 | Network Integrity, Inc. | Continuously-snapshotted protection of computer files |
US5696895A (en) | 1995-05-19 | 1997-12-09 | Compaq Computer Corporation | Fault tolerant multiple network servers |
US5761669A (en) | 1995-06-06 | 1998-06-02 | Microsoft Corporation | Controlling access to objects on multiple operating systems |
US5675782A (en) | 1995-06-06 | 1997-10-07 | Microsoft Corporation | Controlling access to objects on multiple operating systems |
US5603051A (en) | 1995-06-06 | 1997-02-11 | Hewlett-Packard Company | Input/output processor with a local memory providing shared resources for a plurality of input/output interfaces on an I/O bus |
US5628005A (en) * | 1995-06-07 | 1997-05-06 | Microsoft Corporation | System and method for providing opportunistic file access in a network environment |
US5729705A (en) | 1995-07-24 | 1998-03-17 | Symbios Logic Inc. | Method and apparatus for enhancing throughput of disk array data transfers in a controller |
US5720029A (en) | 1995-07-25 | 1998-02-17 | International Business Machines Corporation | Asynchronously shadowing record updates in a remote copy session using track arrays |
US5668958A (en) | 1995-09-12 | 1997-09-16 | International Business Machines Corporation | Heterogeneous filing system with common API and reconciled file management rules |
US5737744A (en) | 1995-10-13 | 1998-04-07 | Compaq Computer Corporation | Disk array controller for performing exclusive or operations |
US5740367A (en) * | 1995-11-03 | 1998-04-14 | Spilo; Michael L. | Method and apparatus for improving the throughput of a local area network |
US5742752A (en) | 1995-12-29 | 1998-04-21 | Symbios Logic Inc. | Method for performing a RAID stripe write operation using a drive XOR command set |
US5737523A (en) | 1996-03-04 | 1998-04-07 | Sun Microsystems, Inc. | Methods and apparatus for providing dynamic network file system client authentication |
US5819310A (en) | 1996-05-24 | 1998-10-06 | Emc Corporation | Method and apparatus for reading data from mirrored logical volumes on physical disk drives |
US5825877A (en) | 1996-06-11 | 1998-10-20 | International Business Machines Corporation | Support for portable trusted software |
US5828876A (en) * | 1996-07-31 | 1998-10-27 | Ncr Corporation | File system for a clustered processing system |
US6161165A (en) | 1996-11-14 | 2000-12-12 | Emc Corporation | High performance data path with XOR on the fly |
US6026474A (en) * | 1996-11-22 | 2000-02-15 | Mangosoft Corporation | Shared client-side web caching using globally addressable memory |
US5915087A (en) | 1996-12-12 | 1999-06-22 | Secure Computing Corporation | Transparent security proxy for unreliable message exchange protocols |
US5931935A (en) | 1997-04-15 | 1999-08-03 | Microsoft Corporation | File system primitive allowing reprocessing of I/O requests by multiple drivers in a layered driver I/O system |
US5876278A (en) | 1997-05-29 | 1999-03-02 | Cheng; Henry | Cooling device |
US6067541A (en) | 1997-09-17 | 2000-05-23 | Microsoft Corporation | Monitoring document changes in a file system of documents with the document change information stored in a persistent log |
US6275953B1 (en) * | 1997-09-26 | 2001-08-14 | Emc Corporation | Recovery from failure of a data processor in a network server |
US5996086A (en) | 1997-10-14 | 1999-11-30 | Lsi Logic Corporation | Context-based failover architecture for redundant servers |
US5999943A (en) | 1997-10-31 | 1999-12-07 | Oracle Corporation | Lob locators |
US5940828A (en) * | 1997-11-18 | 1999-08-17 | International Business Machines Corporation | Locking contention resolution for shared resources |
US6516351B2 (en) | 1997-12-05 | 2003-02-04 | Network Appliance, Inc. | Enforcing uniform file-locking for diverse file-locking protocols |
US6457130B2 (en) | 1998-03-03 | 2002-09-24 | Network Appliance, Inc. | File access control in a multi-protocol file server |
US5890959A (en) | 1998-03-31 | 1999-04-06 | Digital Equipment Corporation | High efficiency blower system with integral backflow preventor |
US6279011B1 (en) | 1998-06-19 | 2001-08-21 | Network Appliance, Inc. | Backup and restore for heterogeneous file server environment |
US6574591B1 (en) | 1998-07-31 | 2003-06-03 | Network Appliance, Inc. | File systems image transfer between dissimilar file systems |
US6654912B1 (en) | 2000-10-04 | 2003-11-25 | Network Appliance, Inc. | Recovery of file system data in file servers mirrored file system volumes |
-
1998
- 1998-10-21 US US09/176,599 patent/US6516351B2/en not_active Expired - Lifetime
- 1998-11-30 JP JP2000524743A patent/JP2001526426A/en active Pending
- 1998-11-30 WO PCT/US1998/025388 patent/WO1999030254A1/en active Application Filing
- 1998-11-30 EP EP98961834A patent/EP1034493A1/en not_active Withdrawn
- 1998-11-30 CA CA002312492A patent/CA2312492C/en not_active Expired - Fee Related
-
2002
- 2002-08-28 US US10/230,877 patent/US7293097B2/en not_active Expired - Fee Related
-
2008
- 2008-06-06 JP JP2008148947A patent/JP4430722B2/en not_active Expired - Fee Related
Patent Citations (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5261051A (en) * | 1989-08-14 | 1993-11-09 | Microsoft Corporation | Method and system for open file caching in a networked computer system |
Non-Patent Citations (2)
Title |
---|
BORR A J: "SecureShare: safe UNIX/Windows file sharing through multiprotocol locking", PROCEEDINGS OF THE 2ND USENIX WINDOWS NT SYMPOSIUM, PROCEEDINGS OF 2ND USENIX WINDOWS NT SYMPOSIUM, SEATTLE, WA, USA, 3-5 AUG. 1998, ISBN 1-880446-95-2, 1998, Berkeley, CA, USA, USENIX Assoc, USA, pages 117 - 126, XP002097387 * |
TANNER J: "CIFS: COMMON INTERNET FILE SYSTEM", UNIX REVIEW, vol. 31, February 1997 (1997-02-01), pages 31/32, 34, 36 - 41, XP000783952 * |
Cited By (22)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6751637B1 (en) | 1995-05-31 | 2004-06-15 | Network Appliance, Inc. | Allocating files in a file system integrated with a raid disk sub-system |
US6516351B2 (en) | 1997-12-05 | 2003-02-04 | Network Appliance, Inc. | Enforcing uniform file-locking for diverse file-locking protocols |
US7293097B2 (en) | 1997-12-05 | 2007-11-06 | Network Appliance, Inc. | Enforcing uniform file-locking for diverse file-locking protocols |
US6826615B2 (en) | 1999-10-14 | 2004-11-30 | Bluearc Uk Limited | Apparatus and method for hardware implementation or acceleration of operating system functions |
GB2394816A (en) * | 1999-10-18 | 2004-05-05 | Fisher Rosemount Systems Inc | Database server to provide concurrent access for multiple clients to the database uses a shared cache for holding copy of the data being accessed |
US7127460B2 (en) | 1999-10-18 | 2006-10-24 | Fisher-Rosemount Systems, Inc. | Accessing and updating a configuration database from distributed physical locations within a process control system |
GB2394816B (en) * | 1999-10-18 | 2004-08-11 | Fisher Rosemount Systems Inc | Accessing and updating a configuration database from distributed physical locations within a process control system |
JP2003513544A (en) * | 1999-11-04 | 2003-04-08 | ミラポイント インコーポレイテッド | Method and apparatus for electronic message communication system |
SG91903A1 (en) * | 2000-03-30 | 2002-10-15 | Ibm | File system locking |
EP1335286A3 (en) * | 2002-02-07 | 2004-08-18 | Fujitsu Limited | Control device for file resources in a network |
EP1335286A2 (en) * | 2002-02-07 | 2003-08-13 | Fujitsu Limited | Control device for file resources in a network |
US6952755B2 (en) | 2002-02-07 | 2005-10-04 | Fujitsu Limited | Control device for file resources in a network |
EP1335285A3 (en) * | 2002-02-07 | 2004-07-28 | Fujitsu Limited | Control device for file resources in a network |
EP1335285A2 (en) * | 2002-02-07 | 2003-08-13 | Fujitsu Limited | Control device for file resources in a network |
US9542310B2 (en) | 2002-11-01 | 2017-01-10 | Hitachi Data Systems Engineering UK Limited | File server node with non-volatile memory processing module coupled to cluster file server node |
US9753848B2 (en) | 2002-11-01 | 2017-09-05 | Hitachi Data Systems Engineering UK Limited | Apparatus for managing a plurality of root nodes for file systems |
EP1473632A2 (en) * | 2003-04-11 | 2004-11-03 | Sun Microsystems, Inc. | Generation interface for file interval lock |
EP1473632A3 (en) * | 2003-04-11 | 2007-05-30 | Sun Microsystems, Inc. | Generation interface for file interval lock |
JP2014520343A (en) * | 2011-06-24 | 2014-08-21 | ネットアップ,インコーポレイテッド | System and method for providing an integrated storage system that supports file / object duality |
EP2724236A4 (en) * | 2011-06-24 | 2015-09-16 | Netapp Inc | System and method for providing a unified storage system that supports file/object duality |
US9400802B2 (en) | 2011-06-24 | 2016-07-26 | Netapp, Inc. | System and method for providing a unified storage system that supports file/object duality |
EP3525127A4 (en) * | 2016-08-08 | 2020-05-20 | Namusoft Co., Ltd. | Method and system for blocking phishing or ransomware attack |
Also Published As
Publication number | Publication date |
---|---|
JP4430722B2 (en) | 2010-03-10 |
JP2001526426A (en) | 2001-12-18 |
JP2008305405A (en) | 2008-12-18 |
CA2312492C (en) | 2006-02-07 |
US6516351B2 (en) | 2003-02-04 |
US7293097B2 (en) | 2007-11-06 |
CA2312492A1 (en) | 1999-06-17 |
EP1034493A1 (en) | 2000-09-13 |
US20020019874A1 (en) | 2002-02-14 |
US20030065796A1 (en) | 2003-04-03 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
CA2312492C (en) | Multi-protocol unified file-locking | |
US6453354B1 (en) | File server system using connection-oriented protocol and sharing data sets among data movers | |
US6973455B1 (en) | File server system providing direct data sharing between clients with a server acting as an arbiter and coordinator | |
US6324581B1 (en) | File server system using file system storage, data movers, and an exchange of meta data among data movers for file locking and direct access to shared file systems | |
US7120631B1 (en) | File server system providing direct data sharing between clients with a server acting as an arbiter and coordinator | |
CA2445576C (en) | Filter driver for identifying disk files by analysis of content | |
Smalley et al. | Implementing SELinux as a Linux security module | |
US7822719B1 (en) | Multi-protocol lock manager | |
US5740370A (en) | System for opening cache file associated with designated file of file server only if the file is not subject to being modified by different program | |
US7010554B2 (en) | Delegation of metadata management in a storage system by leasing of free file system blocks and i-nodes from a file system owner | |
US7676526B1 (en) | System, method and computer program product for multi-level file-sharing by concurrent users | |
US6065065A (en) | Parallel computer system and file processing method using multiple I/O nodes | |
JPH0619771A (en) | File management system of shared file by different kinds of clients | |
US7293033B1 (en) | System and method for providing effective file-sharing in a computer system to allow concurrent multi-user access | |
JP4613023B2 (en) | Protocol-independent client-side caching system and method | |
EP0456920A2 (en) | Remote authentication and authorisation in a distributed data processing system | |
US7512990B2 (en) | Multiple simultaneous ACL formats on a filesystem | |
VanMeter et al. | Derived virtual devices: A secure distributed file system mechanism | |
Burns et al. | Semi-preemptible locks for a distributed file system | |
Borr | Secureshare: Safe unix/windows file sharing through multiprotocol locking | |
KR100604239B1 (en) | Method of operating a file server by enforcing a uniform file-locking semantics for diverse file-locking protocols, and a file server operated by the method | |
US7870239B1 (en) | Method and system for securing network access to dynamically updateable data stored in a data storage system | |
EP1204026A2 (en) | Mandatory locking mechanisms for unix file systems | |
Borr | 2nd USENIX Windows NT Symposium [Technical Program] | |
Honeyman | Synopsis of Distributed File System Protocols |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AK | Designated states |
Kind code of ref document: A1 Designated state(s): CA JP |
|
AL | Designated countries for regional patents |
Kind code of ref document: A1 Designated state(s): AT BE CH CY DE DK ES FI FR GB GR IE IT LU MC NL PT SE |
|
DFPE | Request for preliminary examination filed prior to expiration of 19th month from priority date (pct application filed before 20040101) | ||
REEP | Request for entry into the european phase |
Ref document number: 1998961834 Country of ref document: EP |
|
WWE | Wipo information: entry into national phase |
Ref document number: 1998961834 Country of ref document: EP |
|
121 | Ep: the epo has been informed by wipo that ep was designated in this application | ||
ENP | Entry into the national phase |
Ref document number: 2312492 Country of ref document: CA Ref document number: 2312492 Country of ref document: CA Kind code of ref document: A |
|
ENP | Entry into the national phase |
Ref document number: 2000 524743 Country of ref document: JP Kind code of ref document: A |
|
WWP | Wipo information: published in national office |
Ref document number: 1998961834 Country of ref document: EP |