Lines Matching full:filesystem
7 <Title>The extended-2 filesystem overview</Title>
22 the ext2 filesystem. It was written in summer 95, while I was working on the
23 <Literal remap="tt">ext2 filesystem editor project (EXT2ED)</Literal>.
28 design aspects of the the ext2 filesystem. This document is a result of an
109 users. If you use Linux, chances are that you are using the ext2 filesystem.
119 The ext2 filesystem is still under development. I will document here
123 ext2 filesystem in Linux 1.3, so stay tuned.
129 <Title>A filesystem - Why do we need it?</Title>
137 A <Literal remap="tt">filesystem</Literal> consists of two word - <Literal remap="tt">file</Literal> and <Literal remap="tt">system</Literal>.
152 the filesystem, as I understand it, is to make it easy for us to update and
160 wherever we wish. It is the task of the filesystem management code to store
167 Second Extended Filesystem.
176 When Linux was first developed, it supported only one filesystem - The
177 <Literal remap="tt">Minix</Literal> filesystem. Today, Linux has the ability to support several
179 between the kernel and the filesystem code - The Virtual File System (VFS).
184 request to the proper filesystem management code. I haven't learned much of
195 In order to ease management, the ext2 filesystem logically divides the disk
197 can be allocated. Each block in the filesystem can be <Literal remap="tt">allocated</Literal> or
210 the filesystem.
215 block</Literal>. The resulting situation is that the filesystem is managed as a
218 much of the filesystem management reduces to management of a single blocks
228 Each file in the filesystem is reserved a special <Literal remap="tt">inode</Literal>. I don't want
281 is used to allocate / deallocate each specific inode in the filesystem.
292 when the filesystem is created.
327 filesystem's <Literal remap="tt">superblock</Literal>, which will be explained later.
400 An inode is a main resource in the ext2 filesystem. It is used for various
422 Each file, for example, will allocate one inode from the filesystem
427 An ext2 filesystem has a total number of available inodes which is determined
428 while creating the filesystem. When all the inodes are used, for example, you
430 be free blocks on the filesystem.
434 Each inode takes up 128 bytes in the filesystem. By default, <Literal remap="tt">mke2fs</Literal>
435 reserves an inode for each 4096 bytes of the filesystem space.
536 It was found experimently that many of the files in the filesystem are
787 The ext2 filesystem associates additional flags with an inode. The extended
790 are used in version 0.5a of the filesystem. Specifically, the
833 disk, as if the filesystem was mounted with the "sync" mount option.
877 filesystem are visible to the user - In a pure abstract usage of the
878 filesystem, the user should not care about inodes.
888 Hard links can be done only in the same filesystem. This is obvious,
890 and the above elements are filesystem specific.
912 As such, it "speaks" in the language of the abstract filesystem. When the
992 The first ten inodes on the filesystem are special inodes:
999 blocks contain a list of the bad blocks in the filesystem, which
1007 It is the starting point for reaching a known path in the filesystem.
1014 currently not supported by the ext2 filesystem, so I believe this
1112 the state of the internal filesystem.
1133 Filesystem parameters which are fixed and which were determined when
1134 this specific filesystem was created. Some of those parameters can
1135 be different in different installations of the ext2 filesystem, but
1136 can not be changed once the filesystem was created.
1142 Filesystem parameters which are tunable - Can always be changed.
1148 Information about the current filesystem state.
1199 The ext2 filesystem's superblock is identified by the <Literal remap="tt">s_magic</Literal> field.
1201 Filesystem". In versions of the ext2 filesystem prior to 0.2B, the magic
1210 <Title>Filesystem fixed parameters</Title>
1255 system which created this specific filesystem:
1282 <Literal remap="tt">s_rev_level</Literal> contains the major version of the ext2 filesystem.
1300 The ext2 filesystem error handling is based on the following philosophy:
1333 unmounted filesystem means that the filesystem was not unmounted
1334 properly - The filesystem is not "clean" and probably contains
1342 error in the filesystem. A value of 0 doesn't mean that there isn't
1343 an error in the filesystem, just that the kernel didn't find any.
1365 The kernel will remount the filesystem in read-only mode if
1390 Of-course, <Literal remap="tt">e2fsck</Literal> will check the filesystem if errors were detected
1391 or if the filesystem is not clean.
1395 In addition, each time the filesystem is mounted, <Literal remap="tt">s_mnt_count</Literal> is
1397 will force a check on the filesystem even though it may be clean. It will
1419 above. This is done so that the filesystem will usually not be 100% full,
1431 <Title>Filesystem current state</Title>
1435 in the filesystem.
1440 filesystem.
1449 filesystem.
1494 design and implementation of the ext2 filesystem kernel code and support
1503 Who designed, implemented and maintains the ext2 filesystem kernel
1505 author of several helpful slides concerning the ext2 filesystem.
1517 Who designed the ext2 filesystem.
1525 Who helped designing the ext2 filesystem kernel code and wrote the
