All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hans Reiser <reiser@namesys.com>
To: Nikita Danilov <Nikita@Namesys.COM>
Cc: Cyril Plisko <Cyril.Plisko@CloverleafComm.COM>,
	reiserfs-list@namesys.com
Subject: Re: Specification for ReiserFS4
Date: Tue, 09 Dec 2003 16:41:09 +0300	[thread overview]
Message-ID: <3FD5D0F5.7090208@namesys.com> (raw)
In-Reply-To: <16341.45920.686958.311924@laputa.namesys.com>

Nikita Danilov wrote:

>Cyril Plisko writes:
> > Anyone care to answer ?
> > 
> > On Wednesday 03 December 2003 18:22, Cyril Plisko wrote:
> > > Hello,
> > > 
> > > I am interesting in numbers similar to posted in
> > > http://www.namesys.com/faq.html
> > > There are various characteristic figures for max values
> > > for ReiserFS 3.5 and 3.6.  I cannot find such spec
> > > for ReiserFS4.
> > > 
> > > Can someone help ?
>
>Hello, and sorry for delay.
>
>"Specification" for reiser4:
>
>max number of files user can create on a single file system:  1152921504606846976   (2^60)
>
>max number files a directory can have:                        1152921504606846976   (2^60)
>
>max number sub-directories in a directory:                             4294967294   (2^32 - 2)
>
>max file size[1]:                                            18446744073709551615   (2^64 - 1)
>
>max number links to a file:                                            4294967296   (2^32)
>
>max filesystem size[2]:                                   75557863725914323419136   (2^64 * 4096)
>
>This is for default setup (per-directory limits are determined by
>directory plugin, maximal number of links is determined by stat-data
>plugin, etc.).
>
>[1] Current page cache limitations effectively limit maximal file size
>to 2^(32 + 12) == 2^44 == 17592186044416 bytes, on 32-bit architectures,
>but on-disk format provides for more.
>
>[2] Block IO sub-system currently limits device size to 2^64 * 512 ==
>9444732965739290427392, but on-disk format provides for more.
>
> > > 
> > > Regards,
> > > 	Cyril
> > > 
>
>Nikita.
>
> > > 
> > 
> > -- 
> > /~\  The ASCII Ribbon Campaign
> > \ /    No HTML/RTF in email
> >  X     No Word docs in email
> > / \  Respect for open standards
> > 
>
>
>  
>
Please put the numbers in our v4 documentation somewhere.  Can you say 
more about the 2^32 numbers?  Is it VFS constrained?

-- 
Hans



      reply	other threads:[~2003-12-09 13:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-03 16:22 Specification for ReiserFS4 Cyril Plisko
2003-12-09  6:55 ` Cyril Plisko
2003-12-09 11:34   ` Nikita Danilov
2003-12-09 13:41     ` Hans Reiser [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=3FD5D0F5.7090208@namesys.com \
    --to=reiser@namesys.com \
    --cc=Cyril.Plisko@CloverleafComm.COM \
    --cc=Nikita@Namesys.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.