Lines Matching full:filesystem
30 ext2 filesystem.
120 manipulate an ext2 filesystem.
127 * Filesystem-level functions::
139 @node Filesystem-level functions, File I/O Functions, EXT2FS Library Functions, EXT2FS Library Functions
141 @section Filesystem-level functions
143 The following functions operate on a filesystem handle. Most EXT2FS
144 Library functions require a filesystem handle as their first argument.
145 There are two functions which create a filesystem handle,
148 The filesystem can also be closed using @code{ext2fs_close}, and any
153 * Opening an ext2 filesystem::
155 * Initializing a filesystem::
156 * Filesystem flag functions::
161 @node Opening an ext2 filesystem, Closing and flushing out changes, Filesystem-level functions, Filesystem-level functions
163 @subsection Opening an ext2 filesystem
165 Most libext2fs functions take a filesystem handle of type
166 @code{ext2_filsys}. A filesystem handle is created either by opening
168 filesystem using @code{ext2fs_initialize}.
172 Opens a filesystem named @var{name}, using the the io_manager
174 write the filesystem. In the case of the @code{unix_io} io_manager,
175 @var{name} is interpreted as the Unix filename of the filesystem image.
179 superblock which should be used when opening the filesystem.
181 superblock located at offset 1024 bytes from the start of the filesystem
185 filesystem. Normally this is determined automatically from the
186 filesystem uperblock. If @var{block_size} is non-zero, it must match
193 the filesystem open should be handled.
197 Open the filesystem for reading and writing. Without this flag, the
198 filesystem is opened for reading only.
201 Open the filesystem regardless of the feature sets listed in the
209 @node Closing and flushing out changes, Initializing a filesystem, Opening an ext2 filesystem, Filesystem-level functions
215 Write any changes to the high-level filesystem data structures in the
216 @var{fs} filesystem. The following data structures will be written out:
219 @item The filesystem superblock
220 @item The filesystem group descriptors
221 @item The filesystem bitmaps, if read in via @code{ext2fs_read_bitmaps}.
229 associated with the filesystem handle.
234 Flush out any changes to the high-level filesystem data structures using
235 @code{ext2fs_flush} if the filesystem is marked dirty; then close and
236 free the filesystem using @code{ext2fs_free}.
242 @node Initializing a filesystem, Filesystem flag functions, Closing and flushing out changes, Filesystem-level functions
244 @subsection Initializing a filesystem
246 An ext2 filesystem is initializing by the @code{mke2fs} program. The
249 a filesystem. However, they don't do the whole job. @code{mke2fs}
250 calls @code{ext2fs_initialize} to set up the filesystem superblock, and
259 filesystem. The @code{ext2fs_initialize} function creates a filesystem
261 for a filesystem to be located in @var{name}, using the io_manager
263 supply parameters such as the number of blocks in the filesystem, the
281 The number of blocks in the filesystem. This parameter is mandatory and
285 The number of inodes in the filesystem. The
286 default value is determined by calculating the size of the filesystem,
294 The blocksize of the filesystem. Valid values are 0 (1024 bytes), 1
298 The size of fragments. The ext2 filesystem does not support fragments
303 The first data block for the filesystem. For filesystem with a
312 This field defines the number of times that the filesystem can be
315 skip the filesystem check if the number of times that the filesystem has
317 between the last time a filesystem check was performed and the current
322 This field defines the minimal interval between filesystem checks. See
329 errors are detected in the filesystem. Possible values include:
336 Remount the filesystem read-only.
357 @node Filesystem flag functions, , Initializing a filesystem, Filesystem-level functions
359 @subsection Filesystem flag functions
361 The filesystem handle has a number of flags which can be manipulated
363 libext2fs filesystem behaves; others are provided solely for the
368 This flag indicates whether or not the filesystem has been changed.
373 Mark the filesystem @var{fs} as being dirty; this will cause
375 called. @code{ext2fs_mark_super_dirty} will also set the filesystem
383 This flag indicates whether or not the filesystem is free of errors.
394 to be written when the filesystem is closed or flushed.
399 @node File I/O Functions, Inode Functions, Filesystem-level functions, EXT2FS Library Functions
404 write a file in an filesystem. The interface is similar in spirit to
429 Opens a file identified by inode number @var{ino} in filesystem @var{fs}
432 from the filesystem.
449 Return the filesystem handle where the open file @var{file} was opened.
527 * Iterating over inodes in a filesystem::
534 @node Reading and writing inodes, Iterating over inodes in a filesystem, Inode Functions, Inode Functions
549 @node Iterating over inodes in a filesystem, Iterating over blocks in an inode, Reading and writing inodes, Inode Functions
551 @subsection Iterating over inodes in a filesystem
554 in a filesystem.
571 This function returns the next inode from the filesystem; the inode
609 @node Iterating over blocks in an inode, Inode Convenience Functions, Iterating over inodes in a filesystem, Inode Functions
615 Iterate over all of the blocks in inode number @var{ino} in filesystem
621 filesystem's blocksize.
773 which must be at least as big as the filesystem's blocksize.
1154 over all directory entries in a filesystem; @code{e2fsck} does this in
1192 filesystem, this function provides a convenient way to iterate over all
1193 directory entries for that filesystem.
1204 filesystem. This is used twice; once to store the actual number of times
1216 Creates an icount stucture for a filesystem @var{fs}, with initial space
