Lines Matching +full:trade +full:- +full:off

68 .Em super-block
71 The following structure describes the super-block and is
74 .Bd -literal
81 	int32_t	 fs_sblkno;        /* offset of super-block in filesys */
82 	int32_t	 fs_cblkno;        /* offset of cyl-block in filesys */
83 	int32_t	 fs_iblkno;        /* offset of inode-blocks in filesys */
132 /* this data must be re-computed after crashes */
137 	int8_t 	 fs_ronly;         /* mounted read-only flag */
141 	uint64_t fs_swuid;         /* system-wide uid */
170 	int32_t	 fs_old_inodefmt;  /* format of on-disk inodes */
172 	int64_t	 fs_qbmask;        /* ~fs_bmask for use with 64-bit size */
173 	int64_t	 fs_qfmask;        /* ~fs_fmask for use with 64-bit size */
188 #define FS_42INODEFMT	-1      /* 4.2BSD inode format */
202 A file system is described by its super-block, which in turn
204 The super-block is critical
209 super-block data does not change, so the copies need not be
253 only the super-user may continue to allocate blocks.
264 Empirically the best trade-off between block fragmentation and
318 Note that super-blocks are never more than size
325 the super-block for this name.
338 in addition to the super-block.
348 .Em "Super-block for a file system" :
350 is limited by the fact that the super-block is of size
379 each current directory, each mounted-on file,
381 An inode is `named' by its device/i-number pair.
386 .Bd -literal
392 	char	ea_name[1];	    /* attribute name (NOT nul-terminated) */
400 .Bl -tag -width ".Dv EXTATTR_CONTENT_SIZE(eap)"
413 .Bd -literal
414 	if (eap->ea_namespace == EXTATTR_NAMESPACE_SYSTEM &&
415             eap->ea_namelength == sizeof(POSIX1E_ACL_ACCESS_EXTATTR_NAME) - 1 &&
416 	    strncmp(eap->ea_name, POSIX1E_ACL_ACCESS_EXTATTR_NAME,
417              sizeof(POSIX1E_ACL_ACCESS_EXTATTR_NAME) - 1) == 0) {
424 A super-block structure named filsys appeared in