From: "Takashi Sato" <sho@bsd.tnes.nec.co.jp>
To: "Andreas Dilger" <adilger@clusterfs.com>
Cc: "Badari Pulavarty" <pbadari@gmail.com>,
"lkml" <linux-kernel@vger.kernel.org>,
"ext2-devel" <Ext2-devel@lists.sourceforge.net>
Subject: Re: [Ext2-devel] [PATCH 2/2] ext2/3: Support 2^32-1blocks(e2fsprogs)
Date: Sat, 18 Mar 2006 22:17:25 +0900 [thread overview]
Message-ID: <00e801c64a8e$4f5a3080$4168010a@bsd.tnes.nec.co.jp> (raw)
In-Reply-To: <20060318101102.GZ30801@schatzie.adilger.int>
Hi,
> On Mar 18, 2006 14:57 +0900, Takashi Sato wrote:
>> >elm3b29:~/e2fsprogs-1.38/misc # ./mke2fs /dev/md0
>> >mke2fs 1.38 (30-Jun-2005)
>> >mke2fs: Filesystem too large. No more than 2**31-1 blocks
>> > (8TB using a blocksize of 4k) are currently supported.
>> >
>> >When I try to create "ext3":
>>
>> As I said in my previous mail, You should specify -F option to
>> create ext2/3 which has more than 2**31-1 blocks.
>> It is because of the compatibility.
>
> Oh, using -F for this is highly dangerous. That would allow mke2fs to
> run on e.g. a mounted filesystem or something. Instead use an option
> like "-E 16tb" or something.
I would like to integrate the function into new option "-O large_block"
in my mail "[PATCH 1/4] ext2/3: Extends the max file size(ext2 in kernel)".
next prev parent reply other threads:[~2006-03-18 13:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-15 12:39 [PATCH 2/2] ext2/3: Support 2^32-1 blocks(e2fsprogs) Takashi Sato
2006-03-17 21:19 ` [Ext2-devel] " Badari Pulavarty
2006-03-18 5:57 ` [Ext2-devel] [PATCH 2/2] ext2/3: Support 2^32-1blocks(e2fsprogs) Takashi Sato
2006-03-18 10:11 ` Andreas Dilger
2006-03-18 12:24 ` Theodore Ts'o
2006-03-18 13:17 ` Takashi Sato [this message]
2006-03-22 23:45 ` Badari Pulavarty
2006-03-23 18:16 ` Badari Pulavarty
2006-03-24 1:54 ` [Ext2-devel] [PATCH 2/2] ext2/3: Support2^32-1blocks(e2fsprogs) Takashi Sato
2006-03-19 2:44 ` [Ext2-devel] [PATCH 2/2] ext2/3: Support 2^32-1 blocks(e2fsprogs) Theodore Ts'o
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='00e801c64a8e$4f5a3080$4168010a@bsd.tnes.nec.co.jp' \
--to=sho@bsd.tnes.nec.co.jp \
--cc=Ext2-devel@lists.sourceforge.net \
--cc=adilger@clusterfs.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pbadari@gmail.com \
/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
all inboxes | Powered by JetHome®