From: rpeterso@sourceware.org <rpeterso@sourceware.org>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] cluster/gfs2/man gfs2_tool.8
Date: 7 Nov 2007 21:14:51 -0000 [thread overview]
Message-ID: <20071107211451.2898.qmail@sourceware.org> (raw)
CVSROOT: /cvs/cluster
Module name: cluster
Changes by: rpeterso at sourceware.org 2007-11-07 21:14:50
Modified files:
gfs2/man : gfs2_tool.8
Log message:
Resolves: bz 336561: gfs2_tool accepts jdata flag; man page says no
Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/cluster/gfs2/man/gfs2_tool.8.diff?cvsroot=cluster&r1=1.5&r2=1.6
--- cluster/gfs2/man/gfs2_tool.8 2007/10/30 14:06:06 1.5
+++ cluster/gfs2/man/gfs2_tool.8 2007/11/07 21:14:50 1.6
@@ -103,11 +103,17 @@
Print out the superblock.
.TP
\fBsetflag\fP \fIFlag\fR \fIFile1\fR \fIFile2\fR \fI...\fR
-Set an attribute flag on a file. There are five currently
-supported flags. They are directio, immutable, appendonly,
+Set an attribute flag on a file. There are six currently
+supported flags. They are jdata, directio, immutable, appendonly,
noatime, and sync. In most cases, the chattr command may be used
rather than gfs2_tool to set attributes.
+The \fIjdata\fR flag causes all the data written to a file
+to be journaled. If the \fIjdata\fR flag is set for a directory,
+all files and directories subsequently created within that directory
+are also journaled. This behavior replaces the old \fIinherit_jdata\fR
+flag from gfs. Same as chattr +j.
+
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.
@@ -123,10 +129,6 @@
The \fIsync\fR flag causes data written to the file to be sync'ed to
stable storage immediately. Same as chattr +S.
-
-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
next reply other threads:[~2007-11-07 21:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-07 21:14 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-07-26 23:22 rpeterso
2007-07-26 23:20 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=20071107211451.2898.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 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 NNTP newsgroup(s).