From: Eric Biggers <ebiggers@kernel.org>
To: linux-ext4@vger.kernel.org
Cc: linux-fscrypt@vger.kernel.org
Subject: [PATCH 3/4] ext4.5: document the stable_inodes feature
Date: Wed, 1 Apr 2020 13:32:38 -0700 [thread overview]
Message-ID: <20200401203239.163679-4-ebiggers@kernel.org> (raw)
In-Reply-To: <20200401203239.163679-1-ebiggers@kernel.org>
From: Eric Biggers <ebiggers@google.com>
Signed-off-by: Eric Biggers <ebiggers@google.com>
---
misc/ext4.5.in | 16 ++++++++++++++++
1 file changed, 16 insertions(+)
diff --git a/misc/ext4.5.in b/misc/ext4.5.in
index 1db61a5f..90bc4f88 100644
--- a/misc/ext4.5.in
+++ b/misc/ext4.5.in
@@ -299,6 +299,20 @@ feature is essentially a more extreme version of sparse_super and is
designed to allow a much larger percentage of the disk to have
contiguous blocks available for data files.
.TP
+.B stable_inodes
+.br
+Marks the filesystem's inode numbers and UUID as stable.
+.BR resize2fs (8)
+will not allow shrinking a filesystem with this feature, nor
+will
+.BR tune2fs (8)
+allow changing its UUID. This feature allows the use of specialized encryption
+settings that make use of the inode numbers and UUID. Note that the
+.B encrypt
+feature still needs to be enabled separately.
+.B stable_inodes
+is a "compat" feature, so old kernels will allow it.
+.TP
.B uninit_bg
.br
This ext4 file system feature indicates that the block group descriptors
@@ -788,6 +802,8 @@ ext4, 4.13
ext4, 5.2
.IP "\fBverity\fR" 2i
ext4, 5.4
+.IP "\fBstable_inodes\fR" 2i
+ext4, 5.5
.SH SEE ALSO
.BR mke2fs (8),
.BR mke2fs.conf (5),
--
2.26.0.rc2.310.g2932bb562d-goog
next prev parent reply other threads:[~2020-04-01 20:35 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-01 20:32 [PATCH 0/4] e2fsprogs: fix and document the stable_inodes feature Eric Biggers
2020-04-01 20:32 ` [PATCH 1/4] tune2fs: prevent changing UUID of fs with " Eric Biggers
2020-04-02 2:19 ` Andreas Dilger
2020-04-07 5:32 ` Eric Biggers
2020-04-07 16:18 ` Andreas Dilger
2020-04-08 3:11 ` Eric Biggers
2020-04-10 11:53 ` Andreas Dilger
2020-04-10 15:06 ` Theodore Y. Ts'o
2020-04-10 16:30 ` Eric Biggers
2020-04-01 20:32 ` [PATCH 2/4] tune2fs: prevent stable_inodes feature from being cleared Eric Biggers
2020-04-01 20:32 ` Eric Biggers [this message]
2020-04-01 20:32 ` [PATCH 4/4] tune2fs.8: document the stable_inodes feature Eric Biggers
2020-04-02 2:12 ` Andreas Dilger
2020-04-07 5:10 ` Eric Biggers
2020-04-10 15:24 ` [PATCH 0/4] e2fsprogs: fix and " Theodore Y. Ts'o
2020-05-07 18:18 ` Eric Biggers
2020-06-15 22:22 ` Eric Biggers
2020-07-27 16:45 ` Eric Biggers
2020-09-01 16:19 ` Eric Biggers
2020-09-21 22:41 ` Eric Biggers
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=20200401203239.163679-4-ebiggers@kernel.org \
--to=ebiggers@kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fscrypt@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 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.