Re: free space inode generation (0) did not match free space cache generation

[Hendrik Friedel <hendrik@friedels.name>]

Hi,

> Well, given the relative immaturity of btrfs as a filesystem at this
> point in its lifetime, I think it's acceptable/tolerable.  However, for a
> filesystem feted[1] to ultimately replace the ext* series as an assumed
> Linux default, I'd definitely argue that the current situation should be
> changed such that btrfs can automatically manage its own de-allocation at
> some point, yes, and that said "some point" really needs to come before
> that point at which btrfs can be considered an appropriate replacement
> for ext2/3/4 as the assumed default Linux filesystem of the day.

Agreed! I hope, this is on the ToDo List?!

> [1] feted: celebrated, honored.  I had to look it up to be sure my
> intuition on usage was correct, and indeed I had spelled it wrong

:-)


Greetings,
Hendrik