GNU Info

(libext2fs.info)Filesystem flag functions

---

Prev: Initializing a filesystem Up: Filesystem-level functions

---

Enter node , (file) or (file)node

Filesystem flag functions
-------------------------

   The filesystem handle has a number of flags which can be manipulated
using the following function.  Some of these flags affect how the
libext2fs filesystem behaves; others are provided solely for the
application's convenience.

 - Function: void ext2fs_mark_changed (ext2_filsys FS)
 - Function: int ext2fs_test_changed (ext2_filsys FS)
     This flag indicates whether or not the filesystem has been changed.
     It is not used by the ext2fs library.

 - Function: void ext2fs_mark_super_dirty (ext2_filsys FS)
     Mark the filesystem FS as being dirty; this will cause the
     superblock information to be flushed out when `ext2fs_close' is
     called.  `ext2fs_mark_super_dirty' will also set the filesystem
     changed flag.  The dirty flag is automatically cleared by
     `ext2fs_flush' when the superblock is written to disk.

 - Function: void ext2fs_mark_valid (ext2_filsys FS)
 - Function: void ext2fs_unmark_valid (ext2_filsys FS)
 - Function: int ext2fs_test_valid (ext2_filsys FS)
     This flag indicates whether or not the filesystem is free of
     errors.  It is not used by libext2fs, and is solely for the
     application's convenience.

 - Function: void ext2fs_mark_ib_dirty (ext2_filsys FS)
 - Function: void ext2fs_mark_bb_dirty (ext2_filsys FS)
 - Function: int ext2fs_test_ib_dirty (ext2_filsys FS)
 - Function: int ext2fs_test_bb_dirty (ext2_filsys FS)
     These flags indicate whether or not the inode or block bitmaps
     have been modified.   If the flag is set, it will cause the
     appropriate bitmap to be written when the filesystem is closed or
     flushed.