Displaying 10 results from an estimated 10 matches for "ext3_feature_compat_has_journ".
Did you mean:
ext3_feature_compat_has_journal
2008 Oct 11
1
[PATCH] fstype: Fix ext4/ext4dev probing
...tes,
+ int *test_fs)
{
const struct ext3_super_block *sb =
(const struct ext3_super_block *)buf;
- /* ext4dev needs ext2 + journal + test_fs flag + one !ext3 feature */
- if (sb->s_magic == __cpu_to_le16(EXT2_SUPER_MAGIC)
- && (sb->s_feature_compat
- & __cpu_to_le32(EXT3_FEATURE_COMPAT_HAS_JOURNAL))
- && (sb->s_flags & __cpu_to_le32(EXT2_FLAGS_TEST_FILESYS))
- && (sb->s_feature_incompat
- & __cpu_to_le32(EXT3_FEATURE_RO_COMPAT_SUPP)
- || sb->s_feature_incompat
- & __cpu_to_le32(EXT3_FEATURE_INCOMPAT_UNSUPPORTED)
- || sb->s_feature_incompat
- &...
2008 Jun 16
0
latest fixes
...0x0004
+#define EXT2_FEATURE_RO_COMPAT_SPARSE_SUPER 0x0001
+#define EXT2_FEATURE_RO_COMPAT_LARGE_FILE 0x0002
+#define EXT2_FEATURE_RO_COMPAT_BTREE_DIR 0x0004
+#define EXT2_FEATURE_INCOMPAT_FILETYPE 0x0002
+#define EXT2_FEATURE_INCOMPAT_META_BG 0x0010
#define EXT3_FEATURE_COMPAT_HAS_JOURNAL 0x0004
#define EXT3_FEATURE_INCOMPAT_JOURNAL_DEV 0x0008
+#define EXT3_FEATURE_INCOMPAT_RECOVER 0x0004
+
#define EXT3_FEATURE_INCOMPAT_EXTENTS 0x0040
#define EXT4_FEATURE_INCOMPAT_64BIT 0x0080
#define EXT4_FEATURE_INCOMPAT_MMP 0x0100...
2003 Apr 22
0
ext3 "noload" option to mount returning error in 2.4.9 & 2.4.18 s eries kernel
...n sd(8,81)
Is my syntax incorrect? What specifically is the noload option for. In
the 2.4.18 kernel sources it looks like "noload" will always give this error
if the "noload" option is set.
if (!test_opt(sb, NOLOAD) &&
EXT3_HAS_COMPAT_FEATURE(sb, EXT3_FEATURE_COMPAT_HAS_JOURNAL)) {
if (ext3_load_journal(sb, es))
goto failed_mount2;
} else if (journal_inum) {
if (ext3_create_journal(sb, es, journal_inum))
goto failed_mount2;
} else {
if (!silent)...
2003 Apr 22
0
RE: ext3 "noload" option to mount returning error in 2.4.9 & 2.4. 18 s eries kernel
...incorrect? What specifically is the noload option for. In
> the 2.4.18 kernel sources it looks like "noload" will always give this
error
> if the "noload" option is set.
>
> if (!test_opt(sb, NOLOAD) &&
> EXT3_HAS_COMPAT_FEATURE(sb, EXT3_FEATURE_COMPAT_HAS_JOURNAL))
{
> if (ext3_load_journal(sb, es))
> goto failed_mount2;
> } else if (journal_inum) {
> if (ext3_create_journal(sb, es, journal_inum))
> goto failed_mount2;
> } else {
>...
2003 Apr 18
1
ext3 "noload" option to mount returning error in 2.4.9&2.4.18 ser ies kernel
...n sd(8,81)
Is my syntax incorrect? What specifically is the noload option for. In
the 2.4.18 kernel sources it looks like "noload" will always give this error
if the "noload" option is set.
if (!test_opt(sb, NOLOAD) &&
EXT3_HAS_COMPAT_FEATURE(sb, EXT3_FEATURE_COMPAT_HAS_JOURNAL)) {
if (ext3_load_journal(sb, es))
goto failed_mount2;
} else if (journal_inum) {
if (ext3_create_journal(sb, es, journal_inum))
goto failed_mount2;
} else {
if (!silent)...
2001 Aug 24
1
how to tell ext2 from ext3 at byte-level?
If I have an image of a filesystem taken with dd, I can look at it with a
hex editor and discover that an ext2/3 superblock is at offset 1024 and I
can figure out a lot of info about it. I cannot figure out, however, how
the superblock differs from ext2 in ext3. I can't tell them apart... the
"magic number" is the same as well as the "revision" field.
If I have such an
2009 Oct 04
1
[PATCH] recognise ext4 without journal
...mage(const void *buf, unsigned long long *bytes,
if (sb->s_magic != __cpu_to_le16(EXT2_SUPER_MAGIC))
return 0;
- /*
- * For now, ext4 requires a journal -- but this may change
- * soon if we get that patch from Google. :-)
- */
- if ((sb->s_feature_compat
- & __cpu_to_le32(EXT3_FEATURE_COMPAT_HAS_JOURNAL)) == 0)
- return 0;
-
/* There is at least one feature not supported by ext3 */
if ((sb->s_feature_incompat
& __cpu_to_le32(EXT3_FEATURE_INCOMPAT_UNSUPPORTED)) ||
--
1.6.3.3
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.
..._prealloc_blocks; /* Nr of blocks to try to preallocate*/
__u8 s_prealloc_dir_blocks; /* Nr to preallocate for dirs */
- __u16 s_reserved_gdt_blocks; /* Per group desc for online growth */
+ __le16 s_reserved_gdt_blocks; /* Per group desc for online growth */
/*
* Journaling support valid if EXT3_FEATURE_COMPAT_HAS_JOURNAL set.
*/
Index: linux-warnings/fs/ext3/super.c
===================================================================
--- linux-warnings/fs/ext3/super.c (revision 14)
+++ linux-warnings/fs/ext3/super.c (revision 20)
@@ -2105,13 +2105,13 @@
ext3_mark_recovery_complete(sb, es);
} else {
-...
2007 Aug 15
0
[git patch] fstype support + minor stuff
...Signed-off-by: maximilian attems <max at stro.at>
diff --git a/usr/kinit/fstype/ext3_fs.h b/usr/kinit/fstype/ext3_fs.h
index e3deb72..12d64fe 100644
--- a/usr/kinit/fstype/ext3_fs.h
+++ b/usr/kinit/fstype/ext3_fs.h
@@ -7,6 +7,10 @@
#define EXT3_SUPER_MAGIC 0xEF53
#define EXT3_FEATURE_COMPAT_HAS_JOURNAL 0x0004
+#define EXT3_FEATURE_INCOMPAT_JOURNAL_DEV 0x0008
+#define EXT3_FEATURE_INCOMPAT_EXTENTS 0x0040
+#define EXT4_FEATURE_INCOMPAT_64BIT 0x0080
+#define EXT4_FEATURE_INCOMPAT_MMP 0x0100
/*
* Structure of the super block
diff --git a/usr/ki...