From: Niv Sardi <xaiki@sgi.com>
To: Eric Sandeen <sandeen@sandeen.net>
Cc: xfs@oss.sgi.com, xfs-dev@sgi.com
Subject: Re: [REVIEW] mkfs.xfs man page needs the default settings updated, TAKE 2.
Date: Thu, 06 Mar 2008 15:41:29 +1100 [thread overview]
Message-ID: <ncczltcfoqu.fsf_-_@sgi.com> (raw)
In-Reply-To: <47CD6ED7.5050505@sandeen.net> (Eric Sandeen's message of "Tue, 04 Mar 2008 09:46:31 -0600")
[-- Attachment #1: Type: text/plain, Size: 74 bytes --]
Thanks to Eric for the comments, is this better ?
Cheers,
--
Niv Sardi
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: 0001-Update-mkfs-manpage-for-new-defaults.patch --]
[-- Type: text/x-diff, Size: 3452 bytes --]
>From 7e0e328663858ecf13f35678f1a6d349c3d4dd5a Mon Sep 17 00:00:00 2001
From: Niv Sardi <xaiki@sgi.com>
Date: Fri, 22 Feb 2008 16:48:32 +1100
Subject: [PATCH] Update mkfs manpage for new defaults:
log, attr and inodes v2,
Drop the ability to turn unwritten extents off completly,
reduce imaxpct for big filesystems, less AGs for single disks configs.
---
xfsprogs/man/man8/mkfs.xfs.8 | 41 ++++++++++++++++++-----------------------
1 files changed, 18 insertions(+), 23 deletions(-)
diff --git a/xfsprogs/man/man8/mkfs.xfs.8 b/xfsprogs/man/man8/mkfs.xfs.8
index b6024c3..afc284c 100644
--- a/xfsprogs/man/man8/mkfs.xfs.8
+++ b/xfsprogs/man/man8/mkfs.xfs.8
@@ -304,10 +304,16 @@ bits.
This specifies the maximum percentage of space in the filesystem that
can be allocated to inodes. The default
.I value
-is 25%. Setting the
+is 25% for filesystems under 1TB, 5% for filesystems under 50TB and 1%
+for filesystems over 50TB. Setting the
.I value
-to 0 means that essentially all of the filesystem can
-become inode blocks.
+to 0 means that essentially all of the filesystem can become inode
+blocks. Note that this is only used by inode32 (on 32bits platforms),
+and is ignored on 64bits platforms. On 32 bits platforms, we can only
+use the first TB of disk space for inodes, so the allocator will try
+to avoid this region, hence miss-using the first AG if this is set to
+high (the worst case is a 4TB filesystem where a full AG will be
+untouched by anything but inodes with a 25% maxpct).
.TP
.BI align[= value ]
This is used to specify that inode allocation is or is not aligned. The
@@ -325,18 +331,11 @@ that does not have the inode alignment feature
(any release of IRIX before 6.2, and IRIX 6.2 without XFS patches).
.TP
.BI attr[= value ]
-This is used to specify the version of extended attribute inline allocation
-policy to be used.
-By default, this is zero. Once extended attributes are used for the
-first time, the version will be set to either one or two.
-The current version (two) uses a more efficient algorithm for managing
-the available inline inode space than version one does, however, for
-backward compatibility reasons (and in the absence of the
-.B attr=2
-mkfs option, or the
-.B attr2
-mount option), version one will be selected
-by default when attributes are first used on a filesystem.
+This is used to specify the version of extended attribute inline
+allocation policy to be used. By default, this is 2. The current
+version (two) uses a more efficient algorithm for managing the
+available inline inode space than version one does. This option is
+kept for backward compatibility, attr2 was added in kernel 2.6.16.
.RE
.TP
.BI \-l " log_section_options"
@@ -389,15 +388,11 @@ and directory block size, the minimum log size is larger than 512 blocks.
.BI version= value
This specifies the version of the log. The
.I value
-is either 1 or 2. Specifying
+is either 1 or 2 (the default is 2).
.B version=2
-enables the
-.B sunit
-suboption, and allows the logbsize to be increased beyond 32K.
-Version 2 logs are automatically selected if a log stripe unit
-is specified. See
-.BR sunit " and " su
-suboptions, below.
+allows bigger log buffer size (version 1 had a limit at 32K), and the
+use of the sunit and su options. Possibility to use version=1 is left
+for backward compatibility only.
.TP
.BI sunit= value
This specifies the alignment to be used for log writes. The
--
1.5.4.3
next prev parent reply other threads:[~2008-03-06 4:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-04 5:36 [REVIEW] mkfs.xfs man page needs the default settings updated Niv Sardi
2008-03-04 15:38 ` Eric Sandeen
2008-03-04 15:46 ` Eric Sandeen
2008-03-06 4:41 ` Niv Sardi [this message]
2008-03-06 5:29 ` [REVIEW] mkfs.xfs man page needs the default settings updated, TAKE 2 Eric Sandeen
2008-03-06 6:19 ` David Chinner
2008-03-06 6:12 ` David Chinner
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=ncczltcfoqu.fsf_-_@sgi.com \
--to=xaiki@sgi.com \
--cc=sandeen@sandeen.net \
--cc=xfs-dev@sgi.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