From: Andreas Dilger <adilger@clusterfs.com>
To: Alexandre Ratchov <alexandre.ratchov@bull.net>
Cc: linux-ext4@vger.kernel.org
Subject: Re: [Ext2-devel] rfc: [patch 3/6] more e2fsprogs fixes
Date: Wed, 6 Sep 2006 04:47:32 -0600 [thread overview]
Message-ID: <20060906104732.GP20105@schatzie.adilger.int> (raw)
In-Reply-To: <20060904145941.GA9427@openx1.frec.bull.fr>
On Sep 04, 2006 16:59 +0200, Alexandre Ratchov wrote:
> in order tu use 48bit adressing, we have to use larger block groups (because
> all group descriptors must fit in one block group). So we'll need 16bit
> "_hi" bits for blocks_count, inodes_count and perhaps used_dirs_count. And
> this leaves no room for additional fields.
>
> There's already a patch that makes the descriptor structure size variable
> (similarly to the inode size), see marc.theaimsgroup.com/?m=114968738307171
> Here is the updated patch set:
It was always my desire to require the use of the larger group descriptors
when using a filesystem with > 32-bit blocks. That avoids the need to use
up the small group descriptors for the 64-bit block numbers, allowing them
to be used for other features that are still relevant for smaller filesystems
like checksums and UNINIT groups.
> linux-2.6.18-rc4:
>
> http://www.bullopensource.org/ext4/20060904/ext4-linux-2.6.18-rc4.tar.gz
>
> e2fsprogs-1.39:
>
> http://www.bullopensource.org/ext4/20060904/ext4-e2fsprogs-1.39.tar.gz
Cheers, Andreas
--
Andreas Dilger
Principal Software Engineer
Cluster File Systems, Inc.
prev parent reply other threads:[~2006-09-06 10:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20060825131138.GA20278@openx1.frec.bull.fr>
[not found] ` <20060825131840.GC20944@openx1.frec.bull.fr>
[not found] ` <20060825235049.GP6634@schatzie.adilger.int>
2006-09-04 14:59 ` [Ext2-devel] rfc: [patch 3/6] more e2fsprogs fixes Alexandre Ratchov
2006-09-06 10:47 ` Andreas Dilger [this message]
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=20060906104732.GP20105@schatzie.adilger.int \
--to=adilger@clusterfs.com \
--cc=alexandre.ratchov@bull.net \
--cc=linux-ext4@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox