public inbox for linux-ext4@vger.kernel.org
 help / color / mirror / Atom feed
From: Goswin von Brederlow <goswin-v-b@web.de>
To: "Jose R. Santos" <jrs@us.ibm.com>
Cc: Andreas Dilger <adilger@sun.com>,
	Goswin von Brederlow <goswin-v-b@web.de>,
	linux-ext4@vger.kernel.org
Subject: Re: ext4 64bit (disk >16TB) question
Date: Wed, 16 Jul 2008 12:10:31 +0200	[thread overview]
Message-ID: <87r69u9m20.fsf@frosties.localdomain> (raw)
In-Reply-To: <20080715162003.061c745a@ichigo> (Jose R. Santos's message of "Tue, 15 Jul 2008 16:20:03 -0500")

"Jose R. Santos" <jrs@us.ibm.com> writes:

> block boundary.  Dont have large disk to test on so Im playing with
> device mapper to see how I can fake one.  Our lab network is making
> thing difficult though.

Download

http://www.bullopensource.org/ext4/files/sparse_create

and for 32TiB use

dd if=/dev/zero of=/somewhere/SPACE bs=1 count=1 seek=100000000000
losetup /dev/loop0 /somewhere/SPACE
./sparse_create ext4dev /dev/loop0 68719476736

If you have a real block device to spare use that directly.

MfG
        Goswin

      reply	other threads:[~2008-07-16 10:10 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-14 19:50 ext4 64bit (disk >16TB) question Goswin von Brederlow
2008-07-14 23:46 ` Theodore Tso
2008-07-15  5:42   ` Goswin von Brederlow
2008-07-15 12:36     ` Theodore Tso
2008-07-15 17:00       ` Goswin von Brederlow
2008-07-15 17:19         ` Theodore Tso
2008-07-15 13:16     ` Ric Wheeler
2008-07-15 14:01       ` Bernd Schubert
2008-07-15 14:08         ` Ric Wheeler
2008-07-15 16:13           ` Goswin von Brederlow
2008-07-15 18:27 ` Jose R. Santos
2008-07-15 20:12   ` Andreas Dilger
2008-07-15 20:15     ` Ric Wheeler
2008-07-15 21:03       ` Goswin von Brederlow
2008-07-15 21:20     ` Jose R. Santos
2008-07-16 10:10       ` Goswin von Brederlow [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=87r69u9m20.fsf@frosties.localdomain \
    --to=goswin-v-b@web.de \
    --cc=adilger@sun.com \
    --cc=jrs@us.ibm.com \
    --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