CN103345482A - Network storage system and file access conflict processing method thereof - Google Patents
Network storage system and file access conflict processing method thereof Download PDFInfo
- Publication number
- CN103345482A CN103345482A CN2013102453529A CN201310245352A CN103345482A CN 103345482 A CN103345482 A CN 103345482A CN 2013102453529 A CN2013102453529 A CN 2013102453529A CN 201310245352 A CN201310245352 A CN 201310245352A CN 103345482 A CN103345482 A CN 103345482A
- Authority
- CN
- China
- Prior art keywords
- file
- client access
- storage device
- access device
- magnetic disk
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Images
Abstract
The invention discloses a network storage system. The network storage system comprises a network additional storage device and more than one client access device, wherein the client access devices are used for accessing shared files on the network additional storage device through a network communication protocol. The network additional storage device comprises a file sharing unit and a file storage unit, wherein the file sharing unit is used for storing the shared files on a disk medium of the network additional storage device, and providing file operation interfaces for the file sharing unit to call, and the file sharing unit is used for receiving file operation requests from a plurality of client access devices, carrying out inspection to judge whether operations are in conflict according to the types of the file operations, informing the client access devices that the operations are in conflict when the operations are in conflict, accessing the shared files of the file storage unit by calling the file operation interfaces when the operations are not in conflicts, and informing the client access devices of the executive results of the operations. The invention further discloses a file access conflict processing method applied to the network storage system. According to the technical scheme, the conflict problem caused by the phenomenon that a plurality of users use one shared file together can be solved.
Description
Technical field
The application relates to network store system, this network store system is used for share and access and the co-operate of file, when share and access and co-operate, can allow a plurality of users to use simultaneously and edit same file, realized the coordination of conflict and merge handling by network store system then; Relate in particular to a kind of network store system and file access conflict processing method thereof.
Background technology
Network additive storage device is a kind of network storage equipment commonly used, it directly is attached to magnetic disk media on the network, then can be for main frame by the (CIFS of common the Internet file system, Common Internet File System), network file system(NFS) (NFS, Network File System) etc. procotol is visited the data of its storage, is applied to sharing of organizational structure's data usually.
But this class network store system is when share and access, particularly a plurality of users are common when using same shared file, there are many restrictions, comprise and do not allow to write simultaneously this shared file, behind existing opened this file of user, do not allow another user's deletion, rename or mobile these files.These restrictions can cause shared file when the cooperation office, have inconvenience, comprise that a plurality of people operate a certain file simultaneously, after perhaps conflict appears in operation, can not effectively handle automatically, need a large amount of manual behavior interventions.And, if effectively do not conflict treatment mechanism, also will there be potential safety hazard, for example, certain user is revising a file, and in the time of after closing, another user carries out the file deletion action, then might delete the amended file of up-to-date user by mistake.
Summary of the invention
The application provides a kind of network store system and file access conflict processing method thereof, can effectively solve the collision problem when a plurality of users are common to use a shared file.
A kind of network store system that the embodiment of the present application provides comprises network additive storage device and more than one client access device, and client access device is used for by the shared file on the network communication protocol accesses network additional memory devices,
Described network additive storage device comprises file sharing unit and file storage unit;
File storage unit is used for storing shared file at the magnetic disk media of network additive storage device, and provides the file operation interface to call for file sharing unit;
File sharing unit is used for receiving the file operation requests from a plurality of client access device, and operate according to the type checking of file operation and whether conflict, if, this operating collision of notice client access device; Otherwise, by calling the shared file of described file operation interface accessing file storage unit, with the result notification client access device of operation execution;
Described client access device comprises:
The file view module is used for showing shared file at file view;
The file buffering module is for the shared file of the network additive storage device that buffer memory had been visited on the local disk medium of client access device;
The file synchronization module: be used for file view to the file buffering module in the shared file of buffer memory carry out file operation, according to described file operation spanned file operation requests, described file operation requests is synchronized in the file sharing unit of network additive storage device.
Preferably, the file operation interface that provides of described file storage unit comprises one of following or its combination in any:
The document creation interface is used for creating a new file or folder at the magnetic disk media of network additive storage device;
The File Open interface is used for opening a file that has existed at the magnetic disk media of network additive storage device, is used for writing or reading data;
File is write incoming interface, is used for writing file content at the magnetic disk media of network additive storage device to an opened file;
The file fetch interface is used for reading file content at the magnetic disk media of network additive storage device to an opened file;
The file delete interface is used for the file or folder of magnetic disk media deletion at network additive storage device;
File rename interface is used for the title at a file or folder of magnetic disk media modification of network additive storage device;
File moves interface, is used at mobile file or folder to a reposition of the magnetic disk media of network additive storage device.
Preferably, described file sharing unit further comprises:
Receive subelement, be used for receiving the file operation requests from client access device;
The formation subelement is used for the maintenance documentation operation queue, and when the collision detection subelement detects the operation that receives the file operation requests correspondence that subelement receives and do not conflict, this document operation requests is inserted in the file operation formation;
The collision detection subelement, whether the type checking operation for the file operation requests that receives according to the reception subelement conflicts, if, check whether this conflict can merge, if not, this document operation is not inserted in the file operation formation of formation subelement maintenance, and this operating collision of notice client access device; Then notify client access device to merge this conflict if can merge; If there is not conflict, file operation requests is inserted in the file operation formation of formation subelement maintenance;
Carry out subelement, be used for according to file operation requests, calling the corresponding interface of file storage unit, complete operation from file operation requests of bottom taking-up of the file operation formation of formation subelement maintenance; Result notification client access device with the operation execution.
Preferably, whether the described inspection operation that receives the file operation requests correspondence that subelement receives conflicts and comprises:
Check whether this document operation file pointed is present in the file operation formation;
Whether the type checking operation according to file operation conflicts;
More than two judged results if any any for being, then have conflict, have only when being not, then do not have conflict.
Preferably, receive being operating as of file operation requests correspondence that subelement receives when newly-built, if the collision detection subelement finds that there has been file of the same name in file storage unit, described operating collision and can not merging then; If the collision detection subelement find the parent folder at this document place in the file storage unit or more the file on upper strata do not have described operating collision and can merging then;
Being operating as when revising content of the file operation requests correspondence that the reception subelement receives, content was revised by other client access device before this is subsynchronous if the collision detection subelement is found the file storage unit respective file, then this operating collision and cannot merging; If the collision detection subelement find the parent folder at this document place in the file storage unit or more the file on upper strata do not have described operating collision and can merging then;
Receive file operation requests correspondence that subelement receives be operating as rename the time, if the collision detection subelement finds in the file storage unit that new filename has existed or the respective file content was revised by other client access device before this is subsynchronous, this operating collision and cannot merging then; If the collision detection subelement find the parent folder at this document place in the file storage unit or more the file on upper strata do not have described operating collision and can merging then;
Receive file operation requests correspondence that subelement receives be operating as deletion the time, if the collision detection subelement finds that the respective file content is modified in the file storage unit, this operating collision and cannot merging then; If the collision detection subelement find the parent folder at this document place in the file storage unit or more the file on upper strata do not have described operating collision and can merging then;
Receive being operating as of file operation requests correspondence that subelement receives when mobile, if the collision detection subelement finds that new file exists in the file storage unit, this operating collision and cannot merging then; , if the collision detection subelement finds that file content is modified in the file storage unit, this operating collision and cannot merging then;
If the collision detection subelement find the parent folder at this document place in the file storage unit or more the file on upper strata do not have described operating collision and can merging then.
Preferably, described collision detection subelement is further used for the setting according to first client access device, before the revised file content file is locked;
During file was locked, if there are other client access device except first client access device to require modification, movement, deletion or rename this document, then the collision detection subelement was judged the operating collision of other client access device.
The embodiment of the present application also provides the conflict processing method of the file access in a kind of network store system, comprising:
The shared file of A, the client access device network additive storage device that buffer memory had been visited on the local disk medium; In file view, the shared file of buffer memory in the file buffering module is carried out file operation, according to described file operation spanned file operation requests, described file operation requests is synchronized to network additive storage device;
B, network additive storage device receive the file operation requests from a plurality of client access device, and operate according to the type checking of file operation and whether conflict, if, this operating collision of notice client access device; Otherwise, by the shared file on the magnetic disk media that calls file operation interface accessing network additive storage device, with the result notification client access device of operation execution.
Preferably, the file operation interface comprises one of following or its combination in any:
The document creation interface is used for creating a new file or folder at the magnetic disk media of network additive storage device;
The File Open interface is used for opening a file that has existed at the magnetic disk media of network additive storage device, is used for writing or reading data;
File is write incoming interface, and what be used for network additive storage device writes file content at magnetic disk media to an opened file;
The file fetch interface, what be used for network additive storage device reads file content at magnetic disk media to an opened file;
The file delete interface, what be used for network additive storage device deletes a file or folder at magnetic disk media;
File rename interface is used for the title at a file or folder of magnetic disk media modification of network additive storage device;
File moves interface, is used at mobile file or folder to a reposition of the magnetic disk media of network additive storage device.
Preferably, described step B comprises:
B1, whether operation conflicts according to the type checking of the file operation requests that receives, if, check whether this conflict can merge, if not, this document operation be not inserted in the file operation formation, and notify client access device this operating collision; Then notify client access device to merge this conflict if can merge; If there is not conflict, file operation requests is inserted in the file operation formation;
B2, take out a file operation requests from the bottom of file operation formation, according to file operation requests, call the corresponding interface of file storage unit, complete operation; Result notification client access device with the operation execution.
Preferably, whether described type checking according to file operation is operated to conflict and is comprised:
Check whether this document operation file pointed is present in the file operation formation;
Whether the type checking operation according to file operation conflicts;
More than two judged results if any any for being, then have conflict, have only when being not, then do not have conflict.
Preferably, the being operating as when newly-built of file operation requests correspondence that receives, if find to have had file of the same name on the magnetic disk media of network additive storage device, described operating collision and can not merging then; If find the parent folder at this document place on the magnetic disk media of network additive storage device or more the file on upper strata do not have described operating collision and can merging then;
Being operating as when revising content of the file operation requests correspondence that receives, if find that the respective file content was revised by other client access device on the magnetic disk media of network additive storage device before this is subsynchronous, this operating collision and cannot merging then; If find the parent folder at this document place on the magnetic disk media of network additive storage device or more the file on upper strata do not have described operating collision and can merging then;
The file operation requests correspondence that receives be operating as rename the time, if find on the magnetic disk media of network additive storage device that new filename has existed or the respective file content was revised by other client access device before this is subsynchronous, this operating collision and cannot merging then; If find the parent folder at this document place on the magnetic disk media of network additive storage device or more the file on upper strata do not have described operating collision and can merging then;
The file operation requests correspondence that receives be operating as when deletion, if find that the respective file content is modified on the magnetic disk media of network additive storage device, this operating collision and cannot merging then; If find the parent folder at this document place on the magnetic disk media of network additive storage device or more the file on upper strata do not have described operating collision and can merging then;
Being operating as when mobile of the file operation requests correspondence that receives, if find that new file exists on the magnetic disk media of network additive storage device, this operating collision and cannot merging then; If find that file content is modified on the magnetic disk media of network additive storage device, this operating collision and cannot merging then; If find the parent folder at this document place on the magnetic disk media of network additive storage device or more the file on upper strata do not have described operating collision and can merging then.
Preferably, this method further comprises:
According to the setting of first client access device, before the revised file content file that will be modified on the magnetic disk media of network additive storage device is being locked;
During file is locked, if there are other client access device except first client access device to require modification, movement, deletion or rename this document, then judge the operating collision of other client access device.
As can be seen from the above technical solutions, client access device is carried out buffer memory to shared file, and according to the operating result spanned file operation requests to the shared file in the buffer memory; Network additive storage device is received the file operation requests from a plurality of client access device, operates according to the type checking of file operation and whether conflicts, and the processing that conflicts accordingly.By using the present techniques scheme, can a plurality of client access device in network store system visit and operate same shared file simultaneously; Can allow newly-built, revised file content, deletion, rename, mobile same shared file.
Description of drawings
The network store system block diagram that Fig. 1 provides for the embodiment of the present application;
Fig. 2 is the block diagram of file storage unit 104 shown in Figure 1;
Fig. 3 is the synoptic diagram of file operation sequence;
Fig. 4 is the processing flow chart of file sharing unit 103 shown in Figure 1;
The processing flow chart of the network store system that Fig. 5 provides for the embodiment of the present application;
Fig. 6 is file synchronization sequence synoptic diagram.
Embodiment
Clearer for the know-why, characteristics and the technique effect that make the present techniques scheme, below in conjunction with specific embodiment the present techniques scheme is described in detail.
In order to realize that shared file can be simultaneously operated, the application provides a kind of file access conflict treatment mechanism, system chart as shown in Figure 1, the network store system that embodiment own provides comprises network additive storage device 101 and client access device 102, and client access device 102 is by the shared file on the network communication protocol accesses network additional memory devices 101.
Network additive storage device 101 comprises file sharing unit 103 and file storage unit 104, file storage unit 104 is used for leaving shared file in magnetic disk media, file sharing unit 103 is used for receiving the request of client access device 102, the shared file of access file storage unit 104.
As shown in Figure 2, in the embodiment of the present application, file storage unit 104 is based on the storage management system of magnetic disk media, and provides as one of lower interface or its combination in any and called by file sharing unit 103 visits:
The document creation interface is the request that file storage unit receives file sharing unit, is used for creating a new file or folder at magnetic disk media.
The File Open interface is the request that file storage unit receives file sharing unit, is used for opening a file that has existed at magnetic disk media, is used for writing or reading data.
File is write incoming interface, is the request that file storage unit receives file sharing unit, is used for writing file content to magnetic disk media to an opened file.
The file fetch interface is the request that file storage unit receives file sharing unit, is used for reading file content to magnetic disk media to an opened file.
The file delete interface is the request that file storage unit receives file sharing unit, is used at file or folder of magnetic disk media deletion.
File rename interface is the request that file storage unit receives file sharing unit, is used for revising at magnetic disk media the title of a file or folder.
File moves interface, is the request that file storage unit receives file sharing unit, is used at mobile file or folder to a reposition of magnetic disk media.
The filename of newly-built operation is newly-built file name, and action type is newly-built, and operation information is that new Object is file or folder, and creation-time.
The filename of opening operation is the file name that will open, and action type is for opening, and operation information does not have.
The filename of write operation is the file name that will write, and action type is for writing, and operation information is the displaced position of writing, data block to be written, the time of file of client access device.
The filename of read operation is the file name that will read, and action type is for reading the displaced position that operation information is read and length.
The filename of deletion action is the file name that will open, and action type is deletion, and operation information does not have.
The filename of rename operation is the file name that will revise, and action type is rename, and operation information is new title.
The filename of move operation is the file name that will move, and action type is for mobile, and operation information is the reposition that moves to.
Described file sharing unit 103 may further include:
Receive subelement, be used for receiving the file operation requests from client access device 102;
The formation subelement is used for the maintenance documentation operation queue, and when the collision detection subelement detects the operation that receives the file operation requests correspondence that subelement receives and do not conflict, this document operation requests is inserted in the file operation formation;
The collision detection subelement, whether conflict for the operation that checks the file operation requests correspondence that the reception subelement receives, if, this document operation is not inserted in the file operation formation of formation subelement maintenance, and this operating collision of notice client access device; Otherwise, file operation requests is inserted in the file operation formation of formation subelement maintenance;
Carry out subelement, be used for according to file operation requests, calling the corresponding interface of file storage unit, complete operation from file operation requests of bottom taking-up of the file operation formation of formation subelement maintenance; Result notification client access device 102 with the operation execution.
Whether the operation of the file operation requests correspondence that described inspection reception subelement receives conflicts and comprises:
Check whether this document operation file pointed is present in formation;
Whether the type checking operation according to file operation conflicts;
More than two judged results if any any for being, then have conflict, have only when being not, then do not have conflict.
Receive being operating as of file operation requests correspondence that subelement receives when newly-built, if the collision detection subelement finds that there has been file of the same name in file storage unit, described operating collision and can not merging then; If the collision detection subelement find the parent folder at this document place in the file storage unit or more the file on upper strata do not have described operating collision and can merging then;
Being operating as when revising content of the file operation requests correspondence that the reception subelement receives, content was revised by other client access device before this is subsynchronous if the collision detection subelement is found the file storage unit respective file, then this operating collision and cannot merging; If the collision detection subelement find the parent folder at this document place in the file storage unit or more the file on upper strata do not have described operating collision and can merging then;
Receive file operation requests correspondence that subelement receives be operating as rename the time, if the collision detection subelement finds in the file storage unit that new filename has existed or the respective file content was revised by other client access device before this is subsynchronous, this operating collision and cannot merging then; If the collision detection subelement find the parent folder at this document place in the file storage unit or more the file on upper strata do not have described operating collision and can merging then;
Receive file operation requests correspondence that subelement receives be operating as deletion the time, if the collision detection subelement finds that the respective file content is modified in the file storage unit, this operating collision and cannot merging then; If the collision detection subelement find the parent folder at this document place in the file storage unit or more the file on upper strata do not have described operating collision and can merging then;
Receive being operating as of file operation requests correspondence that subelement receives when mobile, if the collision detection subelement finds that new file exists in the file storage unit, this operating collision and cannot merging then; , if the collision detection subelement finds that file content is modified in the file storage unit, this operating collision and cannot merging then;
If the collision detection subelement find the parent folder at this document place in the file storage unit or more the file on upper strata do not have described operating collision and can merging then.
Described collision detection subelement is further used for the setting according to first client access device, before the revised file content file is locked;
During file was locked, if there are other client access device except first client access device to require modification, movement, deletion or rename this document, then the collision detection subelement was judged the operating collision of other client access device.
The treatment scheme of file sharing unit 103 comprises as shown in Figure 4:
Step 401: file sharing unit receives the file operation requests from client access device;
Step 402: prepare file operation requests is inserted into the file operation formation;
Step 403: check whether this document operation file pointed is present in formation, if go to step 406, otherwise, execution in step 404.
Step 404: whether the type checking operation according to file operation conflicts;
If conflict then is not inserted in the formation, and this operating collision of notice client access device;
If do not conflict execution in step 405.
Step 405: this document operation requests is inserted in the formation.
Step 406: insert failure, this document operation is not inserted in the formation, and this operating collision of notice client access device.
According to file operation requests, call the corresponding interface of file storage unit 104, complete operation;
Result notification client access device 102 with the operation execution.
The file view module: this part be used for to show shared file, in order to used and operate shared file by the user.
The file buffering module: this part is used for the shared file of the network additive storage device that buffer memory had been visited on the local disk medium of client access device, the file buffering module can promote the fluency that file view shows and operates on the one hand, on the other hand, be to realize key of operating the conflict treatment mechanism of a certain file simultaneously of the present invention.
The file synchronization module: be used for file view to the file buffering module in the shared file of buffer memory carry out file operation, and according to described file operation spanned file operation requests, described file operation requests is synchronized in the file sharing unit of network additive storage device.
In the embodiment of the present application, the file synchronization module of client access device 102 is passed through network communication protocol, communicate with the file sharing unit 103 of network additive storage device 101, file operation requests is sent to file sharing unit, carrying out file operation by file sharing unit 103 then handles, its flow process comprises as shown in Figure 5:
Step 501: the user uses the file view module of client access device 102 to carry out file operation, comprise newly-built, read, write, deletion, rename, movement;
Step 502: client access device 102 with the operation in the file view and result cache to the file buffering module;
Step 503: client access device 102 is according to file operation, the spanned file operation requests;
Step 504: after treating that operation is finished in the local cache, client access device 102 is called the file synchronization module, and file operation is inserted in the file synchronization formation;
Step 505: client access device 102 is called the file synchronization module, to the file sharing unit 103 transmission file operation requests of network additive storage device 101;
Step 506: after file sharing unit 103 receives file operation requests, carry out inspection conflict flow process shown in Figure 4, whether decision operation conflicts, if, execution in step 507, otherwise execution in step 508.
Step 507: if the conflict of file sharing unit return, then client access device allows the file synchronization module wait for, returns step 505.
Step 508: request sends successfully, and operation is finished.
The file synchronization module is used for safeguarding a file synchronization formation that as shown in Figure 6, it is similar to the file operation formation of file sharing unit, so no longer describe in detail.
In file access, the embodiment of the present application provides two kinds of conflict treatment mechanisms: the treatment mechanism of conflicting automatically and manual control hazard mechanism.
In automatic conflict treatment mechanism, if when the file operation of a certain client access device is newly-built, judge that conflict and processing mode comprise:
Newly-built certain file of client access device and when being synchronized to file sharing unit, file sharing unit finds that there has been file of the same name in file storage unit, then notifies corresponding client end device this document to be the conflict file.
Newly-built certain file of client access device and when being synchronized to file sharing unit, file sharing unit is found in the file storage unit, the parent folder at this document place (perhaps more the file on upper strata) is not because rename, deletion, mobilely exist, then notify the corresponding client end device to merge this conflict, create parent folder earlier, then synchronous newly-built file.
In the treatment mechanism of conflicting automatically, if the file operation of a certain client access device is when revising content, judge that conflict and processing mode are as follows:
After client access device is revised a certain file content, with amended file synchronization during to file sharing unit, file sharing unit discovery file storage unit respective file content was revised by other client access device before this is subsynchronous, then notify the corresponding client end device, this document is the conflict file.
After client access device is revised a certain file content, with amended file synchronization during to file sharing unit, file sharing unit is found in the file storage unit, the parent folder at this document place (perhaps more the file on upper strata) is not because rename, deletion, mobilely exist, then notify the corresponding client end device, merge this conflict, create parent folder earlier, then this file and the newly file content of modification synchronously.
In automatic conflict treatment mechanism, if when the file operation of a certain client access device is rename, judge that conflict and processing mode are as follows:
During the rename file and when being synchronized to file sharing unit, file sharing unit finds that the new filename of file storage unit exists, then notifies the clients corresponding access means, and this document is the conflict file.
During the rename file and when being synchronized to file sharing unit, file sharing unit finds that file storage unit respective file content is modified, and then notifies the corresponding client end device, and this document is the conflict file.
During the rename file and when being synchronized to file sharing unit, file sharing unit is found in the file storage unit, the parent folder at this document place (perhaps more the file on upper strata) is not because rename, deletion, mobilely exist, then notify the corresponding client end device, merge this conflict, create parent folder earlier, then the file after the rename synchronously.
In automatic conflict treatment mechanism, if the file operation of a certain client access device during for deletion, judges that conflict and processing mode are as follows:
When deleting certain file and being synchronized to file sharing unit, file sharing unit finds that file storage unit respective file content is modified, and then notifies the corresponding client end device, and this document can not be deleted, and cancels the deletion action of client terminal device.
When deleting certain file and being synchronized to file sharing unit, file sharing unit is found in the file storage unit, the parent folder at this document or this document place (perhaps more the file on upper strata) is not because rename, deletion, mobilely exist, then notify the corresponding client end device, ignore this synchronous operation.
In automatic conflict treatment mechanism, if the file operation of a certain client access device when mobile, judges that conflict and processing mode are as follows:
During mobile certain file and when being synchronized to file sharing unit, file sharing unit finds that the new file of file storage unit exists, then notifies the corresponding client end device, and this document is the conflict file.
During mobile certain file and when being synchronized to file sharing unit, file sharing unit finds that the original content of file storage unit correspondence is modified, and then notifies the corresponding client end device, and this document can not move, and cancels the move operation of client terminal device.
During mobile certain file and when being synchronized to file sharing unit, file sharing unit is found in the file storage unit, the parent folder at new file place (perhaps more the file on upper strata) is not because rename, deletion, mobilely exist, then notify the corresponding client end device, merge this conflict, create parent folder earlier, then with the file after the moved further.
In manual control hazard mechanism:
Client access device provides file locking operation, before the revised file content, and can first lock file;
Behind the lock file, to read this document, other client access device can not be revised this document to other client access device between lockup period only;
After the client access device of lock file has been revised file content, can remove the locking of this document, after the releasing, other client access device then can be revised this document.
By the present invention, can reach following effect:
1. in network store system, same shared file can be visited and operate to a plurality of client access device simultaneously.
2. can allow newly-built, revised file content, deletion, rename, mobile same shared file.
3. automatic conflict treatment mechanism can be provided, when simplifying a plurality of client access device and operating a shared file simultaneously, can identify and handle conflict automatically.
4. the treatment mechanism of conflicting automatically is to guarantee file security, in case find to exist in the file storage unit file that upgrades, the file in the overlay file storage unit not then.
5. manual control hazard mechanism is provided, simplifies a plurality of client access device whiles when reading a shared file, only allow a client access device to revise this file.
The above only is the application's preferred embodiment; not in order to limit the application's protection domain; all within the spirit and principle of present techniques scheme, any modification of making, be equal to replacement, improvement etc., all should be included within the scope of the application's protection.
Claims (12)
1. a network store system comprises network additive storage device and more than one client access device, and client access device is used for it is characterized in that by the shared file on the network communication protocol accesses network additional memory devices,
Described network additive storage device comprises file sharing unit and file storage unit;
File storage unit is used for storing shared file at the magnetic disk media of network additive storage device, and provides the file operation interface to call for file sharing unit;
File sharing unit is used for receiving the file operation requests from a plurality of client access device, and operate according to the type checking of file operation and whether conflict, if, this operating collision of notice client access device; Otherwise, by calling the shared file of described file operation interface accessing file storage unit, with the result notification client access device of operation execution;
Described client access device comprises:
The file view module is used for showing shared file at file view;
The file buffering module is for the shared file of the network additive storage device that buffer memory had been visited on the local disk medium of client access device;
The file synchronization module: be used for file view to the file buffering module in the shared file of buffer memory carry out file operation, according to described file operation spanned file operation requests, described file operation requests is synchronized in the file sharing unit of network additive storage device.
2. system according to claim 1 is characterized in that, the file operation interface that described file storage unit provides comprises one of following or its combination in any:
The document creation interface is used for creating a new file or folder at the magnetic disk media of network additive storage device;
The File Open interface is used for opening a file that has existed at the magnetic disk media of network additive storage device, is used for writing or reading data;
File is write incoming interface, is used for writing file content at the magnetic disk media of network additive storage device to an opened file;
The file fetch interface is used for reading file content at the magnetic disk media of network additive storage device to an opened file;
The file delete interface is used for the file or folder of magnetic disk media deletion at network additive storage device;
File rename interface is used for the title at a file or folder of magnetic disk media modification of network additive storage device;
File moves interface, is used at mobile file or folder to a reposition of the magnetic disk media of network additive storage device.
3. system according to claim 1 is characterized in that, described file sharing unit further comprises:
Receive subelement, be used for receiving the file operation requests from client access device;
The formation subelement is used for the maintenance documentation operation queue, and when the collision detection subelement detects the operation that receives the file operation requests correspondence that subelement receives and do not conflict, this document operation requests is inserted in the file operation formation;
The collision detection subelement, whether the type checking operation for the file operation requests that receives according to the reception subelement conflicts, if, check whether this conflict can merge, if not, this document operation is not inserted in the file operation formation of formation subelement maintenance, and this operating collision of notice client access device; Then notify client access device to merge this conflict if can merge; If there is not conflict, file operation requests is inserted in the file operation formation of formation subelement maintenance;
Carry out subelement, be used for according to file operation requests, calling the corresponding interface of file storage unit, complete operation from file operation requests of bottom taking-up of the file operation formation of formation subelement maintenance; Result notification client access device with the operation execution.
4. system according to claim 3 is characterized in that, whether the operation of the file operation requests correspondence that described inspection reception subelement receives conflicts and comprise:
Check whether this document operation file pointed is present in the file operation formation;
Whether the type checking operation according to file operation conflicts;
More than two judged results if any any for being, then have conflict, have only when being not, then do not have conflict.
5. system according to claim 4, it is characterized in that, receive being operating as of file operation requests correspondence that subelement receives when newly-built, if the collision detection subelement finds that there has been file of the same name in file storage unit, described operating collision and can not merging then; If the collision detection subelement find the parent folder at this document place in the file storage unit or more the file on upper strata do not have described operating collision and can merging then;
Being operating as when revising content of the file operation requests correspondence that the reception subelement receives, content was revised by other client access device before this is subsynchronous if the collision detection subelement is found the file storage unit respective file, then this operating collision and cannot merging; If the collision detection subelement find the parent folder at this document place in the file storage unit or more the file on upper strata do not have described operating collision and can merging then;
Receive file operation requests correspondence that subelement receives be operating as rename the time, if the collision detection subelement finds in the file storage unit that new filename has existed or the respective file content was revised by other client access device before this is subsynchronous, this operating collision and cannot merging then; If the collision detection subelement find the parent folder at this document place in the file storage unit or more the file on upper strata do not have described operating collision and can merging then;
Receive file operation requests correspondence that subelement receives be operating as deletion the time, if the collision detection subelement finds that the respective file content is modified in the file storage unit, this operating collision and cannot merging then; If the collision detection subelement find the parent folder at this document place in the file storage unit or more the file on upper strata do not have described operating collision and can merging then;
Receive being operating as of file operation requests correspondence that subelement receives when mobile, if the collision detection subelement finds that new file exists in the file storage unit, this operating collision and cannot merging then; , if the collision detection subelement finds that file content is modified in the file storage unit, this operating collision and cannot merging then;
If the collision detection subelement find the parent folder at this document place in the file storage unit or more the file on upper strata do not have described operating collision and can merging then.
6. system according to claim 4 is characterized in that, described collision detection subelement is further used for the setting according to first client access device, before the revised file content file is locked;
During file was locked, if there are other client access device except first client access device to require modification, movement, deletion or rename this document, then the collision detection subelement was judged the operating collision of other client access device.
7. the file access conflict processing method in the network store system is characterized in that, comprising:
The shared file of A, the client access device network additive storage device that buffer memory had been visited on the local disk medium; In file view, the shared file of buffer memory in the file buffering module is carried out file operation, according to described file operation spanned file operation requests, described file operation requests is synchronized to network additive storage device;
B, network additive storage device receive the file operation requests from a plurality of client access device, and operate according to the type checking of file operation and whether conflict, if, this operating collision of notice client access device; Otherwise, by the shared file on the magnetic disk media that calls file operation interface accessing network additive storage device, with the result notification client access device of operation execution.
8. method according to claim 7 is characterized in that, the file operation interface comprises one of following or its combination in any:
The document creation interface is used for creating a new file or folder at the magnetic disk media of network additive storage device;
The File Open interface is used for opening a file that has existed at the magnetic disk media of network additive storage device, is used for writing or reading data;
File is write incoming interface, and what be used for network additive storage device writes file content at magnetic disk media to an opened file;
The file fetch interface, what be used for network additive storage device reads file content at magnetic disk media to an opened file;
The file delete interface, what be used for network additive storage device deletes a file or folder at magnetic disk media;
File rename interface is used for the title at a file or folder of magnetic disk media modification of network additive storage device;
File moves interface, is used at mobile file or folder to a reposition of the magnetic disk media of network additive storage device.
9. method according to claim 7 is characterized in that, described step B comprises:
B1, whether operation conflicts according to the type checking of the file operation requests that receives, if, check whether this conflict can merge, if not, this document operation be not inserted in the file operation formation, and notify client access device this operating collision; Then notify client access device to merge this conflict if can merge; If there is not conflict, file operation requests is inserted in the file operation formation;
B2, take out a file operation requests from the bottom of file operation formation, according to file operation requests, call the corresponding interface of file storage unit, complete operation; Result notification client access device with the operation execution.
10. method according to claim 9 is characterized in that, whether described type checking operation according to file operation conflicts and comprise:
Check whether this document operation file pointed is present in the file operation formation;
Whether the type checking operation according to file operation conflicts;
More than two judged results if any any for being, then have conflict, have only when being not, then do not have conflict.
11. system according to claim 10 is characterized in that, the being operating as when newly-built of file operation requests correspondence that receives, if find to have had file of the same name on the magnetic disk media of network additive storage device, and described operating collision and can not merging then; If find the parent folder at this document place on the magnetic disk media of network additive storage device or more the file on upper strata do not have described operating collision and can merging then;
Being operating as when revising content of the file operation requests correspondence that receives, if find that the respective file content was revised by other client access device on the magnetic disk media of network additive storage device before this is subsynchronous, this operating collision and cannot merging then; If find the parent folder at this document place on the magnetic disk media of network additive storage device or more the file on upper strata do not have described operating collision and can merging then;
The file operation requests correspondence that receives be operating as rename the time, if find on the magnetic disk media of network additive storage device that new filename has existed or the respective file content was revised by other client access device before this is subsynchronous, this operating collision and cannot merging then; If find the parent folder at this document place on the magnetic disk media of network additive storage device or more the file on upper strata do not have described operating collision and can merging then;
The file operation requests correspondence that receives be operating as when deletion, if find that the respective file content is modified on the magnetic disk media of network additive storage device, this operating collision and cannot merging then; If find the parent folder at this document place on the magnetic disk media of network additive storage device or more the file on upper strata do not have described operating collision and can merging then;
Being operating as when mobile of the file operation requests correspondence that receives, if find that new file exists on the magnetic disk media of network additive storage device, this operating collision and cannot merging then; If find that file content is modified on the magnetic disk media of network additive storage device, this operating collision and cannot merging then; If find the parent folder at this document place on the magnetic disk media of network additive storage device or more the file on upper strata do not have described operating collision and can merging then.
12. method according to claim 10 is characterized in that, this method further comprises:
According to the setting of first client access device, before the revised file content file that will be modified on the magnetic disk media of network additive storage device is being locked;
During file is locked, if there are other client access device except first client access device to require modification, movement, deletion or rename this document, then judge the operating collision of other client access device.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2013102453529A CN103345482A (en) | 2013-06-20 | 2013-06-20 | Network storage system and file access conflict processing method thereof |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2013102453529A CN103345482A (en) | 2013-06-20 | 2013-06-20 | Network storage system and file access conflict processing method thereof |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN103345482A true CN103345482A (en) | 2013-10-09 |
Family
ID=49280277
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN2013102453529A Pending CN103345482A (en) | 2013-06-20 | 2013-06-20 | Network storage system and file access conflict processing method thereof |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN103345482A (en) |
Cited By (17)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103678525A (en) * | 2013-11-29 | 2014-03-26 | 创新科软件技术（深圳）有限公司 | Method for sharing one file by multiple users |
| CN104519132A (en) * | 2014-12-19 | 2015-04-15 | 西安理邦科学仪器有限公司 | Client application handling method and client application handling system of distributed monitoring network |
| CN104539659A (en) * | 2014-12-09 | 2015-04-22 | 华迪计算机集团有限公司 | Multi-user-file exchange and sharing method and device based on NAS |
| CN104579756A (en) * | 2014-12-19 | 2015-04-29 | 西安理邦科学仪器有限公司 | Method and system for managing client operation of distribution type monitoring network |
| CN104935552A (en) * | 2014-03-18 | 2015-09-23 | 安一恒通（北京）科技有限公司 | File opening method and device thereof |
| CN105631350A (en) * | 2015-03-05 | 2016-06-01 | 西安酷派软件科技有限公司 | Data operation method, data operation apparatus and terminal |
| CN105812432A (en) * | 2014-12-31 | 2016-07-27 | 北京金山云网络技术有限公司 | Cloud file processing method and device |
| CN105872077A (en) * | 2016-05-11 | 2016-08-17 | 广西科技大学 | Cross-system file sharing method based on SMB protocol |
| CN105979018A (en) * | 2016-07-29 | 2016-09-28 | 上海爱数信息技术股份有限公司 | State maintaining method and system for file lock |
| CN106375359A (en) * | 2015-07-23 | 2017-02-01 | 腾讯科技（深圳）有限公司 | Method, device and system for processing application data |
| WO2017028688A1 (en) * | 2015-08-14 | 2017-02-23 | 阿里巴巴集团控股有限公司 | Method, device and system for reading and writing files |
| CN106708941A (en) * | 2016-11-24 | 2017-05-24 | 厦门亿力吉奥信息科技有限公司 | Multi-task on-line collaborative editing method for power grid |
| CN107220010A (en) * | 2016-03-21 | 2017-09-29 | 北大方正集团有限公司 | A kind of layout file passes version safety locking method and apparatus |
| CN111385255A (en) * | 2018-12-28 | 2020-07-07 | 北京金山云网络技术有限公司 | Asynchronous call implementation method and device, server and server cluster |
| CN113490929A (en) * | 2019-01-30 | 2021-10-08 | 思杰系统有限公司 | File conflict detection |
| US11275530B2 (en) | 2015-12-30 | 2022-03-15 | Huawei Technologies Co., Ltd. | Method, system, and related device for NAS data access |
| CN117527825A (en) * | 2023-10-26 | 2024-02-06 | 青岛展诚科技有限公司 | Multi-channel synchronous shared data system for realizing integrated circuit design based on nfs protocol |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1074300A (en) * | 1991-12-31 | 1993-07-14 | 国际商业机器公司 | Cursor lock region |
| EP1260902A2 (en) * | 2001-05-14 | 2002-11-27 | K-Plex Inc. | Information sharing method and apparatus using object oriented technology |
| CN1804836A (en) * | 2005-01-14 | 2006-07-19 | 微软公司 | Method and system for synchronizing multiple user revisions to a shared object |
| CN101655845A (en) * | 2008-08-21 | 2010-02-24 | 北京亿企通信息技术有限公司 | Method for processing documents in multi-person collaboration working environment |
| US20100198871A1 (en) * | 2009-02-03 | 2010-08-05 | Hewlett-Packard Development Company, L.P. | Intuitive file sharing with transparent security |
| CN102325169A (en) * | 2011-08-22 | 2012-01-18 | 盛乐信息技术（上海）有限公司 | Network file system supporting sharing and cooperation and method thereof |
-
2013
- 2013-06-20 CN CN2013102453529A patent/CN103345482A/en active Pending
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1074300A (en) * | 1991-12-31 | 1993-07-14 | 国际商业机器公司 | Cursor lock region |
| EP1260902A2 (en) * | 2001-05-14 | 2002-11-27 | K-Plex Inc. | Information sharing method and apparatus using object oriented technology |
| CN1804836A (en) * | 2005-01-14 | 2006-07-19 | 微软公司 | Method and system for synchronizing multiple user revisions to a shared object |
| CN101655845A (en) * | 2008-08-21 | 2010-02-24 | 北京亿企通信息技术有限公司 | Method for processing documents in multi-person collaboration working environment |
| US20100198871A1 (en) * | 2009-02-03 | 2010-08-05 | Hewlett-Packard Development Company, L.P. | Intuitive file sharing with transparent security |
| CN102325169A (en) * | 2011-08-22 | 2012-01-18 | 盛乐信息技术（上海）有限公司 | Network file system supporting sharing and cooperation and method thereof |
Cited By (32)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103678525B (en) * | 2013-11-29 | 2017-09-22 | 创新科软件技术（深圳）有限公司 | A kind of method of multiple users share identical file |
| CN103678525A (en) * | 2013-11-29 | 2014-03-26 | 创新科软件技术（深圳）有限公司 | Method for sharing one file by multiple users |
| CN104935552A (en) * | 2014-03-18 | 2015-09-23 | 安一恒通（北京）科技有限公司 | File opening method and device thereof |
| CN104935552B (en) * | 2014-03-18 | 2018-03-06 | 安一恒通（北京）科技有限公司 | File open method and device |
| CN104539659A (en) * | 2014-12-09 | 2015-04-22 | 华迪计算机集团有限公司 | Multi-user-file exchange and sharing method and device based on NAS |
| CN104539659B (en) * | 2014-12-09 | 2018-06-08 | 华迪计算机集团有限公司 | Multi-user's exchange files sharing method and device based on NAS storages |
| CN104579756B (en) * | 2014-12-19 | 2018-10-23 | 西安理邦科学仪器有限公司 | The client actions management method and system of distributed monitoring network |
| CN104519132A (en) * | 2014-12-19 | 2015-04-15 | 西安理邦科学仪器有限公司 | Client application handling method and client application handling system of distributed monitoring network |
| CN104579756A (en) * | 2014-12-19 | 2015-04-29 | 西安理邦科学仪器有限公司 | Method and system for managing client operation of distribution type monitoring network |
| CN104519132B (en) * | 2014-12-19 | 2019-04-12 | 西安理邦科学仪器有限公司 | The client computer application processing method and system of distributed monitoring network |
| CN105812432A (en) * | 2014-12-31 | 2016-07-27 | 北京金山云网络技术有限公司 | Cloud file processing method and device |
| CN105812432B (en) * | 2014-12-31 | 2019-03-12 | 北京金山云网络技术有限公司 | Cloud document processing method and device |
| CN105631350B (en) * | 2015-03-05 | 2018-07-24 | 西安酷派软件科技有限公司 | Data manipulation method, data operation device and terminal |
| CN105631350A (en) * | 2015-03-05 | 2016-06-01 | 西安酷派软件科技有限公司 | Data operation method, data operation apparatus and terminal |
| CN106375359B (en) * | 2015-07-23 | 2019-11-26 | 腾讯科技（深圳）有限公司 | A kind of processing method using data, device and system |
| CN106375359A (en) * | 2015-07-23 | 2017-02-01 | 腾讯科技（深圳）有限公司 | Method, device and system for processing application data |
| CN106469150B (en) * | 2015-08-14 | 2019-10-08 | 阿里巴巴集团控股有限公司 | File read/write method, device and system |
| WO2017028688A1 (en) * | 2015-08-14 | 2017-02-23 | 阿里巴巴集团控股有限公司 | Method, device and system for reading and writing files |
| US10338917B2 (en) | 2015-08-14 | 2019-07-02 | Alibaba Group Holding Limited | Method, apparatus, and system for reading and writing files |
| CN106469150A (en) * | 2015-08-14 | 2017-03-01 | 阿里巴巴集团控股有限公司 | File read/write method, device and system |
| US11275530B2 (en) | 2015-12-30 | 2022-03-15 | Huawei Technologies Co., Ltd. | Method, system, and related device for NAS data access |
| CN107220010B (en) * | 2016-03-21 | 2019-12-24 | 北大方正集团有限公司 | Method and device for safely locking page file transfer |
| CN107220010A (en) * | 2016-03-21 | 2017-09-29 | 北大方正集团有限公司 | A kind of layout file passes version safety locking method and apparatus |
| CN105872077A (en) * | 2016-05-11 | 2016-08-17 | 广西科技大学 | Cross-system file sharing method based on SMB protocol |
| CN105979018A (en) * | 2016-07-29 | 2016-09-28 | 上海爱数信息技术股份有限公司 | State maintaining method and system for file lock |
| CN106708941B (en) * | 2016-11-24 | 2019-07-30 | 厦门亿力吉奥信息科技有限公司 | The online synergic editing method of power grid multitask |
| CN106708941A (en) * | 2016-11-24 | 2017-05-24 | 厦门亿力吉奥信息科技有限公司 | Multi-task on-line collaborative editing method for power grid |
| CN111385255A (en) * | 2018-12-28 | 2020-07-07 | 北京金山云网络技术有限公司 | Asynchronous call implementation method and device, server and server cluster |
| CN111385255B (en) * | 2018-12-28 | 2022-05-06 | 北京金山云网络技术有限公司 | Asynchronous call implementation method and device, server and server cluster |
| CN113490929A (en) * | 2019-01-30 | 2021-10-08 | 思杰系统有限公司 | File conflict detection |
| CN117527825A (en) * | 2023-10-26 | 2024-02-06 | 青岛展诚科技有限公司 | Multi-channel synchronous shared data system for realizing integrated circuit design based on nfs protocol |
| CN117527825B (en) * | 2023-10-26 | 2024-04-02 | 青岛展诚科技有限公司 | Multi-channel synchronous shared data system for realizing integrated circuit design based on nfs protocol |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN103345482A (en) | Network storage system and file access conflict processing method thereof | |
| US20200128073A1 (en) | Synchronization of permissioned content in cloud-based environments | |
| US9396245B2 (en) | Race condition handling in a system which incrementally updates clients with events that occurred in a cloud-based collaboration platform | |
| US20190155789A1 (en) | Method and apparatus for synchronization of items with read-only permissions in a cloud-based environment | |
| US10599671B2 (en) | Conflict resolution, retry condition management, and handling of problem files for the synchronization client to a cloud-based platform | |
| US10110656B2 (en) | Systems and methods for providing shell communication in a cloud-based platform | |
| US20160359859A1 (en) | System For Secure File Access | |
| US20140195485A1 (en) | File system monitoring in a system which incrementally updates clients with events that occurred in a cloud-based collaboration platform | |
| US10289607B2 (en) | Architecture for management of digital files across distributed network | |
| JP7150830B2 (en) | Content management system workflow functionality enforced by the client device | |
| US20140164315A1 (en) | System And Method For The Creation Of, Automatic Synchronization Of, And Access To Multi-Cloud Documents That Reside Across Dissimilar Clouds, Devices, And Operating Systems And That Are Accessed By Multiple Dissimilar Applications | |
| CN103020257B (en) | The implementation method of data manipulation and device | |
| US11061623B2 (en) | Preventing excessive hydration in a storage virtualization system | |
| CN104391695B (en) | A kind of method and its device that control is synchronized by external equipment | |
| US10417179B2 (en) | Method for managing files and apparatus using the same | |
| CN101944107B (en) | Document management method | |
| US20180039790A1 (en) | System and method to provide document management on a public document system | |
| CN104462403B (en) | File truncation method and apparatus | |
| JP2015153111A (en) | Image forming apparatus and control method of the same | |
| US8498622B2 (en) | Data processing system with synchronization policy | |
| US8909875B1 (en) | Methods and apparatus for storing a new version of an object on a content addressable storage system | |
| CN102932468B (en) | Share data access method | |
| CN109426548A (en) | Prevent the method and system that dirty virtual machine is run on undesirable host server | |
| RU2446460C1 (en) | Method and system for filtering web content | |
| JP2007066200A (en) | System, server, method and program for document management |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| CB02 | Change of applicant information |
Address after: 201112 Shanghai, Minhang District, United Airlines route 1188, building second layer A-1 unit 8 Applicant after: SHANGHAI EISOO INFORMATION TECHNOLOGY CO., LTD. Address before: 200072 room 3, building 840, No. 101 Middle Luochuan Road, Shanghai, Zhabei District Applicant before: Shanghai Eisoo Software Co.,Ltd. |
|
| COR | Change of bibliographic data | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20131009 |
|
| RJ01 | Rejection of invention patent application after publication |