On Tue, Jun 30, 2015 at 4:14 PM, David Sterba wrote:
> On Mon, Jun 29, 2015 at 05:15:12PM +0100, Filipe Manana wrote:
>> On Mon, Jun 29, 2015 at 4:42 PM, David Sterba wrote:
>> > On Wed, Jun 17, 2015 at 12:44:55PM +0100, fdman...@kernel.org wrote:
>> > The test fails after I do this before unmoun
On Mon, Jun 29, 2015 at 05:15:12PM +0100, Filipe Manana wrote:
> On Mon, Jun 29, 2015 at 4:42 PM, David Sterba wrote:
> > On Wed, Jun 17, 2015 at 12:44:55PM +0100, fdman...@kernel.org wrote:
> > The test fails after I do this before unmount:
> >
> > $SUDO_HELPER $TOP/btrfs balance start -mconvert=
On Mon, Jun 29, 2015 at 4:42 PM, David Sterba wrote:
> On Wed, Jun 17, 2015 at 12:44:55PM +0100, fdman...@kernel.org wrote:
>> Currently there is not way for a user to know what is the minimum size a
>> device of a btrfs filesystem can be resized to. Sometimes the value of
>> total allocated space
On Wed, Jun 17, 2015 at 12:44:55PM +0100, fdman...@kernel.org wrote:
> Currently there is not way for a user to know what is the minimum size a
> device of a btrfs filesystem can be resized to. Sometimes the value of
> total allocated space (sum of all allocated chunks/device extents), which
> can
From: Filipe Manana
Currently there is not way for a user to know what is the minimum size a
device of a btrfs filesystem can be resized to. Sometimes the value of
total allocated space (sum of all allocated chunks/device extents), which
can be parsed from 'btrfs filesystem show' and 'btrfs files
