Lines Matching full:filesystem
30 ext2 filesystem.
123 manipulate an ext2 filesystem.
130 * Filesystem-level functions::
142 @node Filesystem-level functions, File I/O Functions, EXT2FS Library Functions, EXT2FS Library Functions
144 @section Filesystem-level functions
146 The following functions operate on a filesystem handle. Most EXT2FS
147 Library functions require a filesystem handle as their first argument.
148 There are two functions which create a filesystem handle,
151 The filesystem can also be closed using @code{ext2fs_close}, and any
156 * Opening an ext2 filesystem::
158 * Initializing a filesystem::
159 * Filesystem flag functions::
164 @node Opening an ext2 filesystem, Closing and flushing out changes, Filesystem-level functions, Filesystem-level functions
166 @subsection Opening an ext2 filesystem
168 Most libext2fs functions take a filesystem handle of type
169 @code{ext2_filsys}. A filesystem handle is created either by opening
171 filesystem using @code{ext2fs_initialize}.
175 Opens a filesystem named @var{name}, using the the io_manager
177 write the filesystem. In the case of the @code{unix_io} io_manager,
178 @var{name} is interpreted as the Unix filename of the filesystem image.
182 superblock which should be used when opening the filesystem.
184 superblock located at offset 1024 bytes from the start of the filesystem
188 filesystem. Normally this is determined automatically from the
189 filesystem uperblock. If @var{block_size} is non-zero, it must match
196 the filesystem open should be handled.
200 Open the filesystem for reading and writing. Without this flag, the
201 filesystem is opened for reading only.
204 Open the filesystem regardless of the feature sets listed in the
212 @node Closing and flushing out changes, Initializing a filesystem, Opening an ext2 filesystem, Filesystem-level functions
218 Write any changes to the high-level filesystem data structures in the
219 @var{fs} filesystem. The following data structures will be written out:
222 @item The filesystem superblock
223 @item The filesystem group descriptors
224 @item The filesystem bitmaps, if read in via @code{ext2fs_read_bitmaps}.
232 associated with the filesystem handle.
237 Flush out any changes to the high-level filesystem data structures using
238 @code{ext2fs_flush} if the filesystem is marked dirty; then close and
239 free the filesystem using @code{ext2fs_free}.
245 @node Initializing a filesystem, Filesystem flag functions, Closing and flushing out changes, Filesystem-level functions
247 @subsection Initializing a filesystem
249 An ext2 filesystem is initializing by the @code{mke2fs} program. The
252 a filesystem. However, they don't do the whole job. @code{mke2fs}
253 calls @code{ext2fs_initialize} to set up the filesystem superblock, and
262 filesystem. The @code{ext2fs_initialize} function creates a filesystem
264 for a filesystem to be located in @var{name}, using the io_manager
266 supply parameters such as the number of blocks in the filesystem, the
284 The number of blocks in the filesystem. This parameter is mandatory and
288 The number of inodes in the filesystem. The
289 default value is determined by calculating the size of the filesystem,
297 The blocksize of the filesystem. Valid values are 0 (1024 bytes), 1
301 The size of fragments. The ext2 filesystem does not support fragments
306 The first data block for the filesystem. For filesystem with a
315 This field defines the number of times that the filesystem can be
318 skip the filesystem check if the number of times that the filesystem has
320 between the last time a filesystem check was performed and the current
325 This field defines the minimal interval between filesystem checks. See
332 errors are detected in the filesystem. Possible values include:
339 Remount the filesystem read-only.
360 @node Filesystem flag functions, , Initializing a filesystem, Filesystem-level functions
362 @subsection Filesystem flag functions
364 The filesystem handle has a number of flags which can be manipulated
366 libext2fs filesystem behaves; others are provided solely for the
371 This flag indicates whether or not the filesystem has been changed.
376 Mark the filesystem @var{fs} as being dirty; this will cause
378 called. @code{ext2fs_mark_super_dirty} will also set the filesystem
386 This flag indicates whether or not the filesystem is free of errors.
397 to be written when the filesystem is closed or flushed.
402 @node File I/O Functions, Inode Functions, Filesystem-level functions, EXT2FS Library Functions
407 write a file in an filesystem. The interface is similar in spirit to
432 Opens a file identified by inode number @var{ino} in filesystem @var{fs}
435 from the filesystem.
452 Return the filesystem handle where the open file @var{file} was opened.
530 * Iterating over inodes in a filesystem::
537 @node Reading and writing inodes, Iterating over inodes in a filesystem, Inode Functions, Inode Functions
552 @node Iterating over inodes in a filesystem, Iterating over blocks in an inode, Reading and writing inodes, Inode Functions
554 @subsection Iterating over inodes in a filesystem
557 in a filesystem.
574 This function returns the next inode from the filesystem; the inode
612 @node Iterating over blocks in an inode, Inode Convenience Functions, Iterating over inodes in a filesystem, Inode Functions
618 Iterate over all of the blocks in inode number @var{ino} in filesystem
624 filesystem's blocksize.
776 which must be at least as big as the filesystem's blocksize.
1157 over all directory entries in a filesystem; @code{e2fsck} does this in
1195 filesystem, this function provides a convenient way to iterate over all
1196 directory entries for that filesystem.
1207 filesystem. This is used twice; once to store the actual number of times
1219 Creates an icount stucture for a filesystem @var{fs}, with initial space
