From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: hal@deer-run.com
Cc: Eric Sandeen <sandeen@sandeen.net>, linux-xfs@vger.kernel.org
Subject: Re: [PATCH] xfs_db: add -R option
Date: Tue, 8 May 2018 09:58:19 -0700 [thread overview]
Message-ID: <20180508165819.GN11261@magnolia> (raw)
In-Reply-To: <20180508164340.GB18224@deer-run.com>
On Tue, May 08, 2018 at 11:43:40AM -0500, hal@deer-run.com wrote:
> > Well, I don't really like either patch for the reasons stated above.
> > xfs_db /can/ write to the filesystem, and -r disables that... but -r
> > as a modifier to affect the behavior of a read-only command is
> > unintuitive.
> >
> > "It is only necessary to omit this flag if a command that changes data
> > (write, blocktrash, crc) is to be used."
> >
> > What are the objections to a blockget modifier option? That seemed like
> > the most direct & obvious solution to me.
> >
> > "blockget/check -L : attempt to perform the blockget and check functions
> > even if the log contains unreplayed metadata," or something like that?
That also seems fine to me. :)
> Ah, OK. I'm getting what you're saying now. Let me poke around with
> the code some and produce a patch that does what you're suggesting.
<nod>
--D
> --Hal
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-xfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2018-05-08 16:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-04 14:02 [PATCH] xfs_db: add -R option hal
2018-05-04 15:32 ` Darrick J. Wong
2018-05-07 11:35 ` hal
2018-05-07 12:56 ` hal
2018-05-08 1:21 ` Darrick J. Wong
2018-05-08 13:55 ` Eric Sandeen
2018-05-08 16:13 ` hal
2018-05-08 16:27 ` Eric Sandeen
2018-05-08 16:43 ` hal
2018-05-08 16:58 ` Darrick J. Wong [this message]
2018-05-09 0:14 ` 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=20180508165819.GN11261@magnolia \
--to=darrick.wong@oracle.com \
--cc=hal@deer-run.com \
--cc=linux-xfs@vger.kernel.org \
--cc=sandeen@sandeen.net \
/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;
as well as URLs for NNTP newsgroup(s).