On Wed, 15 Feb 2012, Avi Miller wrote:
On 15/02/2012, at 8:00 PM, Tim Connors wrote:
It's not ready yet. 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.
There have been a lot of stability fixes in 3.3 and 3.4. Are you reporting these oops' anywhere? Obviously this is very important to me, as Release Manager for Oracle Linux's UEK2 and btrfs. :) Our internal QA testing is seriously hammering btrfs at the moment, so I'd be interested to know if you can reproduce these issues. If you can, please email me directly with the steps to reproduce so that I can try and get Oracle QA to try it as well.
mv ~/ext3/ ~/btrfs/ :) (or I might have been reading files off them at the time. Or it might have been sitting idle. I can't actually remember!) Nothing particularly onerous. Certainly not making or using snapshots or doing anything other than accessing and using it as a simple filesystem. Only thing I can think of that was slightly non-mainstream was that it was over iscsi. Naturally, there's only so many times you can try that for your home directory. I don't have any large quantities of data I don't care about (otherwise I would have allocated a larger /dev/write-once-read-never device)! That's why I like stable filesystems and never will be the target market for experimental New Shiny filesystems. It's remarkable how well tested ext3 is. I let the other people be the guinea pigs. -- Tim Connors