Re: [PATCH] btrfs: Fix no space bug caused by removing bg

[Hugo Mills <hugo@carfax.org.uk>]

[-- Attachment #1: Type: text/plain, Size: 1302 bytes --]

On Wed, Sep 23, 2015 at 03:12:26PM +0200, David Sterba wrote:
> On Tue, Sep 22, 2015 at 02:36:02PM +0000, Hugo Mills wrote:
> > > Yeah, right now there's no persistent default for the allocator. I'm
> > > still hoping that the object properties will magically solve that.
> > 
> >    There's no obvious place that filesystem-wide properties can be
> > stored, though. There's a userspace tool to manipulate the few current
> > FS-wide properties, but that's all special-cased to use the
> > "historical" ioctls for those properties, with no generalisation of a
> > property store, or even (IIRC) any external API for them.
> 
> From the UI point, we proposed to add a specifier that would route the
> property to either subvolume or the filesystem:
> 
> $ btrfs prop set -t filesystem bgtype raid0
> $ btrfs prop set -t subvolume bgtype raid1
> 
> How this will get stored in the xattrs is another question. As there's
> always only single instance of the filesystem properties, it coud be
> something like 'btrfs.fs.bgtype' and be stored as a xattr of the
> toplevel subvolume.

   That's what Austin suggested as well. Makes sense to me.

   Hugo.

-- 
Hugo Mills             | 2 + 2 = 5, for sufficiently large values of 2.
hugo@... carfax.org.uk |
http://carfax.org.uk/  |
PGP: E2AB1DE4          |

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]