[0/1] btrfs-progs: btrfstune: print seeding status

Message ID	20190103232239.11931-1-ddiss@suse.de (mailing list archive)
Headers	show Return-Path: <linux-btrfs-owner@kernel.org> From: David Disseldorp <ddiss@suse.de> To: linux-btrfs@vger.kernel.org Subject: [PATCH 0/1] btrfs-progs: btrfstune: print seeding status Date: Fri, 4 Jan 2019 00:22:38 +0100 Message-Id: <20190103232239.11931-1-ddiss@suse.de> Sender: linux-btrfs-owner@vger.kernel.org Precedence: bulk
Series	btrfs-progs: btrfstune: print seeding status \| expand [0/1] btrfs-progs: btrfstune: print seeding status [1/1] btrfs-progs: btrfstune: print seeding status

Message ID

20190103232239.11931-1-ddiss@suse.de (mailing list archive)

Headers

From: David Disseldorp <ddiss@suse.de>
To: linux-btrfs@vger.kernel.org
Subject: [PATCH 0/1] btrfs-progs: btrfstune: print seeding status
Date: Fri,  4 Jan 2019 00:22:38 +0100
Message-Id: <20190103232239.11931-1-ddiss@suse.de>
Sender: linux-btrfs-owner@vger.kernel.org
Precedence: bulk

Series

btrfs-progs: btrfstune: print seeding status | expand

Message

David Disseldorp Jan. 3, 2019, 11:22 p.m. UTC

AFAICT there's currently no way to easily determine whether or not
seeding is enabled for a given device. The following patch adds new
"btrfstune -s" functionality to perform this.

An xfstests test case will follow if/when the interface is deemed
acceptable.

Cheers, David