From: Viacheslav Dubeyko <Slava.Dubeyko@ibm.com>
To: Karel Zak <kzak@redhat.com>, "slava@dubeyko.com" <slava@dubeyko.com>
Cc: Alex Markuze <amarkuze@redhat.com>,
"util-linux@vger.kernel.org" <util-linux@vger.kernel.org>,
"ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
"idryomov@gmail.com" <idryomov@gmail.com>,
Pavan Rallabhandi <Pavan.Rallabhandi@ibm.com>,
Patrick Donnelly <pdonnell@redhat.com>
Subject: RE: [PATCH] mount: (manpage) add CephFS kernel client mount options
Date: Tue, 13 Jan 2026 19:29:00 +0000 [thread overview]
Message-ID: <c15ce83bf9ee6c5c37db193c33a77b52f0594564.camel@ibm.com> (raw)
In-Reply-To: <binwryzqlbprj2t3ybxb5kychdeenhtmadbe23hov44urszvn5@kpbbv3qks47c>
On Tue, 2026-01-13 at 20:14 +0100, Karel Zak wrote:
> On Mon, Jan 12, 2026 at 12:58:38PM -0800, Viacheslav Dubeyko wrote:
> > From: Viacheslav Dubeyko <Slava.Dubeyko@ibm.com>
> >
> > Currently, manpage for generic mount tool doesn't contain
> > explanation of CephFS kernel client mount options. This patch
> > adds the description of CephFS mount options into
> > file system specific mount options section.
> >
> > Signed-off-by: Viacheslav Dubeyko <Slava.Dubeyko@ibm.com>
> > ---
> > sys-utils/mount.8.adoc | 86 ++++++++++++++++++++++++++++++++++++++++++
> > 1 file changed, 86 insertions(+)
> >
> > diff --git a/sys-utils/mount.8.adoc b/sys-utils/mount.8.adoc
> > index 4571bd2bfd16..191a3fabf501 100644
> > --- a/sys-utils/mount.8.adoc
> > +++ b/sys-utils/mount.8.adoc
> > @@ -853,6 +853,7 @@ This section lists options that are specific to particular filesystems. Where po
> > |===
> > |*Filesystem(s)* |*Manual page*
> > |btrfs |*btrfs*(5)
> > +|cephfs |*mount.ceph*(8)
>
> It seems that all we need is this change.
>
> > |cifs |*mount.cifs*(8)
> > |ext2, ext3, ext4 |*ext4*(5)
> > |fuse |*fuse*(8)
> > @@ -913,6 +914,91 @@ Give blocksize. Allowed values are 512, 1024, 2048, 4096.
> > **grpquota**|**noquota**|**quota**|*usrquota*::
> > These options are accepted but ignored. (However, quota utilities may react to such strings in _/etc/fstab_.)
> >
> > +=== Mount options for ceph
>
> If mount.ceph(8) exists, we do not need to repeat the mount option in
> mount(8). The ideal solution is to keep filesystem-specific mount
> options in the filesystem-specific man page maintained by the
> filesystem developer :-) See btrfs, extN, XFS, etc.
>
My assumption was that if other file systems have description of specific mount
options in this man page, then CephFS should have too. :) But if it is not right
strategy, then you are correct here.
Let me shrink my patch then.
Thanks,
Slava.
next prev parent reply other threads:[~2026-01-13 19:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-12 20:58 [PATCH] mount: (manpage) add CephFS kernel client mount options Viacheslav Dubeyko
2026-01-13 19:14 ` Karel Zak
2026-01-13 19:29 ` Viacheslav Dubeyko [this message]
2026-01-14 9:29 ` Karel Zak
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=c15ce83bf9ee6c5c37db193c33a77b52f0594564.camel@ibm.com \
--to=slava.dubeyko@ibm.com \
--cc=Pavan.Rallabhandi@ibm.com \
--cc=amarkuze@redhat.com \
--cc=ceph-devel@vger.kernel.org \
--cc=idryomov@gmail.com \
--cc=kzak@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=pdonnell@redhat.com \
--cc=slava@dubeyko.com \
--cc=util-linux@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