On Wednesday 15 February 2012 20:00:01 Tim Connors wrote:
It's not ready yet.
Correct, that's why it's marked as experimental in the kernel config.
I installed 3.2 (can't get terribly much more modern by installing debian kernel packages), made a several hundred gig btrfs filesystem and chucked half of several hundred gig onto it. 3 oops with btrfs traces later, I decided I'd remake the FS as ext4.
If you want to experiment with btrfs I sincerely ask you to try with the last 3.3 RC (there haven't been any btrfs changes since 3.3 RC 2 but you might as well get the rest of the fixes that have been going in since) and join the linux-btrfs list and report issues there so that they can get fixed (or, if fixed, get an idea when those are likely to get merged). There's been at least one ENOSPC fix (which, yes, can result in oops's) since 3.2 was released - "Btrfs: fix enospc error caused by wrong checks of the chunk" which was commit 9e622d6bea0202e9fe267955362c01918562c09b. cheers! Chris -- Chris Samuel : http://www.csamuel.org/ : Melbourne, VIC This email may come with a PGP signature as a file. Do not panic. For more info see: http://en.wikipedia.org/wiki/OpenPGP