Presentation is loading. Please wait.

Presentation is loading. Please wait.

File Management System Simulation

Similar presentations


Presentation on theme: "File Management System Simulation"— Presentation transcript:

1 File Management System Simulation
Instructor: Dr. Ramesh K. Karne COSC Group #1 Group member:

2 Contents Introduction Motivation Background Flow Chart Function Demo
Conclusion

3 Introduction Our file management simulation project creates 12 operations to be used in the Linux System. The source code is written in C. Signal Handling for interrupts like unexpected break (ctrl+c). Do implementation of log file to keep record of all the events.

4 Motivation File management is an important process for the operating system. A good file management system could enable the users to find files easily, efficiently , quickly and also make it easy for the file storage and backup. Therefore, we want to do a file management simulation project and implement a bunch of basic operations such as read/write to a file, create/change directory .etc.

5 Background(EXT2) The EXT2 file system, like a lot of the file systems, is built on the premise that the data held in files is kept in data blocks. These data blocks are all of the same length and, although that length can vary between different EXT2 file systems the block size of a particular EXT2 file system is set when it is created (using mke2fs ). Every file's size is rounded up to an integral number of blocks. If the block size is 1024 bytes, then a file of 1025 bytes will occupy two 1024 byte blocks. Unfortunately this means that on average you waste half a block per file. Usually in computing you trade off CPU usage for memory and disk space utilisation. In this case Linux, along with most operating systems, trades off a relatively inefficient disk usage in order to reduce the workload on the CPU. Not all of the blocks in the file system hold data, some must be used to contain the information that describes the structure of the file system. EXT2 defines the file system topology by describing each file in the system with an inode data structure. An inode describes which blocks the data within a file occupies as well as the access rights of the file, the file's modification times and the type of the file. Every file in the EXT2 file system is described by a single inode and each inode has a single unique number identifying it. The inodes for the file system are all kept together in inode tables. EXT2 directories are simply special files (themselves described by inodes) which contain pointers to the inodes of their directory entries.

6 Background(inode) Mode--This holds two pieces of information; what does this inode describe and the permissions that users have to it. For EXT2, an inode can describe one of file, directory, symbolic link, block device, character device or FIFO. Owner info--The user and group identifiers of the owners of this file or directory. This allows the file system to correctly allow the right sort of accesses Size--The size of the file in bytes, Timestamps--The time that the inode was created and the last time that it was modified

7 Flow Chart

8 Create Directory

9 Create File

10 Read File

11 Remove File

12 Function Demo

13 Create Directory

14 Create File

15 Remove File

16 Display File

17 Read File

18 Write File

19 Show status of the File

20 Conclusion In this project, we simulated Linux OS functions: mkdir, cd, cd .., create, ls, rm, write, cat, read, stat, df, exit, help. Moreover, we have a deep understanding about what is file system in the Linux and how to implement in the C source code. Our project code is based on C program. After this project, we learned a lot coding skills: structure design, debugging etc. Team work – Thanks for all team members’ hard working.

21 End Thank you!


Download ppt "File Management System Simulation"

Similar presentations


Ads by Google