public inbox for cluster-cvs@sourceware.org
help / color / mirror / Atom feed
From: Steven Whitehouse <swhiteho@fedoraproject.org>
To: cluster-cvs-relay@redhat.com
Subject: cluster: STABLE3 - man: Remove obsolete info from mount.gfs2 man page
Date: Wed, 27 May 2009 10:20:00 -0000	[thread overview]
Message-ID: <20090527101956.6B3E2120373@lists.fedorahosted.org> (raw)

Gitweb:        http://git.fedorahosted.org/git/cluster.git?p=cluster.git;a=commitdiff;h=5ac843f511e14f46c54a500c3f3c2dd7d5d2c0a4
Commit:        5ac843f511e14f46c54a500c3f3c2dd7d5d2c0a4
Parent:        682d8b2ab1b6b4e8857ddd1b49da853b89e5b69c
Author:        Steven Whitehouse <swhiteho@redhat.com>
AuthorDate:    Tue May 26 10:49:55 2009 +0100
Committer:     Steven Whitehouse <swhiteho@redhat.com>
CommitterDate: Wed May 27 10:08:27 2009 +0100

man: Remove obsolete info from mount.gfs2 man page

Signed-off-by: Steven Whitehouse <swhiteho@redhat.com>
---
 gfs2/man/mount.gfs2.8 |   23 -----------------------
 1 files changed, 0 insertions(+), 23 deletions(-)

diff --git a/gfs2/man/mount.gfs2.8 b/gfs2/man/mount.gfs2.8
index 96d7b62..125e404 100644
--- a/gfs2/man/mount.gfs2.8
+++ b/gfs2/man/mount.gfs2.8
@@ -41,20 +41,6 @@ interpreted by the mount command nor by the kernel's Virtual File System.  GFS2
 and non-GFS2 options may be intermingled after the \fB-o\fP, separated by
 commas (but no spaces).
 
-As an alternative to mount command line options, you may send mount
-options to gfs2 using "gfs2_tool margs" (after loading the gfs2 kernel
-module, but before mounting GFS2).  For example, you may need to do
-this when working from an initial ramdisk \fBinitrd\fP(4).  The
-options are restricted to the ones described on this man page (no
-general \fBmount\fP(8) options will be recognized), must not be
-preceded by -o, and must be separated by commas (no spaces).  Example:
-
-# gfs2_tool margs "lockproto=lock_nolock,ignore_local_fs"
-
-Options loaded via "gfs2_tool margs" have a lifetime of only one GFS2
-mount.  If you wish to mount another GFS2 filesystem, you must set
-another group of options with "gfs2_tool margs".
-
 The options debug, acl, quota, suiddir, and data can be
 changed after mount using the "mount -o remount,option /mountpoint" command.
 The options debug, acl, and suiddir support the "no"
@@ -142,15 +128,6 @@ message that you need to upgrade.  Try mounting again, using the
 \fB-o upgrade\fP option.  When upgrading, only one node may mount the GFS2
 filesystem.
 .TP
-\fBnum_glockd=\fP\fINumber\fR
-Tunes GFS2 to alleviate memory pressure when rapidly acquiring many locks (e.g.
-several processes scanning through huge directory trees).  GFS2' glockd kernel
-daemon cleans up memory for no-longer-needed glocks.  Multiple instances
-of the daemon clean up faster than a single instance.  The default value is
-one daemon, with a maximum of 16.  Since this option was introduced, other
-methods of rapid cleanup have been developed within GFS2, so this option may go
-away in the future.
-.TP
 \fBacl\fP
 Enables POSIX Access Control List \fBacl\fP(5) support within GFS2.
 .TP


                 reply	other threads:[~2009-05-27 10:20 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20090527101956.6B3E2120373@lists.fedorahosted.org \
    --to=swhiteho@fedoraproject.org \
    --cc=cluster-cvs-relay@redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).