From: Dave Chinner <david@fromorbit.com>
To: Catherine Hoang <catherine.hoang@oracle.com>
Cc: linux-xfs@vger.kernel.org
Subject: Re: [PATCH v1] xfs_spaceman: add fsuuid command
Date: Sat, 12 Nov 2022 08:05:32 +1100 [thread overview]
Message-ID: <20221111210532.GP3600936@dread.disaster.area> (raw)
In-Reply-To: <20221109222335.84920-1-catherine.hoang@oracle.com>
On Wed, Nov 09, 2022 at 02:23:35PM -0800, Catherine Hoang wrote:
> Add support for the fsuuid command to retrieve the UUID of a mounted
> filesystem.
>
> Signed-off-by: Catherine Hoang <catherine.hoang@oracle.com>
Not looking at the code, just the high level CLI interface issues.
That is, xfs_admin already has user interfaces to get/set the
filesystem UUID on XFS filesystems. Further, xfs_spaceman is for XFS
filesystem SPACE MANagement, not filesystem identification
operations.
xfs_admin is CLI interface that aggregates various admin utilities
such as identification (UUID and label) management. If we need to
implement a generic VFS ioctl for online UUID retreival, xfs_io is
generally the place to put it because then it can be used by fstests
to run on other filesytems.
We can then wrap xfs_admin around the xfs_io command as needed. i.e.
use 'xfs_io -c fsuuid /mnt/pt' if the filesystem is mounted, 'xfs_db
-c uuid /path/to/device' if the filesystem is not mounted, and we
can make sure that both the xfs_db and xfs_io commands have the same
output....
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
next prev parent reply other threads:[~2022-11-11 21:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-09 22:23 [PATCH v1] xfs_spaceman: add fsuuid command Catherine Hoang
2022-11-11 21:05 ` Dave Chinner [this message]
2022-11-14 22:55 ` Catherine Hoang
2022-11-11 21:31 ` Allison Henderson
2022-11-17 20:37 ` Darrick J. Wong
2022-11-17 21:51 ` Dave Chinner
2022-11-17 23:58 ` Darrick J. Wong
2022-11-21 23:33 ` Dave Chinner
2022-11-22 6:21 ` Darrick J. Wong
2022-11-22 23:45 ` Dave Chinner
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=20221111210532.GP3600936@dread.disaster.area \
--to=david@fromorbit.com \
--cc=catherine.hoang@oracle.com \
--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