Lines Matching refs:of

5 snapshotting.  In addition to versioning capability of the entire file
11 NILFS2 creates a number of checkpoints every few seconds or per
17 There is no limit on the number of snapshots until the volume gets
50 barrier(*)		This enables/disables the use of write barriers.  This
57 cp=n			Specify the checkpoint-number of the snapshot to be
65 			is equivalent to the ordered data mode of the ext3
70 			of all file operations including overwriting of data
72 			overtaking of events occurs in the recovered file
74 norecovery		Disable recovery of the filesystem on mount.
78 discard			This enables/disables the use of discard/TRIM commands.
87 through the system call interfaces. The list of all NILFS2 specific ioctls are
90 Table of NILFS2 specific ioctls
93  NILFS_IOCTL_CHANGE_CPMODE      Change mode of given checkpoint between
113  NILFS_IOCTL_SET_SUINFO         Modify segment usage info of requested
116 				cleaning operation of segments and reduce
117 				performance penalty or wear of flash device
118 				due to redundant move of in-use blocks.
127  NILFS_IOCTL_GET_BDESCS         Return information about descriptors of disk
132 			        environment of requested parameters from
142  NILFS_IOCTL_SET_ALLOC_RANGE    Define lower limit of segments in bytes and
143 			        upper limit of segments in bytes. This ioctl
169 where <cno> is the checkpoint number of the snapshot.
181 A nilfs2 volume is equally divided into a number of segments except
183 of logs.  Each log is composed of summary information blocks, payload
202 The payload blocks are organized per file, and each file consists of
214 The organization of the blocks is recorded in the summary information
225 to maintain file system meta data.  The current version of NILFS2 uses
230  3) Segment usage file (sufile)    -- Stores allocation state of segments
235 The following figure shows a typical organization of the logs:
242 To stride over segment boundaries, this sequence of files may be split
243 into multiple logs.  The sequence of logs that should be treated as
245 summary.  The recovery code of nilfs2 looks this boundary information
246 to ensure atomicity of updates.
250 of regular files, directories, symlinks and other special files, are
251 included in the ifile.  The inode of ifile itself is included in the
270 For detail on the format of each file, please see include/linux/nilfs2_fs.h.