On 2016/09/22 17:26, Omar Sandoval wrote:
> As far as I know, space_cache=v2 isn't documented in the man page, so
> hopefully anyone who managed to find out about it follows the mailing
> list. If someone updates their kernel without updating btrfs-progs, the
> new compat_ro bit will prevent the o
On Thu, Sep 22, 2016 at 05:47:59PM +, ojab wrote:
> On 2016/09/22 17:26, Omar Sandoval wrote:
> > As far as I know, space_cache=v2 isn't documented in the man page, so
> > hopefully anyone who managed to find out about it follows the mailing
> > list. If someone updates their kernel without upd
On Thu, Sep 22, 2016 at 12:10:09PM +0200, Hans van Kranenburg wrote:
> Hi,
>
> On 09/22/2016 10:52 AM, David Sterba wrote:
> > On Wed, Sep 21, 2016 at 01:31:52PM -0700, Omar Sandoval wrote:
> I'm not sure I understand - can you explain why this is was so wrong?
> Or Omar maybe?
>
>
On Thu, Sep 22, 2016 at 10:52:05AM +0200, David Sterba wrote:
> On Wed, Sep 21, 2016 at 01:31:52PM -0700, Omar Sandoval wrote:
> > > > I'm not sure I understand - can you explain why this is was so wrong?
> > > > Or Omar maybe?
> > > >
> > > > If btrfsck wants to correct something (write), it can
Hi,
On 09/22/2016 10:52 AM, David Sterba wrote:
> On Wed, Sep 21, 2016 at 01:31:52PM -0700, Omar Sandoval wrote:
I'm not sure I understand - can you explain why this is was so wrong?
Or Omar maybe?
If btrfsck wants to correct something (write), it can simply always
and unc
On Wed, Sep 21, 2016 at 01:31:52PM -0700, Omar Sandoval wrote:
> > > I'm not sure I understand - can you explain why this is was so wrong?
> > > Or Omar maybe?
> > >
> > > If btrfsck wants to correct something (write), it can simply always
> > > and unconditionally invalidate the fst instead of tr
Hey, guys,
On Wed, Sep 21, 2016 at 08:12:51AM -0400, Austin S. Hemmelgarn wrote:
> On 2016-09-21 06:25, Holger Hoffstätte wrote:
> > On 09/21/16 11:24, David Sterba wrote:
> > > Hi,
> > >
> > > as you might have noticed, the [1] wiki Status page lists the
> > > free-space-tree as 'Unstable', refe
On 2016-09-21 06:25, Holger Hoffstätte wrote:
On 09/21/16 11:24, David Sterba wrote:
Hi,
as you might have noticed, the [1] wiki Status page lists the
free-space-tree as 'Unstable', referencing a problem with the bitmap
endianity. This will affect only bigendian systems.
There's one more probl
On 09/21/16 11:24, David Sterba wrote:
> Hi,
>
> as you might have noticed, the [1] wiki Status page lists the
> free-space-tree as 'Unstable', referencing a problem with the bitmap
> endianity. This will affect only bigendian systems.
>
> There's one more problem that I overlooked but was pointe
