All of lore.kernel.org
 help / color / mirror / Atom feed
From: rpeterso@sourceware.org <rpeterso@sourceware.org>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] cluster/gfs2/man gfs2_tool.8
Date: 26 Jul 2007 23:20:59 -0000	[thread overview]
Message-ID: <20070726232059.28940.qmail@sourceware.org> (raw)

CVSROOT:	/cvs/cluster
Module name:	cluster
Branch: 	RHEL5
Changes by:	rpeterso at sourceware.org	2007-07-26 23:20:59

Modified files:
	gfs2/man       : gfs2_tool.8 

Log message:
	Resolves: bug #248423: gfs2_tool can not set data journal flags as
	specified in the man page.

Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/cluster/gfs2/man/gfs2_tool.8.diff?cvsroot=cluster&only_with_tag=RHEL5&r1=1.3&r2=1.3.2.1

--- cluster/gfs2/man/gfs2_tool.8	2006/05/05 18:12:09	1.3
+++ cluster/gfs2/man/gfs2_tool.8	2007/07/26 23:20:59	1.3.2.1
@@ -1,5 +1,5 @@
 .\"  Copyright (C) Sistina Software, Inc.  1997-2003  All rights reserved.
-.\"  Copyright (C) 2004 Red Hat, Inc.  All rights reserved.
+.\"  Copyright (C) 2004-2007 Red Hat, Inc.  All rights reserved.
 
 .TH gfs2_tool 8
 
@@ -100,38 +100,30 @@
 Print out the superblock.
 .TP
 \fBsetflag\fP \fIFlag\fR \fIFile1\fR \fIFile2\fR \fI...\fR 
-Set an attribute flag on a file.  There are eight currently
-supported flags.  They are jdata, directio, immutable, appendonly,
-noatime, sync, inherit_jdata, and inherit_directio.
-  
-The \fIjdata\fR flag causes all the data written to a regular file
-to be journaled. The jdata flag can only be set (or cleared) if the file
-is zero length.
+Set an attribute flag on a file.  There are five currently
+supported flags.  They are directio, immutable, appendonly,
+noatime, and sync.  In most cases, the chattr command may be used
+rather than gfs2_tool to set attributes.
 
 The \fIdirectio\fR flag causes all I/O to a regular file to be Direct
 I/O, even if the O_DIRECT flag isn't used on the open() command.
 
 The \fIimmutable\fR flag marks the file immutable. The behavior is 
-similar to the immutable flag in the ext2/3 filesystems. All write 
-access is denied.
+similar to the immutable flag in the ext2/3 filesystems.  All write 
+access is denied.  Same as chattr +i.
 
 The \fIappendonly\fR flag causes all data to be written at the end of 
-the file.
+the file.  Same as chattr +a.
 
 The \fInoatime\fR flag disables updates to the file's access time.
+Same as chattr +A.
 
 The \fIsync\fR flag causes data written to the file to be sync'ed to 
-stable storage immediately.
+stable storage immediately.  Same as chattr +S.
 
-The \fIinherit_jdata\fR flag is set on a directory.  It causes all new
-regular files created in that directory automatically inherit the
-\fIjdata\fR flag.  The \fIinherit_jdata\fR is also inherited by any new
-subdirectories created in that directory.
-
-The \fIinherit_directio\fR flag is set on a directory.  It causes all new
-regular files created in that directory automatically inherit the
-\fIdirectio\fR flag.  The \fIinherit_directio\fR is also inherited by
-any new subdirectories created in that directory.
+Note: Unlike the original gfs_tool, the journaled data (\fIjdata\fR) flag 
+is set with chattr +j and reset with chattr -j.  Likewise, the
+\fIinherit_jdata\fR flag is set on a directory with chattr +j.
 .TP
 \fBsettune\fP \fIMountPoint\fR \fIparameter\fR \fInewvalue\fR
 Set the value of tuning parameter.  Use \fBgettune\fP for a listing of 



             reply	other threads:[~2007-07-26 23:20 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-26 23:20 rpeterso [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-01-09 21:30 [Cluster-devel] cluster/gfs2/man gfs2_tool.8 rpeterso
2008-01-09 21:30 rpeterso
2007-11-07 21:15 rpeterso
2007-11-07 21:14 rpeterso
2007-07-26 23:22 rpeterso
2007-07-26 23:19 rpeterso

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=20070726232059.28940.qmail@sourceware.org \
    --to=rpeterso@sourceware.org \
    /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.