From: Valerie Clement <valerie.clement@bull.net>
To: Theodore Ts'o <tytso@mit.edu>
Cc: linux-ext4@vger.kernel.org
Subject: Re: [PATCH, E2FSPROGS] On-disk format definition for 64-bit support
Date: Wed, 18 Oct 2006 15:30:56 +0200 [thread overview]
Message-ID: <45362C90.4030305@bull.net> (raw)
In-Reply-To: <E1Ga4l7-0003mU-46@candygram.thunk.org>
Theodore Ts'o wrote:
> After thinking about it some more, and looking at the code committed
> into the kernel git tree, I've changed my mind and agree that the
> extending current group descriptor is simpler than having two versions
> of the structure depending on the size of the group descriptor.
>
> Does everyone agree this is what the 64-bit on-desk definition should
> be?
See my remarks below. Otherwise, it's good for me.
Should 64-bit support also imply BIG_BG support?
Yes. There is no flag added for the support of the big block groups, we
just use the INCOMPAT_64BIT flag.
>
> Index: e2fsprogs/lib/ext2fs/ext2_fs.h
> ===================================================================
> --- e2fsprogs.orig/lib/ext2fs/ext2_fs.h 2006-10-18 00:33:56.000000000 -0400
> +++ e2fsprogs/lib/ext2fs/ext2_fs.h 2006-10-18 01:08:06.000000000 -0400
> @@ -147,6 +147,25 @@
> __u32 bg_reserved[3];
> };
>
> +struct ext4_group_desc
struct ext2_group_desc ?
> +{
> + __u32 bg_block_bitmap; /* Blocks bitmap block */
> + __u32 bg_inode_bitmap; /* Inodes bitmap block */
> + __u32 bg_inode_table; /* Inodes table block */
> + __u16 bg_free_blocks_count; /* Free blocks count */
> + __u16 bg_free_inodes_count; /* Free inodes count */
> + __u16 bg_used_dirs_count; /* Directories count */
> + __u16 bg_flags;
> + __u32 bg_reserved[3];
> + __u32 bg_block_bitmap_hi; /* Blocks bitmap block MSB */
> + __u32 bg_inode_bitmap_hi; /* Inodes bitmap block MSB */
> + __u32 bg_inode_table_hi; /* Inodes table block MSB */
> + __u16 bg_free_blocks_count_hi; /* Free blocks count MSB */
> + __u16 bg_free_inodes_count_hi; /* Free inodes count MSB */
> + __u16 bg_used_dirs_count_hi; /* Directories count MSB */
> + __u32 bg_reserved2[3];
> +};
> +
> #define EXT2_BG_INODE_UNINIT 0x0001 /* Inode table/bitmap not initialized */
> #define EXT2_BG_BLOCK_UNINIT 0x0002 /* Block bitmap not initialized */
>
> @@ -524,12 +543,15 @@
> __u32 s_hash_seed[4]; /* HTREE hash seed */
> __u8 s_def_hash_version; /* Default hash version to use */
> __u8 s_jnl_backup_type; /* Default type of journal backup */
> - __u16 s_reserved_word_pad;
> + __u16 s_desc_size; /* Group desc. size: INCOMPAT_64BIT */
> __u32 s_default_mount_opts;
> __u32 s_first_meta_bg; /* First metablock group */
> __u32 s_mkfs_time; /* When the filesystem was created */
> __u32 s_jnl_blocks[17]; /* Backup of the journal inode */
> - __u32 s_reserved[172]; /* Padding to the end of the block */
> + __u32 s_blocks_count_hi; /* Blocks count high 32bits */
> + __u32 s_r_blocks_count_hi; /* Reserved blocks count high 32 bits*/
> + __u32 s_free_blocks_hi; /* Free blocks count */
I'd prefer s_free_blocks_count_hi
> + __u32 s_reserved[169]; /* Padding to the end of the block */
> };
Regards,
Valérie
next prev parent reply other threads:[~2006-10-18 13:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-18 6:18 [PATCH, E2FSPROGS] On-disk format definition for 64-bit support Theodore Ts'o
2006-10-18 13:30 ` Valerie Clement [this message]
2006-10-18 17:43 ` Theodore Tso
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=45362C90.4030305@bull.net \
--to=valerie.clement@bull.net \
--cc=linux-ext4@vger.kernel.org \
--cc=tytso@mit.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.