From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id EF26B26B756 for ; Tue, 24 Feb 2026 19:49:05 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=10.30.226.201 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1771962546; cv=none; b=Ei/d7VHBtj5kFz1zTizstCF0XwqVQKj61VtzN1QefdKVyLkBUXx1Xp8Gty2nK4EDO8kawFGw8IYIzNLKr8QnGJemypCCt5PQOZQ5SjWAXPJkqROQgyKUhnvKkuGmRV/elYPGyvO8dyOCdsvsw1pQYvAiXgA40uLHlchXT0Tds0s= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1771962546; c=relaxed/simple; bh=n8M5ovPfpFr9S+m3QbUJtSr+02MlJwH0vSi6qXdmuV0=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=jnr7AaZMpaO9umgtPTN5pFEnxJ0pUe91KE5muhukKxj2oyX/Xnb3rJO/3Bs5wAKu34f/t6aedhCl3Mv+gnMxS9Oj8VmslIopCPUXNSq1LpFrykawIjRxeoWn9IdVH+ra43+ZM6zch0kB2BJtWpaCaQBhAFnjZ5yGeSULQpVJJWA= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=HhVWTTVu; arc=none smtp.client-ip=10.30.226.201 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="HhVWTTVu" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 62EF1C116D0; Tue, 24 Feb 2026 19:49:05 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1771962545; bh=n8M5ovPfpFr9S+m3QbUJtSr+02MlJwH0vSi6qXdmuV0=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=HhVWTTVu8IgJIPp5RkO8v2epVKcoXWmhZIYCS/xyGnJ8slEFe6fNAWfZwfTT5ZmkU REPUbsrTCU0wXZB7OKzXxIV2LvWYwYFGQPj9sHA9wqb97rrtUYQ9G/iPvP+9xGhbyN pTuu4MDIuYgiWX/uFBwb7pnrICIEumgNEJkGjadWfKVS5or5WErCWEGVWD376mgXi8 9raPn+6+lpmD0tHTEG7op5pL8aB8V2nn5Hq4uCXxw4Um/JvVGw9t53pe7+j0zMsyCn c1TU/kK2tr3EaMJdg0hTSvXwJdGeTK4xNGqPR3axP9QAz9sKF8H3GTPhApcU91pwZ9 7MN/3B76Lg6DQ== Date: Tue, 24 Feb 2026 11:49:04 -0800 From: "Darrick J. Wong" To: Christoph Hellwig Cc: =?utf-8?B?0JzQsNGA0Log0JrQvtGA0LXQvdCx0LXRgNCz?= , linux-xfs@vger.kernel.org Subject: Re: [RFE] xfs_growfs: option to clamp growth to an AG boundary Message-ID: <20260224194904.GC13843@frogsfrogsfrogs> References: Precedence: bulk X-Mailing-List: linux-xfs@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: On Tue, Feb 24, 2026 at 07:02:32AM -0800, Christoph Hellwig wrote: > On Mon, Feb 23, 2026 at 02:48:48PM +0500, Марк Коренберг wrote: > > This feels like something xfsprogs could support directly. My proposals: > > I like your proposal. This is actually a relatively east project, > and I've happy to mentor whomever wants to take it up. Although > I think json output while generally useful is probably a separate > issue and should be addressed separately and in a more general > fashion. I've long thought it might be useful to have an xfs_db command that could spit out a mkfs config file for a given filesystem, so you could just do: # xfs_db -c 'mkfs_config' /dev/sda1 > /tmp/foo.cfg # mkfs.xfs -c /tmp/foo.cfg -f /dev/sdb1 and then sdb1 gets whatever featureset sda1 had. The reason I never pursued this is that I don't know how much we'd really want to preserve. User-visible features, yes. But what about geometry things like group size, volume size, or RAID stripe parameters? --D