Displaying 4 results from an estimated 4 matches for "ext3_valid_fs".
2005 Jun 20
0
[patch 2/3] fs/ext3/resize.c: fix sparse warnings
An embedded and charset-unspecified text was scrubbed...
Name: sparse-fs_ext3_resize.patch
URL: <http://listman.redhat.com/archives/ext3-users/attachments/20050620/8e33ffa8/attachment.ksh>
2005 Feb 15
1
[PATCH] ext3: Fix sparse -Wbitwise warnings.
...[%u] = %lu\n",
primary[i]->b_blocknr, gdbackups,
blk + primary[i]->b_blocknr); */
@@ -675,7 +675,7 @@
"can't update backup for group %d (err %d), "
"forcing fsck on next reboot\n", group, err);
sbi->s_mount_state &= ~EXT3_VALID_FS;
- sbi->s_es->s_state &= ~cpu_to_le16(EXT3_VALID_FS);
+ sbi->s_es->s_state &= cpu_to_le16(~EXT3_VALID_FS);
mark_buffer_dirty(sbi->s_sbh);
}
}
2003 Jun 23
3
How to determine Ext2/3 FileSystem state ?
hi all,
I intend to write a snapshot module for Ext2/3 file-systems.
For that i need to make sure that FS is in consistent state before taking
snapshot.
For ex. in case of UFS, the superblock has a fs_clean flag which is set to
be
FSSTABLE to tell that its in consistent state. (otherwise its set to
FSACTIVE)
I m not able to find any such information for Ext2/Ext3.
(The
2003 Jun 25
0
Re: Ext3-users digest, Vol 1 #910 - 5 msgs
...pshot image
> > (Ext2/Ext3 File-System) is indeed consistent.
> >
> > Is there any field in super-block or any other on-disk
>structure which could
> > tell the state of a raw File-System(Ext2/3) image.
>
>After the snapshot is taken (as above), the absence of
>EXT3_VALID_FS in
>s_mount_state, or the presence of EXT3_FEATURE_INCOMPAT_RECOVER
>in
>s_feature_incompat means that the snapshot was not valid.
>
>Cheers, Andreas
>--
>Andreas Dilger
>http://sourceforge.net/projects/ext2resize/
>http://www-mddsp.enel.ucalgary.ca/People/adilger/
>...