Lines Matching refs:an

14 When mounting an ext2 filesystem, the following options are accepted.
27 errors=remount-ro		Remount the filesystem read-only on an error.
28 errors=panic			Panic and halt the machine if an error occurs.
82 the filing system.  The primary copy of the superblock is stored at an
112 Each object in the filesystem is represented by an inode.  The inode
114 data held in the object and all of the metadata about an object except
115 its name.  The metadata about an object includes the permissions, owner,
132 in the inode.  There is a pointer to an indirect block (which contains
148 A directory is a filesystem object and has an inode just like a file.
150 each name with an inode number.  Later revisions of the filesystem also
228 the visible on-disk format).  However, an old kernel writing to such a
230 most common such feature, SPARSE_SUPER, is an RO_COMPAT feature because
234 get an error if it tried to free a series of blocks which crossed a group
239 cause a problem if an old kernel tried to mount it.  FILETYPE is an
242 The COMPRESSION flag is an obvious INCOMPAT flag - if the kernel
252 or not.  Allowing e2fsck to succeed on a filesystem with an unknown
298 an upper limit on the block size imposed by the page size of the kernel,
302 There is an upper limit of 32768 subdirectories in a single directory.
309 performance problems (although RAM size becomes an issue at this point).
327 it is possible to add a journal to an existing ext2 filesystem without