CN112416862A - File management system and method based on partition operating system architecture - Google Patents
File management system and method based on partition operating system architecture Download PDFInfo
- Publication number
- CN112416862A CN112416862A CN202011376542.0A CN202011376542A CN112416862A CN 112416862 A CN112416862 A CN 112416862A CN 202011376542 A CN202011376542 A CN 202011376542A CN 112416862 A CN112416862 A CN 112416862A
- Authority
- CN
- China
- Prior art keywords
- partition
- application
- file system
- application partition
- operating system
- 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.)
- Granted
Links
- 238000005192 partition Methods 0.000 title claims abstract description 167
- 238000000034 method Methods 0.000 title claims abstract description 17
- 238000007726 management method Methods 0.000 claims description 24
- 230000003139 buffering effect Effects 0.000 description 4
- 238000002955 isolation Methods 0.000 description 4
- 238000010586 diagram Methods 0.000 description 2
- 230000005540 biological transmission Effects 0.000 description 1
- 238000004891 communication Methods 0.000 description 1
- 238000013523 data management Methods 0.000 description 1
Images
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/11—File system administration, e.g. details of archiving or snapshots
-
- 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/172—Caching, prefetching or hoarding of files
-
- 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/18—File system types
- G06F16/1847—File system types specifically adapted to static storage, e.g. adapted to flash memory or SSD
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Data Mining & Analysis (AREA)
- Databases & Information Systems (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
- Storage Device Security (AREA)
Abstract
The invention provides a file management system and method based on a partition operating system architecture, wherein the partition operating system architecture comprises the following components: a core operating system and at least one application partition; wherein each application partition comprises: the system comprises a user application and a partition operating system, wherein the user application runs on the partition operating system; each partition operating system comprises a file system, and the file system manages at least one logical disk; the file system of the first application partition is mounted with a logical disk of the second application partition, and at least one logical disk of the second application partition only has read permission; the first application partition and the second application partition are application partitions of the at least one application partition, the first application partition having read data requirements for the second application partition. The problem of safe parallel access of files faced by a partitioned file system can be solved.
Description
Technical Field
The invention belongs to the technical field of computer system software, and particularly relates to a file management system and method based on a partition operating system architecture.
Background
The partition file system should ensure isolation of partition data and access to shared data. And the parallel operation of partition files and the parallel reading and writing of files should be ensured during design. Conventional file systems can only ensure write-exclusive or multi-partition read operations, which are not allowed with respect to simultaneous read operations of write operations. A Partition Operating System (POS) relates to multi-partition parallel operation, and how to solve data isolation and sharing of a file system and ensure parallel access (single-partition write, multi-partition read) of multi-partition file data is a problem that needs to be solved urgently.
Disclosure of Invention
The invention provides a file management system and method based on a partition operating system architecture, which solve the problem of file security parallel access faced by a partition operating system-oriented file system.
One aspect of the present invention provides a file management system based on a partition operating system architecture, where the partition operating system architecture includes: a core operating system and at least one application partition; wherein,
each application partition includes: the system comprises a user application and a partition operating system, wherein the user application runs on the partition operating system;
each partition operating system comprises a file system, and the file system manages at least one logical disk;
the file system of the first application partition is mounted with a logical disk of a second application partition, and at least one logical disk of the second application partition only has read permission;
the first application partition and the second application partition are application partitions of at least one application partition, the first application partition having read data requirements for the second application partition.
Optionally, when receiving an access request to the mounted logical disk of the second application partition, the file system of the first application partition determines, to the core operating system, whether there is an update on the mounted logical disk of the second application partition;
if the access request does not exist, performing reading operation from the read buffer area of the mounted logic disk of the second application partition according to the access request;
and if so, performing read operation from the physical equipment area corresponding to the mounted logical disk of the second application partition according to the access request.
Optionally, when the file system receives a write request, the file system completes a write operation in a write buffer according to the write request;
and updating the writing buffer area to be remote updating.
Optionally, the first application partition and the second application partition have the same file system.
Optionally, the user application sends the request to the file system through a file system partition secure access interface (P2 interface) of ARINC653 PART2 standard.
Another aspect of the present invention provides a file management method based on a partition operating system architecture, which is applied to the file management system according to any one of the above aspects; the method comprises the following steps:
when the file system receives an access request, determining whether the authority exists according to a logic disk to be accessed and request operation carried by the access request;
if yes, executing; if not, execution is denied.
Optionally, when the file system of the first application partition receives an access request to the mounted logical disk of the second application partition; when the request operation carried by the access request is a read operation, determining that the permission exists; and when the request operation carried by the access request is write operation, determining that no authority exists.
Optionally, the file management method further includes:
when the file system of the first application partition receives an access request to the mounted logical disk of the second application partition, determining whether the mounted logical disk of the second application partition is updated or not from a core operating system;
if the access request does not exist, performing reading operation from the read buffer area of the mounted logic disk of the second application partition according to the access request;
and if so, performing read operation from the physical equipment area corresponding to the mounted logical disk of the second application partition according to the access request.
Optionally, the file management method further includes:
when the file system receives a write request, the file system completes write operation in a write buffer area according to the write request; wherein the update of the write buffer is a remote update.
Optionally, the first application partition and the second application partition have the same file system.
The invention provides a file management system and method based on a partition operating system architecture, wherein the partition operating system architecture comprises the following components: a core operating system and at least one application partition; wherein each application partition comprises: the system comprises a user application and a partition operating system, wherein the user application runs on the partition operating system; each partition operating system comprises a file system, and the file system manages at least one logical disk; the file system of the first application partition is mounted with a logical disk of the second application partition, and at least one logical disk of the second application partition only has read permission; the first application partition and the second application partition are application partitions of the at least one application partition, the first application partition having read data requirements for the second application partition. The problem of safe parallel access of files faced by a partitioned file system can be solved.
Drawings
FIG. 1 is a block diagram of a partitioned file system architecture;
FIG. 2 is a schematic diagram of partitioned parallel read and write operations;
FIG. 3 is a flow chart illustrating the execution of partition file operations.
Detailed Description
To further clarify the embodiments of the present invention, the detailed description will be further exemplified with reference to the accompanying drawings.
The following explains a file management system and method based on a partition operating system architecture according to the present invention with reference to the drawings.
Referring to fig. 1-3, the present invention provides a file management system and method based on a partition operating system architecture, comprising the following steps:
and S1, placing the file systems in the application partitions, wherein each application partition maintains one file system to ensure the isolation of partition data.
Each application partition is provided with a Partition Operating System (POS) for providing operating system services for the partitions, each application partition is respectively provided with a file system of the application partition, partition data isolation safety can be achieved, each application partition is provided with an independent file system, the file system divides equipment into a plurality of logic disks for management, each application partition is allocated with at least one logic disk of the application partition, at least one logic disk with sharing requirements can be configured in the plurality of logic disks, and the logic disks with the sharing requirements can allow other partitions to read. When the device data has no sharing requirement, the device data respectively processes the partition file request of the device data for the logical disk to which the device data belongs. And when the sharing requirement exists, executing the file request of the logical disk aiming at the sharing requirement.
It will be appreciated that reading the file system of the partition of the current partition of the logical disk having sharing requirements needs to be consistent with the file system of the current partition.
And S2, ensuring the consistency of data through state transfer between the shared partitions.
According to the file system architecture constructed in S1, when there is a shared data request between partitions, it is allowed that only the logical disks related to the shared data request in another partition have read permission (that is, the logical disks not related to the shared data request do not have read permission, and all the logical disks do not have write permission, and the file system divides the storage device into multiple logical disks for independent management).
When sharing the logical disks of other partitions, the partitions to be shared should mount the same file system first, and the logical disks to be shared should be mounted in the local partition in a read-only mode.
Each partition has its own independent file system buffer, which causes inconsistency of partition shared data, and partition communication is performed between partitions in a form of write status notification in order to ensure consistency of data read by each partition.
And S3, separating read-write management and read-write buffering by the file system, and ensuring the parallelism of read-write operation.
In order to ensure parallel access of reading and writing, the file system should ensure that when the reading and writing operations are executed, the branch management of the file system is relatively isolated and is not influenced by each other, the failure of the writing operation does not influence the reading operation, and the reading operation is supported while the writing operation is executed. For this purpose, the file system manages the read-write branches from the logical layer by using read management and write management respectively. The read-write management and the read-write buffering are separated, so that the read operation can be executed while the write operation is ensured, and the parallelism of the read-write operation is ensured.
And S4, executing the safe file operation by the application partition through the P2 interface.
The P2 interface is a set of file system partition safe access interface meeting ARINC653 PART2 standard, file operation is executed between partitions through the P2 interface, safe access check between partitions is executed according to access authority in the partitions, the file operation is executed through the partition file system without directly returning error through the authority check and after the authority check.
And S5, executing the partition file operation.
When the exclusive equipment and the partitions execute the read-write operation request, each partition firstly judges the access authority of the logical disk, directly returns the access authority without the authority, and directly performs data management on the partition file system with the authority.
And when the partition executes a read-write operation request, each partition firstly judges the access authority of the logical disk, and directly returns without the authority, when the partition with the authority reads and shares other partition logical disks, the partition with the authority inquires the write state of the volume to which the partition belongs, if the write state is changed, the shared data is directly read from the device, and if the write state is not changed, the shared data is read from the buffer of the partition.
Parallel read-write flow of the file system: when a shared data request exists between the partitions, one process executes write operation, other processes execute read operation, and access to a write buffer is provided when the write operation is executed and access to a read buffer is provided when the read operation is executed. When the write operation is executed, the transaction log is written, the updated content is written into a newly distributed physical block, and after the atomic operation is finished and the transaction state is submitted, the pointer of the write buffer root node is assigned to the pointer of the root node of the read management tree, namely the read management tree is updated. The two trees are independent in buffering, and the parallelism of read-write operation is ensured.
The specific working steps of the file system security access architecture for the partition operating system are as follows:
step 1, placing a file system in each application partition, wherein each partition has a relatively independent file system;
step 2, ensuring the consistency of shared data through state transmission among the shared partitions;
and 3, separating the file system through read-write management and read-write buffering to ensure the parallelism of read-write operation.
And 4, the application partition executes file operation through a P2 secure access interface meeting ARINC653 PART2 standard.
And 5, executing the file operation according to the partition file operation execution flow.
Claims (10)
1. A file management system based on a partitioned operating system architecture, the partitioned operating system architecture comprising: a core operating system and at least one application partition; wherein,
each application partition includes: the system comprises a user application and a partition operating system, wherein the user application runs on the partition operating system;
each partition operating system comprises a file system, and the file system manages at least one logical disk;
the file system of the first application partition is mounted with a logical disk of a second application partition, and at least one logical disk of the second application partition only has read permission;
the first application partition and the second application partition are application partitions of at least one application partition, the first application partition having read data requirements for the second application partition.
2. The file system of claim 1, wherein the file system of the first application partition, upon receiving an access request to the mounted logical disk of the second application partition, determines to a core operating system whether there is an update to the mounted logical disk of the second application partition;
if the access request does not exist, performing reading operation from the read buffer area of the mounted logic disk of the second application partition according to the access request;
and if so, performing read operation from the physical equipment area corresponding to the mounted logical disk of the second application partition according to the access request.
3. The file system according to claim 1, wherein when the file system receives a write request, the file system completes a write operation in a write buffer according to the write request;
and updating the writing buffer area to be remote updating.
4. The file system of claim 1, wherein the first application partition and the second application partition have the same file system.
5. The file system of claim 1, wherein the user application sends the request to the file system via a file system partition secure access interface of the ARINC653 PART2 standard.
6. A file management method based on a partition operating system architecture, which is applied to the file management system according to any one of claims 1-5; the method comprises the following steps:
when the file system receives an access request, determining whether the authority exists according to a logic disk to be accessed and request operation carried by the access request;
if yes, executing; if not, execution is denied.
7. The method of claim 6, wherein when the file system of the first application partition receives an access request to the mounted logical disk of the second application partition; when the request operation carried by the access request is a read operation, determining that the permission exists; and when the request operation carried by the access request is write operation, determining that no authority exists.
8. The method of claim 6, further comprising:
when the file system of the first application partition receives an access request to the mounted logical disk of the second application partition, determining whether the mounted logical disk of the second application partition is updated or not from a core operating system;
if the access request does not exist, performing reading operation from the read buffer area of the mounted logic disk of the second application partition according to the access request;
and if so, performing read operation from the physical equipment area corresponding to the mounted logical disk of the second application partition according to the access request.
9. The method of claim 6, further comprising:
when the file system receives a write request, the file system completes write operation in a write buffer area according to the write request; wherein the update of the write buffer is a remote update.
10. The method of claim 6, wherein the first application partition and the second application partition have the same file system.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN202011376542.0A CN112416862B (en) | 2020-11-30 | 2020-11-30 | File management system and method based on partition operating system architecture |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN202011376542.0A CN112416862B (en) | 2020-11-30 | 2020-11-30 | File management system and method based on partition operating system architecture |
Publications (2)
Publication Number | Publication Date |
---|---|
CN112416862A true CN112416862A (en) | 2021-02-26 |
CN112416862B CN112416862B (en) | 2024-06-18 |
Family
ID=74828975
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CN202011376542.0A Active CN112416862B (en) | 2020-11-30 | 2020-11-30 | File management system and method based on partition operating system architecture |
Country Status (1)
Country | Link |
---|---|
CN (1) | CN112416862B (en) |
Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN102664923A (en) * | 2012-03-30 | 2012-09-12 | 浪潮电子信息产业股份有限公司 | Method for realizing shared storage pool by utilizing Linux global file system |
KR101643729B1 (en) * | 2015-10-28 | 2016-07-29 | 주식회사 인피니플럭스 | System and method of data managing for time base data backup, restoring, and mounting |
CN109445861A (en) * | 2018-10-18 | 2019-03-08 | 深圳市网心科技有限公司 | System start method, device, computer installation and storage medium |
CN109542831A (en) * | 2018-10-28 | 2019-03-29 | 西南电子技术研究所(中国电子科技集团公司第十研究所) | Airborne platform multi-core virtual multidomain treat-ment system |
KR20200109547A (en) * | 2019-03-13 | 2020-09-23 | 김한규 | Method and network attached storage apparatus for sharing files between computers |
-
2020
- 2020-11-30 CN CN202011376542.0A patent/CN112416862B/en active Active
Patent Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN102664923A (en) * | 2012-03-30 | 2012-09-12 | 浪潮电子信息产业股份有限公司 | Method for realizing shared storage pool by utilizing Linux global file system |
KR101643729B1 (en) * | 2015-10-28 | 2016-07-29 | 주식회사 인피니플럭스 | System and method of data managing for time base data backup, restoring, and mounting |
CN109445861A (en) * | 2018-10-18 | 2019-03-08 | 深圳市网心科技有限公司 | System start method, device, computer installation and storage medium |
CN109542831A (en) * | 2018-10-28 | 2019-03-29 | 西南电子技术研究所(中国电子科技集团公司第十研究所) | Airborne platform multi-core virtual multidomain treat-ment system |
KR20200109547A (en) * | 2019-03-13 | 2020-09-23 | 김한규 | Method and network attached storage apparatus for sharing files between computers |
Non-Patent Citations (2)
Title |
---|
MAHADEV SATYANARAYANAN: "Scalable, Secure, and Highly Available Distributed File Access", COMPUTER, vol. 23, no. 5, pages 9 - 21 * |
郭亚锋: "用bash脚本原生读写macOS下NTFS文件", 网络安全和信息化, no. 8, pages 98 - 100 * |
Also Published As
Publication number | Publication date |
---|---|
CN112416862B (en) | 2024-06-18 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US9558207B1 (en) | Versioning of database partition maps | |
CN108509462B (en) | Method and device for synchronizing activity transaction table | |
US20210326168A1 (en) | Autonomous cell-based control plane for scalable virtualized computing | |
CA2644997C (en) | Providing an address format compatible with different addressing formats used for addressing different sized address spaces | |
CN113396407A (en) | System and method for augmenting database applications using blockchain techniques | |
US11080253B1 (en) | Dynamic splitting of contentious index data pages | |
US20210173572A1 (en) | System and method for managing volumes of data in a block storage system | |
CN106326229B (en) | File storage method and device of embedded system | |
US20120323851A1 (en) | Distributed, asynchronous and fault-tolerant storage system | |
JP4175083B2 (en) | Storage device management computer and program | |
CN113760901A (en) | Data processing method, device, equipment and storage medium | |
CN108304142A (en) | A kind of data managing method and device | |
US7996631B1 (en) | System and method for accessing storage devices attached to a stateless client | |
CN117113380A (en) | Embedded virtual file system design method based on domestic operating system | |
CN112416862B (en) | File management system and method based on partition operating system architecture | |
CN115964444A (en) | Cloud native distributed multi-tenant database implementation method and system | |
KR20120063946A (en) | Memory apparatus for collective volume memory and metadate managing method thereof | |
US11121981B1 (en) | Optimistically granting permission to host computing resources | |
JP2002312210A (en) | Method for providing disc array with file system access | |
JP5031538B2 (en) | Data distribution method, data distribution program, and parallel database system | |
JP2001014201A (en) | Shared file system | |
US11853319B1 (en) | Caching updates appended to an immutable log for handling reads to the immutable log | |
KR101440605B1 (en) | User device having file system gateway unit and method for accessing to stored data | |
EP3314390B1 (en) | Returning coherent data in response to a failure of a storage device when a single input/output request spans two storage devices | |
JP2005234919A (en) | Cluster memory file system |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
PB01 | Publication | ||
PB01 | Publication | ||
SE01 | Entry into force of request for substantive examination | ||
SE01 | Entry into force of request for substantive examination | ||
GR01 | Patent grant | ||
GR01 | Patent grant |