public inbox for linux-ext4@vger.kernel.org
 help / color / mirror / Atom feed
From: "Jose R. Santos" <jrs@us.ibm.com>
To: "Jose R. Santos" <jrs@us.ibm.com>
Cc: Valerie Clement <valerie.clement@bull.net>,
	Theodore Tso <tytso@mit.edu>,
	ext4 development <linux-ext4@vger.kernel.org>
Subject: Re: [RFC][PATCH 4/12] convert some block types in e2fsprogs
Date: Tue, 12 Jun 2007 09:57:57 -0500	[thread overview]
Message-ID: <20070612095757.2f1fe23d@gara> (raw)
In-Reply-To: <20070611155930.0bbcccbf@gara>

On Mon, 11 Jun 2007 15:59:30 -0500
"Jose R. Santos" <jrs@us.ibm.com> wrote:

> On Mon, 11 Jun 2007 18:42:28 +0200
> Valerie Clement <valerie.clement@bull.net> wrote:
> 
> > This patch converts some int or unsigned int block number definitions
> > to blk_t type.  Most conversions are necessary for 64-bit porting.
> 
> What about unsigned long?  There are various places where block is
> represented by using unsigned long which is 32-bit when running 32 bit
> binaries. Most PPC64 distributions compile their user-space tools in
> 32-bit binaries.
> 
> I wonder how badly it will break.

I found a PPC64 box to test this out and it seems to break pretty badly
when compiled in the default 32bit mode.  Should ext2_get_device_size()
fail if the number of block is greater than 2**32 and the size of
unsigned long is 4?  At least until it can be verified that this will
work under 32bit binaries since it could corrupt a filesystem to do
an fsck.

mke2fs 1.39-tyt3 (29-Apr-2007)

Warning:Filesystem greater than 2**32 blocks, 64-bit incompatible feature forced.

Filesystem label=
OS type: Linux
Block size=1024 (log=0)
Fragment size=1024 (log=0)
4194304 inodes, 5 blocks
0 blocks (0.00%) reserved for the super user
First data block=1
524288 block groups
8192 blocks per group, 8192 fragments per group
8 inodes per group
Superblock backups stored on blocks: 
        267387660, 267387660, 267387660, 267387660, 267387660, 267387660, 267387660, 267387660, 267387660, 
        267387660, 267387660, 267387660, 267387660, 267387660, 267387660, 267387660, 
        267387660, 267387660, 267387660, 267387660, 267387660, 267387660, 
        267387660, 267387660, 267387660, 267387660

mke2fs: Could not allocate block in ext2 filesystem while trying to allocate filesystem tables


-JRS

      reply	other threads:[~2007-06-12 14:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-11 16:42 [RFC][PATCH 4/12] convert some block types in e2fsprogs Valerie Clement
2007-06-11 20:59 ` Jose R. Santos
2007-06-12 14:57   ` Jose R. Santos [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=20070612095757.2f1fe23d@gara \
    --to=jrs@us.ibm.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=tytso@mit.edu \
    --cc=valerie.clement@bull.net \
    /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