Lines Matching +full:long +full:- +full:ram +full:- +full:code
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.
40 nouid32 Use 16-bit UIDs and GIDs.
84 ------
93 ------------
110 --------------
140 ------
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 -----------
187 The inode allocation code tries to assign inodes which are in the same
190 The current implementation of ext2 uses a singly-linked list to store
198 -------------
202 itself if the symlink is less than 60 bytes long. It uses the fields
205 block for the symlink, and most symlinks are less than 60 characters long.
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 ----------------
227 the filesystem at boot can take a long time if it is large). fsck will
233 ---------------------
238 filesystem code. The feature compatibility mechanism is not supported by
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
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
311 limits are imposed by the current implementation of the kernel code.
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
341 (under development) allows 100k-1M+ files in a single directory without
342 performance problems (although RAM size becomes an issue at this point).
347 enough 4-character names to make up unique directory entries, so they
352 ----------
354 A journaling extension to the ext2 code has been developed by Stephen
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/