On Tue, May 08, 2018 at 11:43:40AM -0500, hal@xxxxxxxxxxxx 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@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html -- To unsubscribe from this list: send the line "unsubscribe linux-xfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
