From: Farkas Levente <lfarkas@bppiac.hu>
To: Neil Brown <neilb@suse.de>
Cc: Joshua Baker-LePain <jlb17@duke.edu>, linux-raid@vger.kernel.org
Subject: Re: maximum size
Date: Tue, 04 Oct 2005 12:16:25 +0200 [thread overview]
Message-ID: <43425679.3050601@bppiac.hu> (raw)
In-Reply-To: <17217.49985.339220.524306@cse.unsw.edu.au>
Neil Brown wrote:
> On Wednesday September 28, jlb17@duke.edu wrote:
>
>>On Wed, 28 Sep 2005 at 10:56am, Neil Brown wrote
>>
>>
>>>On Tuesday September 27, lfarkas@bppiac.hu wrote:
>>
>>>>suppose i create the raid device with:
>>>>mdadm --create /dev/md0--level=5 --raid-devices=8 --spare-devices=1
>>>>/dev/sd[abcdefgh]1
>>>>then what is the maximum size for /dev/md0?
>>>>(or more precisely after a mkfs.ext3 /dev/md0).
>>>
>>>The /dev/sdX1 cannot be larger than 2TB. The /dev/md0 can be as big
>>>as you like. The filesystem can be as big as your filesystem allows.
>>>I don't think ext3 can exceed 2 TB (I could be wrong). Other
>>
>>RH (e.g.) officially supports ext3 FSs up to 8TB in RHEL4.
>
>
> See... I was wrong! :-)
>
> I'm sure there is a 32bit limit somewhere, so it's probably that block
> addresses are limited to 32 bits. With 4K blocks, that's 2^34 K, or
> 16TB.... Maybe there is some confusion with the sign bit, making it on
> 2^33K, or 8TB.
i already find the trivial source kernel/Documentation/filesystems/ext2.txt:
---------------------------------
Filesystem block size: 1kB 2kB 4kB 8kB
File size limit: 16GB 256GB 2048GB 2048GB
Filesystem size limit: 2047GB 8192GB 16384GB 32768GB
---------------------------------
--
Levente "Si vis pacem para bellum!"
next prev parent reply other threads:[~2005-10-04 10:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-27 13:21 maximum size Farkas Levente
2005-09-27 13:28 ` Brad Campbell
2005-09-27 13:31 ` Neil Brown
2005-09-27 13:51 ` Farkas Levente
2005-09-28 8:56 ` Neil Brown
2005-09-28 12:27 ` Joshua Baker-LePain
2005-10-03 23:48 ` Neil Brown
2005-10-04 10:16 ` Farkas Levente [this message]
2005-09-28 12:50 ` Brad Campbell
2005-09-27 16:18 ` Brad Dameron
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=43425679.3050601@bppiac.hu \
--to=lfarkas@bppiac.hu \
--cc=jlb17@duke.edu \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.de \
/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;
as well as URLs for NNTP newsgroup(s).