search for: s_blocks_count

Hello, I just noticed that 'tune2fs -l' did not returned a "lively" updated information regarding the free inodes count (looks like it's always correct after unmounting). It became suprising after an online resizing operation, where the total inode count was immediatly updated (grown in my case) but the free inode count was the same: one could deduce that suddenly a lot of

We are having problems remounting an ext3 filesystem using an external journal device. The filesystem in question was working fine until the server was rebooted. This is what we see on dmesg when trying to mount: EXT3: failed to claim external journal device. The external journal lives on a LVM2 logical volume and it seems to be accessible ( we can dumpe2fs and see filesystem information).

...in-memory filesystems. */ diff --git a/fs/ext3/super.c b/fs/ext3/super.c index 6c953bb..d0643db 100644 --- a/fs/ext3/super.c +++ b/fs/ext3/super.c @@ -1862,8 +1862,8 @@ static int ext3_fill_super (struct super_block *sb, void *data, int silent) goto failed_mount; } - if (le32_to_cpu(es->s_blocks_count) > - (sector_t)(~0ULL) >> (sb->s_blocksize_bits - 9)) { + if (generic_check_addressable(sb->s_blocksize_bits, + le32_to_cpu(es->s_blocks_count))) { ext3_msg(sb, KERN_ERR, "error: filesystem is too large to mount safely"); if (sizeof(sector_t) <...

...at least one feature not supported by ext3 */ + if ((sb->s_feature_incompat + & __cpu_to_le32(EXT3_FEATURE_INCOMPAT_UNSUPPORTED)) || + (sb->s_feature_ro_compat + & __cpu_to_le32(EXT3_FEATURE_RO_COMPAT_UNSUPPORTED))) { *bytes = (unsigned long long)__le32_to_cpu(sb->s_blocks_count) - << (10 + __le32_to_cpu(sb->s_log_block_size)); + << (10 + __le32_to_cpu(sb->s_log_block_size)); + *test_fs = (sb->s_flags & + __cpu_to_le32(EXT2_FLAGS_TEST_FILESYS)) != 0; return 1; } return 0; } +static int ext4_image(const void *buf, unsigned l...

...ic int ext2_fs_init(struct fs_info *fs) if (sb.s_desc_size < sizeof(struct ext2_group_desc)) sb.s_desc_size = sizeof(struct ext2_group_desc); sbi->s_desc_per_block = BLOCK_SIZE(fs) / sb.s_desc_size; + sbi->s_desc_size = sb.s_desc_size; sbi->s_groups_count = (sb.s_blocks_count - sb.s_first_data_block + EXT2_BLOCKS_PER_GROUP(fs) - 1) / EXT2_BLOCKS_PER_GROUP(fs); diff --git a/core/fs/ext2/ext2_fs.h b/core/fs/ext2/ext2_fs.h index 803a9954..d8d07ebd 100644 --- a/core/fs/ext2/ext2_fs.h +++ b/core/fs/ext2/ext2_fs.h @@ -278,6 +278,7 @@ struct...

...tes) { const struct ext3_super_block *sb = (const struct ext3_super_block *)buf; @@ -209,43 +128,11 @@ static int base_ext4_image(const void *buf, unsigned long long *bytes, & __cpu_to_le32(EXT3_FEATURE_RO_COMPAT_UNSUPPORTED))) { *bytes = (unsigned long long)__le32_to_cpu(sb->s_blocks_count) << (10 + __le32_to_cpu(sb->s_log_block_size)); - *test_fs = (sb->s_flags & - __cpu_to_le32(EXT2_FLAGS_TEST_FILESYS)) != 0; return 1; } return 0; } -static int ext4_image(const void *buf, unsigned long long *bytes) -{ - int ret, test_fs, ext4dev_present, ext4_pr...

...e_extents(struct convert_fs *fs, - struct extent_io_tree *free_tree) -{ - ext2_filsys ext2_fs = fs->privdata; - int ret = 0; - blk_t block; - u64 bytenr; - u64 blocksize = ext2_fs->blocksize; - - block = ext2_fs->super->s_first_data_block; - for (; block < ext2_fs->super->s_blocks_count; block++) { - if (ext2fs_fast_test_block_bitmap(ext2_fs->block_map, block)) - continue; - bytenr = block * blocksize; - ret = set_extent_dirty(free_tree, bytenr, - bytenr + blocksize - 1, 0); - BUG_ON(ret); - } - - return 0; -} - /* mark btrfs-reserved blocks as used */ static...

Hi, I believe the following patch in the GIT - 2.6.17-rc5 is not correct: http://www.kernel.org/git/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=75616cf9854b83eb83a968b1338ae0ee11c9673c It is the second of the two patches contributed by Leonid Ananiev. This one incorrectly adds the super block unlocking in the error path, though. As we can see in the function ext3_group_add() the

...- __u8 s_reserved_char_pad; - __u16 s_reserved_word_pad; - __u32 s_reserved[192]; /* Padding to the end of the block */ + __u8 s_jnl_backup_type; + __u16 s_reserved_word_pad; + __u32 s_default_mount_opts; + __u32 s_first_meta_bg; + __u32 s_mkfs_time; + __u32 s_jnl_blocks[17]; + __u32 s_blocks_count_hi; + __u32 s_r_blocks_count_hi; + __u32 s_free_blocks_hi; + __u16 s_min_extra_isize; + __u16 s_want_extra_isize; + __u32 s_flags; + __u16 s_raid_stride; + __u16 s_mmp_interval; + __u64 s_mmp_block; + __u32 s_raid_stripe_width; + __u32 s_reserved[163]; }; #endif /* __EXT3_FS...

...>s_feature_incompat + & __cpu_to_le32(EXT3_FEATURE_INCOMPAT_EXTENTS) + || sb->s_feature_incompat + & __cpu_to_le32(EXT4_FEATURE_INCOMPAT_64BIT) + || sb->s_feature_incompat + & __cpu_to_le32(EXT4_FEATURE_INCOMPAT_MMP))) { + *bytes = (unsigned long long)__le32_to_cpu(sb->s_blocks_count) + << (10 + __le32_to_cpu(sb->s_log_block_size)); + return 1; + } + return 0; +} + static int ext3_image(const void *buf, unsigned long long *bytes) { const struct ext3_super_block *sb = @@ -302,6 +321,7 @@ static struct imagetype images[] = { {0, "romfs", romfs_image...

Hi, Is the http://xenbits.xensource.com/linux-2.6-xen.hg tree still being updated? if not, what''s the preferred Linux tree to track that has all of the Xen bits? Thanks, Muli _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel