Lines Matching +full:group +full:- +full:index +full:- +full:bits
1 .. SPDX-License-Identifier: GPL-2.0
18 set using tune2fs(8). Kernel-determined defaults are indicated by (*).
34 errors=remount-ro Remount the filesystem read-only on an error.
37 grpid, bsdgroups Give objects the same group ID as their parent.
38 nogrpid, sysvgroups New objects have the group ID of their creator.
40 nouid32 Use 16-bit UIDs and GIDs.
50 resgid=n The group ID which may use the reserved blocks.
65 grpquota Enable group disk quota support
84 ------
93 ------------
97 of consecutive data. Information about each block group is kept in a
99 Two blocks near the start of each group are reserved for the block usage
102 that the maximum size of a block group is 8 times the size of a block.
104 The block(s) following the bitmaps in each block group are designated
105 as the inode table for that block group and the remainder are the data
107 in the same block group as the inode which contains them.
110 --------------
118 every block group, along with backups of the group descriptor block(s).
126 how many inodes and blocks are in each block group, when the filesystem
140 ------
142 The inode (index node) is a fundamental concept in the ext2 filesystem.
147 group, flags, size, number of blocks used, access time, change time,
154 bits of the file size if the inode is a regular file (allowing file sizes
158 used up for both Linux and the HURD for larger owner and group fields,
160 fields to store the extra more bits.
164 pointers to the next set of blocks), a pointer to a doubly-indirect
166 trebly-indirect block (which contains pointers to doubly-indirect blocks).
168 The flags field contains some ext2-specific flags which aren't catered
171 behaviour on a per-file basis. There are flags for secure deletion,
172 undeletable, compression, synchronous updates, immutability, append-only,
173 dumpable, no-atime, indexed directories, and data-journaling. Not all
177 -----------
188 block group as the directory in which they are first created.
190 The current implementation of ext2 uses a singly-linked list to store
198 -------------
212 --------------
215 for a particular user (normally the super-user). This is intended to
216 allow for the system to continue functioning even if non-privileged users
222 ----------------
233 ---------------------
240 revision 1. There are three 32-bit fields, one for compatible features
241 (COMPAT), one for read-only compatible (RO_COMPAT) features and one for
247 but the on-disk format is 100% compatible with older on-disk formats, so
257 An RO_COMPAT flag indicates that the on-disk format is 100% compatible
258 with older on-disk formats for reading (i.e. the feature does not change
259 the visible on-disk format). However, an old kernel writing to such a
262 sparse groups allow file data blocks where superblock/group descriptor
265 get an error if it tried to free a series of blocks which crossed a group
268 An INCOMPAT flag indicates the on-disk format has changed in some
273 The COMPRESSION flag is an obvious INCOMPAT flag - if the kernel
290 --------
300 - per-file if you have the program source: use the O_SYNC flag to open()
301 - per-file if you don't have the source: use "chattr +S" on the file
302 - per-filesystem: add the "sync" option to mount (or in /etc/fstab)
308 -----------
310 There are various limits imposed by the on-disk layout of ext2. Other
318 Most of these limits could be overcome with slight changes in the on-disk
337 There is a "soft" upper limit of about 10-15k files in a single directory
338 with the current linear linked-list directory implementation. This limit
340 finding) files in such large directories. Using a hashed directory index
341 (under development) allows 100k-1M+ files in a single directory without
347 enough 4-character names to make up unique directory entries, so they
352 ----------
357 to the on-disk ext2 layout. In a nutshell, the journal is a regular
394 RISC OS client http://www.esw-heim.tu-clausthal.de/~marco/smorbrod/IscaFS/