From: Eric Sandeen <sandeen@redhat.com>
To: xfs-oss <xfs@oss.sgi.com>
Subject: [PATCH RESEND] xfsprogs: add supported file attributes to xfs.5 manpage
Date: Wed, 20 Aug 2014 13:00:09 -0500 [thread overview]
Message-ID: <53F4E229.3010607@redhat.com> (raw)
The chattr(1) manpage now refers users to filesystem-specific
manpages for details on supported attributes, so add those to
xfs.5.
Signed-off-by: Eric Sandeen <sandeen@redhat.com>
---
I thought I had sent this already, but I guess not...
(and now resending to xfs@ not linux-xfs@ in hopes that this
one gets through...)
diff --git a/man/man5/xfs.5 b/man/man5/xfs.5
index 5e47c4c..3214455 100644
--- a/man/man5/xfs.5
+++ b/man/man5/xfs.5
@@ -1,6 +1,6 @@
.TH xfs 5
.SH NAME
-xfs \- layout and mount options for the XFS filesystem
+xfs \- layout, mount options, and supported file attributes for the XFS filesystem
.SH DESCRIPTION
An XFS filesystem can reside on a regular disk partition or on a
logical volume.
@@ -302,7 +302,27 @@ namespace is on stable storage. This is useful in HA setups
where failover must not result in clients seeing
inconsistent namespace presentation during or after a
failover event.
+.SH FILE ATTRIBUTES
+The XFS filesystem supports setting the following file
+attributes on Linux systems using the
+.BR chattr (1)
+utility:
+.sp
+.BR a " - append only"
+.sp
+.BR A " - no atime updates"
+.sp
+.BR d " - no dump"
+.sp
+.BR i " - immutable"
+.sp
+.BR S " - synchronous updates"
+.sp
+For descriptions of these attribute flags, please refer to the
+.BR chattr (1)
+man page.
.SH SEE ALSO
+.BR chattr (1),
.BR xfsctl (3),
.BR mount (8),
.BR mkfs.xfs (8),
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next reply other threads:[~2014-08-20 18:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-20 18:00 Eric Sandeen [this message]
2014-08-20 18:54 ` [PATCH RESEND] xfsprogs: add supported file attributes to xfs.5 manpage Troy McCorkell
2014-08-20 20:25 ` Eric Sandeen
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=53F4E229.3010607@redhat.com \
--to=sandeen@redhat.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 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.