On Tue, Mar 06, 2018 at 12:49:04PM -0800, Darrick J. Wong wrote: > On Tue, Mar 06, 2018 at 01:34:42PM -0600, Eric Sandeen wrote: > > Sorry - of course later patches make xfs_info work offline, but still, > > I'd like to see some rationale for why we need that capability. I'm all > > for the code reduction of the common printing routine but what's the big > > picture rational for teaching all these other tools to print mkfs-like output? > > Growing the filesystem falls under the umbrella of space management, so > in the long run (like after I finish putting online repair in) I intend > to make growfs a part of xfs_spaceman, and then the xfs_growfs command > becomes a wrapper around that. Looking forward towards Dave's subvolume > thingy, I think it makes sense to be able to manage subvolumes entirely > via spaceman commands. Agreed with this, as this is where I've implemented all the subvol management stuff. Also, when we have lots of subvoils sitting around as files, it'd bee really nice to be able to have utilities that can identify them from accessing the backing file.... Cheers, Dave. -- Dave Chinner david@xxxxxxxxxxxxx -- 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
