public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Niv Sardi <xaiki@cxhome.ath.cx>
To: xfs@oss.sgi.com
Cc: xfs-dev@sgi.com
Subject: [REVIEW] mkfs.xfs man page needs the default settings updated.
Date: Tue, 04 Mar 2008 16:36:59 +1100	[thread overview]
Message-ID: <ncc8x0zhwxw.fsf@sgi.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 79 bytes --]


Manpages update for the new defaults, please review, I believe I got'em all.


[-- 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: 3481 bytes --]

>From 71011d480d52aaefe99ef252dfff513bf77f209e 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 |   44 +++++------------------------------------
 1 files changed, 6 insertions(+), 38 deletions(-)

diff --git a/xfsprogs/man/man8/mkfs.xfs.8 b/xfsprogs/man/man8/mkfs.xfs.8
index b6024c3..f9a89af 100644
--- a/xfsprogs/man/man8/mkfs.xfs.8
+++ b/xfsprogs/man/man8/mkfs.xfs.8
@@ -304,7 +304,8 @@ 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.
@@ -327,16 +328,10 @@ that does not have the inode alignment feature
 .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
+By default, this is 2.  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.
+the available inline inode space than version one does.
 .RE
 .TP
 .BI \-l " log_section_options"
@@ -389,15 +384,9 @@ 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 the logbsize to be increased beyond 32K.
 .TP
 .BI sunit= value
 This specifies the alignment to be used for log writes. The
@@ -430,27 +419,6 @@ suffixes). This value must be a multiple of the filesystem block size.
 Version 2 logs are automatically selected if the log
 .B su
 suboption is specified.
-.TP
-.BI lazy-count= value
-This changes the method of logging various persistent counters
-in the superblock.  Under metadata intensive workloads, these
-counters are updated and logged frequently enough that the superblock
-updates become a serialisation point in the filesystem. The
-.I value
-can be either 0 or 1.
-.IP
-With
-.BR lazy-count=1 ,
-the superblock is not modified or logged on every change of the
-persistent counters. Instead, enough information is kept in
-other parts of the filesystem to be able to maintain the persistent
-counter values without needed to keep them in the superblock.
-This gives significant improvements in performance on some configurations.
-The default
-.I value
-is 0 (off) so you must specify
-.B lazy-count=1
-if you want to make use of this feature.
 .RE
 .TP
 .BI \-n " naming_options"
-- 
1.5.4.1


[-- Attachment #3: Type: text/plain, Size: 15 bytes --]


-- 
Niv Sardi

             reply	other threads:[~2008-03-04  5:37 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-04  5:36 Niv Sardi [this message]
2008-03-04 15:38 ` [REVIEW] mkfs.xfs man page needs the default settings updated Eric Sandeen
2008-03-04 15:46   ` Eric Sandeen
2008-03-06  4:41     ` [REVIEW] mkfs.xfs man page needs the default settings updated, TAKE 2 Niv Sardi
2008-03-06  5:29       ` 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=ncc8x0zhwxw.fsf@sgi.com \
    --to=xaiki@cxhome.ath.cx \
    --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