From: Christoph Hellwig <hch@lst.de>
To: Andrey Albershteyn <aalbersh@kernel.org>
Cc: linux-xfs@vger.kernel.org
Subject: [PATCH 2/2] growfs: clarify the man page a bit
Date: Thu, 30 Jul 2026 14:28:16 +0200 [thread overview]
Message-ID: <20260730122841.2591200-3-hch@lst.de> (raw)
In-Reply-To: <20260730122841.2591200-1-hch@lst.de>
While no RT section needs to exist for GROWFS_RT to work, the buftarg
must point to a block device already.
Signed-off-by: Christoph Hellwig <hch@lst.de>
---
man/man8/xfs_growfs.8 | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/man/man8/xfs_growfs.8 b/man/man8/xfs_growfs.8
index d6e5fe13e943..1aa57fb0308f 100644
--- a/man/man8/xfs_growfs.8
+++ b/man/man8/xfs_growfs.8
@@ -151,7 +151,8 @@ the real-time section is grown to the largest size possible with the
option. The filesystem does not need to have contained a real-time section
before the
.B xfs_growfs
-operation.
+operation, but it must have been mounted with the -o rtdev option pointing
+to a block device.
.TP
.B \-t
Specifies an alternate mount table file (default is
--
2.53.0
next prev parent reply other threads:[~2026-07-30 12:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-30 12:28 make the size options to xfs_growfs a bit more useful v2 Christoph Hellwig
2026-07-30 12:28 ` [PATCH 1/2] growfs: support unit postfixes when specifying sizes Christoph Hellwig
2026-07-30 15:49 ` Darrick J. Wong
2026-07-30 12:28 ` Christoph Hellwig [this message]
2026-07-30 15:44 ` [PATCH 2/2] growfs: clarify the man page a bit Darrick J. Wong
-- strict thread matches above, loose matches on Subject: below --
2026-07-30 12:25 make the size options to xfs_growfs a bit more useful Christoph Hellwig
2026-07-30 12:25 ` [PATCH 2/2] growfs: clarify the man page a bit Christoph Hellwig
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=20260730122841.2591200-3-hch@lst.de \
--to=hch@lst.de \
--cc=aalbersh@kernel.org \
--cc=linux-xfs@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