From: Jeff Mahoney <jeffm@suse.com>
To: Mike Young <myoung@wildernessvoice.com>
Cc: reiserfs-list@namesys.com
Subject: Re: ACL Support
Date: Thu, 01 Apr 2004 16:48:31 -0500 [thread overview]
Message-ID: <406C8E2F.2070304@suse.com> (raw)
In-Reply-To: <200404012043.MAA12517@amber.he.net>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Mike Young wrote:
| Wow Jeff! That's a great explanation and very helpful too. Can you
answer
| a couple more questions for me on the v3.x reiserfs? I'm trying to
| understand the limits right now. For example, how big of a volume can I
| support? How large of a file? And how many files?
|
| I actually have a problem in that I've got files that are 2TB in size--
| nothing bigger, though.
Mike -
The on-disk format for ReiserFS v3 defines the maximum filesystem size
as 2^32 * blocksize, which is currently limited by the size of a page on
the system. So, 16 TB assuming a 4k blocksize. The maximum file size is
2^61-1bytes, but is obviously limited by the maximum size of the
filesystem. The maximum number of files is 2^32.
If you're using a 2.4 kernel, you're not going to be able to handle that
workload using any filesystem, since block devices are limited to 2^32 *
512 bytes = 2 TB. This, in turn, limits all filesystems to 2 TB in size.
Using the 2.6 kernel, the block device limits have been raised, so
ReiserFS can use its maximum capacity.
- -Jeff
- --
Jeff Mahoney
SuSE Labs
jeffm@suse.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFAbI4vLPWxlyuTD7IRAsaSAJwIN8Vv/W+LVO5xA2muNWhAsuusAACfV2sn
eX23G/LcEyflt0svSywvIUM=
=Bi+O
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2004-04-01 21:48 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-01 16:50 ACL Support Mike Young
2004-04-01 17:11 ` Christian Mayrhuber
2004-04-01 19:05 ` Jeff Mahoney
2004-04-01 20:43 ` Mike Young
2004-04-01 21:48 ` Jeff Mahoney [this message]
2004-04-01 22:11 ` Mike Young
-- strict thread matches above, loose matches on Subject: below --
2014-03-26 5:23 ACL support dE
2014-03-26 10:34 ` Edward Shishkin
2014-03-26 15:42 ` dE
2014-03-26 16:01 ` Edward Shishkin
2014-03-26 16:44 ` dE
2014-03-26 17:04 ` Edward Shishkin
2014-03-27 15:21 ` dE
2014-03-29 3:42 ` dE
[not found] ` <CAJZSrNLHanHHgAV-E=1bpnbq4FvqYETQkOQhdsrEwLza+Yd90w@mail.gmail.com>
2014-04-13 22:22 ` Edward Shishkin
2002-03-07 20:58 pelletierma
2002-03-07 23:25 ` Andreas Dilger
2002-03-05 20:32 pelletierma
2002-03-06 3:38 ` Andreas Dilger
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=406C8E2F.2070304@suse.com \
--to=jeffm@suse.com \
--cc=myoung@wildernessvoice.com \
--cc=reiserfs-list@namesys.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.