Lines Matching full:filesystem
4 The Second Extended Filesystem
9 Extended Filesystem. It is currently still (April 2001) the predominant
10 filesystem in use by Linux. There are also implementations available
16 Most defaults are determined by the filesystem superblock, and can be
32 errors=continue Keep going on a filesystem error.
33 errors=remount-ro Remount the filesystem read-only on an error.
89 which is decided when the filesystem is created. Smaller blocks mean
91 and also impose other limits on the size of files and the filesystem.
116 to mounting the filesystem. Since it is so important, backup copies of
117 the superblock are stored in block groups throughout the filesystem.
126 number of inodes and blocks in the filesystem and how many are free,
127 how many inodes and blocks are in each block group, when the filesystem
129 what version of the filesystem it is (see the Revisions section below)
132 If the filesystem is revision 1 or higher, then there are extra fields,
134 and space for optional filesystem features to store configuration info.
137 on the disc in little endian format, so a filesystem is portable between
143 The inode (index node) is a fundamental concept in the ext2 filesystem.
144 Each object in the filesystem is represented by an inode. The inode
145 structure contains pointers to the filesystem blocks which contain the
171 and changed with the chattr command, and allow specific filesystem
180 A directory is a filesystem object and has an inode just like a file.
182 each name with an inode number. Later revisions of the filesystem also
201 Symbolic links are also filesystem objects with inodes. They deserve
218 fill up all the space available to them (this is independent of filesystem
219 quotas). It also keeps the filesystem from filling up entirely which
222 Filesystem check
226 filesystems. The superblock of the ext2 filesystem contains several
228 the filesystem at boot can take a long time if it is large). fsck will
229 run if the filesystem was not cleanly unmounted, if the maximum mount
237 It safely allows features to be added to the filesystem, without
239 filesystem code. The feature compatibility mechanism is not supported by
247 A COMPAT flag indicates that a feature is present in the filesystem,
250 the filesystem without any chance of corrupting the filesystem (or even
252 "this filesystem has a (hidden) feature" that the kernel or e2fsck may
261 filesystem would/could corrupt the filesystem, so this is prevented. The
267 boundary, but this is a legitimate layout in a SPARSE_SUPER filesystem.
278 ext3 journal from mounting the filesystem without replaying the journal.
282 RO_COMPAT, or INCOMPAT flags it will refuse to check the filesystem,
284 or not. Allowing e2fsck to succeed on a filesystem with an unknown
286 a filesystem with unknown features is a good incentive for the user to
303 - per-filesystem: add the "sync" option to mount (or in /etc/fstab)
313 Many of the limits are determined at the time the filesystem is first
315 data blocks is fixed at filesystem creation time, so the only way to
316 increase the number of inodes is to increase the size of the filesystem.
324 Filesystem block size 1kB 2kB 4kB 8kB
327 Filesystem size limit 2047GB 8192GB 16384GB 32768GB
331 filesystem larger than that can be created at this time. There is also
360 been modified, prior to writing them into the filesystem. This means
361 it is possible to add a journal to an existing ext2 filesystem without
364 When changes to the filesystem (e.g. a file is renamed) they are stored in
368 in that transaction are guaranteed to represent a valid filesystem state,
369 and are copied into the filesystem. If a transaction is incomplete at
372 filesystem changes they represent are also lost).
384 Filesystem Resizing http://ext2resize.sourceforge.net/