Term
|
Definition
| keeps up with happenings in the system. if there is an error, then journaling can be used to help recover. |
|
|
Term
|
Definition
| consecutive sectors used to set up units. 1024, 2048, 4096 |
|
|
Term
|
Definition
| a collection of blocks. consecutive, sequential order. they are all the same size except for the last one. |
|
|
Term
|
Definition
|
|
Term
|
Definition
| ext3 has multiple superblocks throughout the drive. this way, the info we need is always close. this is faster than ntfs where we have to go to the mft to find indexing info. |
|
|
Term
|
Definition
| tells us block size, # of blocks, # of inodes. think of it as boot code |
|
|
Term
|
Definition
| points to the blocks that have been used in this block group. allocated. where block group starts |
|
|
Term
|
Definition
| which inodes are allocated which ones have been used. how to get to inode table within block group |
|
|
Term
|
Definition
| tells us where the indoes are. how to find the inode table itself |
|
|
Term
|
Definition
| repeat. first we have info about the block group, then the actual data is located after that. |
|
|
Term
|
Definition
| structure that stores info about the file. stores metadata about the file. one per file. stored in block groups. |
|
|
Term
|
Definition
|
|
Term
|
Definition
| table that allows us to address individual block groups. how to get to them. mft gave us ability to store data into it. gdt does not. it’s a true index |
|
|
Term
| each file has how many inodes |
|
Definition
|
|
Term
|
Definition
| we cannot write more data |
|
|
Term
|
Definition
| number of block groups. gdt located at the end of previous block groups because there is some unused space there. |
|
|
Term
| three types of linux files |
|
Definition
| directories, files, links |
|
|
Term
|
Definition
| file types for linux(three types = directories, files, links), permissions(three types), attributes, size, pointers to data blocks, times/dates (no date created in linux, only modified or accessed.) every inode entry points to a single file within that file group. |
|
|
Term
|
Definition
total inodes. how may inodes we have per partition
2. filesystem size (blocks)
3. reserved blocks(counts)
4. free block counter = how many blocks I have free on the system
5. free inode counter = how many inodes I have free on the system
6. number of first useful block. always 1. |
|
|
Term
|
Definition
Block number of block bitmap = where block bitmap is
2. Block number of inode bitmap = where inode bitmap is
3. block number of first inode table block = first inode of table
4.number of free blocks in the group = how many blocks we have avaliable in each group. inodes can fill up
5.number of free inodes in the group
6. number of directories in the group |
|
|
Term
|
Definition
File type and access rights = Is it a file, directory, or link?
2. owner ID = who owns the file.
3. File length in bytes
4. time of last file access
5.time that the inode last changed. why does this change? to update metadate.
6.time that the file content last changed |
|
|
Term
|
Definition
| then the knowledge of where the blocks start is also gone |
|
|
Term
| Any operating system can use any file system |
|
Definition
| as long as it knows how to use it (install drivers) |
|
|
Term
|
Definition
| a method where a user can puts its own userdefined attribute within mft record |
|
|
Term
|
Definition
| directly after boot code for each partition |
|
|
