From: Eric Sandeen <sandeen@redhat.com>
To: ext4 development <linux-ext4@vger.kernel.org>
Subject: [PATCH 1/4] e2fsprogs: Document mmp commands in debugfs manpage
Date: Thu, 10 Nov 2011 16:51:28 -0600 [thread overview]
Message-ID: <4EBC5570.3060708@redhat.com> (raw)
In-Reply-To: <4EBC5524.3000105@redhat.com>
Document the dump_mmp and set_mmp_value commands in
the debugfs manpage.
Signed-off-by: Eric Sandeen <sandeen@redhat.com>
---
diff --git a/debugfs/debugfs.8.in b/debugfs/debugfs.8.in
index fe07f34..d0d1938 100644
--- a/debugfs/debugfs.8.in
+++ b/debugfs/debugfs.8.in
@@ -210,6 +210,9 @@ option is given set the owner, group and permissions information on
to match
.IR filespec .
.TP
+.I dump_mmp
+Display the multiple-mount protection (mmp) field values.
+.TP
.I dx_hash [-h hash_alg] [-s hash_seed] filename
Calculate the directory hash of
.IR filename .
@@ -485,6 +488,16 @@ The list of valid inode fields which can be set via this command
can be displayed by using the command:
.B set_inode_field -l
.TP
+.I set_mmp_value field value
+Modify the multiple-mount protection (mmp) data so that the
+mmp field
+.I field
+has value
+.I value.
+The list of valid mmp fields which can be set via this command
+can be displayed by using the command:
+.B set_mmp_value -l
+.TP
.I set_super_value field value
Set the superblock field
.I field
next prev parent reply other threads:[~2011-11-10 22:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-10 22:50 [PATCH 0/4] cleanup various mmp cruft & bugs Eric Sandeen
2011-11-10 22:51 ` Eric Sandeen [this message]
2011-11-12 2:12 ` [PATCH 1/4] e2fsprogs: Document mmp commands in debugfs manpage Ted Ts'o
2011-11-10 22:53 ` [PATCH 2/4] e2fsprogs: Tidy up mmp handling in debugfs Eric Sandeen
2011-11-12 2:12 ` Ted Ts'o
2011-11-10 23:00 ` [PATCH 3/4] e2fsprogs: Fix write size in ext2fs_mmp_write Eric Sandeen
2011-11-12 2:13 ` Ted Ts'o
2011-11-10 23:04 ` [PATCH 4/4] e2fsprogs: fix mmp tests on hard 4k devices (resend) Eric Sandeen
2011-11-12 2:13 ` Ted Ts'o
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=4EBC5570.3060708@redhat.com \
--to=sandeen@redhat.com \
--cc=linux-ext4@vger.kernel.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).