Lines Matching full:filesystem
5 The Second Extended Filesystem
10 Extended Filesystem. It is currently still (April 2001) the predominant
11 filesystem in use by Linux. There are also implementations available
17 Most defaults are determined by the filesystem superblock, and can be
33 errors=continue Keep going on a filesystem error.
34 errors=remount-ro Remount the filesystem read-only on an error.
88 which is decided when the filesystem is created. Smaller blocks mean
90 and also impose other limits on the size of files and the filesystem.
115 to mounting the filesystem. Since it is so important, backup copies of
116 the superblock are stored in block groups throughout the filesystem.
125 number of inodes and blocks in the filesystem and how many are free,
126 how many inodes and blocks are in each block group, when the filesystem
128 what version of the filesystem it is (see the Revisions section below)
131 If the filesystem is revision 1 or higher, then there are extra fields,
133 and space for optional filesystem features to store configuration info.
136 on the disc in little endian format, so a filesystem is portable between
142 The inode (index node) is a fundamental concept in the ext2 filesystem.
143 Each object in the filesystem is represented by an inode. The inode
144 structure contains pointers to the filesystem blocks which contain the
170 and changed with the chattr command, and allow specific filesystem
179 A directory is a filesystem object and has an inode just like a file.
181 each name with an inode number. Later revisions of the filesystem also
200 Symbolic links are also filesystem objects with inodes. They deserve
217 fill up all the space available to them (this is independent of filesystem
218 quotas). It also keeps the filesystem from filling up entirely which
221 Filesystem check
225 filesystems. The superblock of the ext2 filesystem contains several
227 the filesystem at boot can take a long time if it is large). fsck will
228 run if the filesystem was not cleanly unmounted, if the maximum mount
236 It safely allows features to be added to the filesystem, without
238 filesystem code. The feature compatibility mechanism is not supported by
246 A COMPAT flag indicates that a feature is present in the filesystem,
249 the filesystem without any chance of corrupting the filesystem (or even
251 "this filesystem has a (hidden) feature" that the kernel or e2fsck may
260 filesystem would/could corrupt the filesystem, so this is prevented. The
266 boundary, but this is a legitimate layout in a SPARSE_SUPER filesystem.
277 ext3 journal from mounting the filesystem without replaying the journal.
281 RO_COMPAT, or INCOMPAT flags it will refuse to check the filesystem,
283 or not. Allowing e2fsck to succeed on a filesystem with an unknown
285 a filesystem with unknown features is a good incentive for the user to
302 - per-filesystem: add the "sync" option to mount (or in /etc/fstab)
312 Many of the limits are determined at the time the filesystem is first
314 data blocks is fixed at filesystem creation time, so the only way to
315 increase the number of inodes is to increase the size of the filesystem.
323 Filesystem block size 1kB 2kB 4kB 8kB
326 Filesystem size limit 2047GB 8192GB 16384GB 32768GB
330 filesystem larger than that can be created at this time. There is also
359 been modified, prior to writing them into the filesystem. This means
360 it is possible to add a journal to an existing ext2 filesystem without
363 When changes to the filesystem (e.g. a file is renamed) they are stored in
367 in that transaction are guaranteed to represent a valid filesystem state,
368 and are copied into the filesystem. If a transaction is incomplete at
371 filesystem changes they represent are also lost).
383 Filesystem Resizing http://ext2resize.sourceforge.net/