From: Eric Sandeen <sandeen@sandeen.net>
To: Carlos Maiolino <cmaiolino@redhat.com>
Cc: xfs@oss.sgi.com
Subject: Re: [PATCH] mkfs: update manpage to match current inode allocation behaviour
Date: Thu, 18 Oct 2012 17:38:45 -0500 [thread overview]
Message-ID: <508084F5.5020602@sandeen.net> (raw)
In-Reply-To: <1350574957-1044-1-git-send-email-cmaiolino@redhat.com>
On 10/18/12 10:42 AM, Carlos Maiolino wrote:
> Once inode64 is the default allocator, mkfs man page needs to be updated to
> match the current behaviour.
>
> Signed-off-by: Carlos Maiolino <cmaiolino@redhat.com>
> ---
> man/man8/mkfs.xfs.8 | 7 ++++---
> 1 file changed, 4 insertions(+), 3 deletions(-)
>
> diff --git a/man/man8/mkfs.xfs.8 b/man/man8/mkfs.xfs.8
> index fa52152..c33cfb2 100644
> --- a/man/man8/mkfs.xfs.8
> +++ b/man/man8/mkfs.xfs.8
> @@ -309,16 +309,17 @@ can be allocated to inodes. The default
> is 25% for filesystems under 1TB, 5% for filesystems under 50TB and 1%
> for filesystems over 50TB.
> .IP
> -In the default inode allocation mode, inode blocks are chosen such
> +In the inode32 inode allocation mode, inode blocks are chosen such
> that inode numbers will not exceed 32 bits, which restricts the inode
> blocks to the lower portion of the filesystem. The data block
> allocator will avoid these low blocks to accommodate the specified
> maxpct, so a high value may result in a filesystem with nothing but
> inodes in a significant portion of the lower blocks of the filesystem.
> -(This restriction is not present when the filesystem is mounted with
> +(This restriction is not present in the default inode allocation mode,
> +i.e. when the filesystem is mounted with
> the
> .I "inode64"
> -option on 64-bit platforms).
> +option).
This is a little confusing - the "default" mode when "mounted with the -o inode64 option?"
If you mount with -o anything that's not quite default - or at best restating defaults.
How about:
(This restriction is not present in the default inode allocation mode,
i.e. when the filesystem is mounted without the
.I "inode32"
option).
-Eric
> .IP
> Setting the value to 0 means that essentially all of the filesystem
> can become inode blocks, subject to inode32 restrictions.
>
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2012-10-18 22:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-18 15:42 [PATCH] mkfs: update manpage to match current inode allocation behaviour Carlos Maiolino
2012-10-18 22:38 ` Eric Sandeen [this message]
2012-10-19 13:50 ` Carlos Maiolino
2012-11-02 22:20 ` Mark Tinguely
2012-11-02 22:24 ` Ben Myers
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=508084F5.5020602@sandeen.net \
--to=sandeen@sandeen.net \
--cc=cmaiolino@redhat.com \
--cc=xfs@oss.sgi.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