Lines Matching refs:of
6 Theodore Ts'o and Stephen Tweedie, it was a major rewrite of the
20 check=none, nocheck (*) Don't do extra checking of bitmaps on mount
34 nogrpid, sysvgroups New objects have the group ID of their creator.
69 the concepts of blocks, inodes and directories. It has space in the
80 a fixed size, of 1024, 2048 or 4096 bytes (8192 bytes on Alpha systems),
83 and also impose other limits on the size of files and the filesystem.
89 and minimise the amount of head seeking when reading a large amount
90 of consecutive data. Information about each block group is kept in a
92 Two blocks near the start of each group are reserved for the block usage
95 that the maximum size of a block group is 8 times the size of a block.
105 The superblock contains all the information about the configuration of
106 the filing system. The primary copy of the superblock is stored at an
107 offset of 1024 bytes from the start of the device, and it is essential
108 to mounting the filesystem. Since it is so important, backup copies of
110 The first version of ext2 (revision 0) stores a copy at the start of
111 every block group, along with backups of the group descriptor block(s).
112 Because this can consume a considerable amount of space for large
113 filesystems, later revisions can optionally reduce the number of backup
115 superblock feature). The groups chosen are 0, 1 and powers of 3, 5 and 7.
118 number of inodes and blocks in the filesystem and how many are free,
121 what version of the filesystem it is (see the Revisions section below)
138 data held in the object and all of the metadata about an object except
140 group, flags, size, number of blocks used, access time, change time,
141 modification time, deletion time, number of links, fragments, version
147 bits of the file size if the inode is a regular file (allowing file sizes
149 by the HURD to reference the inode of a program which will be used to
150 interpret this object. Most of the remaining reserved fields have been
152 The HURD also has a larger mode field so it uses another of the remaining
157 pointers to the next set of blocks), a pointer to a doubly-indirect
167 of these are supported yet.
174 each name with an inode number. Later revisions of the filesystem also
175 encode the type of the object (file, directory, symlink, device, fifo,
177 (support for taking advantage of this feature does not yet exist in
183 The current implementation of ext2 uses a singly-linked list to store
184 the filenames in the directory; a pending enhancement uses hashing of the
207 In ext2, there is a mechanism for reserving a certain number of blocks
210 fill up all the space available to them (this is independent of filesystem
218 filesystems. The superblock of the ext2 filesystem contains several
230 unnecessarily sacrificing compatibility with older versions of the
232 the original revision 0 (EXT2_GOOD_OLD_REV) of ext2, but was introduced in
242 the filesystem without any chance of corrupting the filesystem (or even
245 want to be aware of (more on e2fsck and feature flags later). The ext3
248 take any special notice of it if it doesn't understand ext3 journaling.
258 get an error if it tried to free a series of blocks which crossed a group
268 read() instead of it automatically decompressing your data. The ext3
272 For e2fsck, it needs to be more strict with the handling of these
273 flags than the kernel. If it doesn't understand ANY of the COMPAT,
275 because it has no way of verifying whether a given feature is valid
277 feature is a false sense of security for the user. Refusing to check
285 It is frequently claimed that the ext2 implementation of writing
290 If you're exceptionally paranoid, there are 3 ways of making metadata
303 There are various limits imposed by the on-disk layout of ext2. Other
304 limits are imposed by the current implementation of the kernel code.
305 Many of the limits are determined at the time the filesystem is first
306 created, and depend upon the block size chosen. The ratio of inodes to
308 increase the number of inodes is to increase the size of the filesystem.
309 No tools currently exist which can change the ratio of inodes to blocks.
311 Most of these limits could be overcome with slight changes in the on-disk
313 the expense of some compatibility).
320 There is a 2.4 kernel limit of 2048GB for a single block device, so no
322 an upper limit on the block size imposed by the page size of the kernel,
326 There is an upper limit of 32000 subdirectories in a single directory.
328 There is a "soft" upper limit of about 10-15k files in a single directory
335 The (meaningless) absolute upper limit of files in a single directory
340 running out of unique filenames.
346 Tweedie. It avoids the risks of metadata corruption and the need to
356 the time of a crash. If a transaction is complete at the time of a crash
360 the time of the crash, then there is no guarantee of consistency for
383 (*) no longer actively developed/supported (as of Apr 2001)
384 (+) no longer actively developed/supported (as of Mar 2009)