Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 23 May 2024 10:46:38 +0000
From:      bugzilla-noreply@freebsd.org
To:        bugs@FreeBSD.org
Subject:   [Bug 279249] quotactl(2) out of date w.r.t. ZFS, and missing information
Message-ID:  <bug-279249-227@https.bugs.freebsd.org/bugzilla/>

next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D279249

            Bug ID: 279249
           Summary: quotactl(2) out of date w.r.t. ZFS, and missing
                    information
           Product: Documentation
           Version: Latest
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Many People
          Priority: ---
         Component: Manual Pages
          Assignee: bugs@FreeBSD.org
          Reporter: gray@nxg.name
                CC: doc@FreeBSD.org

The quotactl(2) manpage states bluntly that =E2=80=98Currently quotas are s=
upported
only for the "ufs" file system.=E2=80=99 But (a) bug #234413 from 2019/12.0=
, states
that =E2=80=98ZFS implements quotactl(2) as of r336017; the man page needs =
to be
updated.=E2=80=99 Also (b) quotactl does seem to work when called on a ZFS =
filesystem.

Though it seems to work, does this work only by accident? (ie, is it going =
to
stop working unexpectedly?).  It would be good for the manpage to be explic=
it
about this.

Separately, the manpage doesn't give, or point to, relevant information on =
how
to interpret the results of the call.  I can call quotactl(2) on a ZFS
filesystem and it produces numbers, which quota.h tells me are in units of =
disk
blocks, and which are right if the block-size is 512B.  But I can find noth=
ing,
neither in quotactl() nor in ufs/ufs/quota.h, which tells me that
unequivocally, and in a way which I'm confident will work on a pool with a
different ashift value.

--=20
You are receiving this mail because:
You are the assignee for the bug.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-279249-227>