Le jeudi 04 juillet 2013 à 11:54 -0400, Jeff Mahoney a écrit :
Hi all -
Over the past year, btrfs has received substantial attention in the areas of both stability and performance. I've been running it, personally, on a 4 TB data volume as well as my root partitions for my openSUSE 12.2/12.3 systems. I've been able to do stress tests like a long fsmark run simultaneously with creating and removing snapshots (with syncs to force them to disk) and haven't run into any issues. David Sterba, who's been leading the charge at SUSE for btrfs stability has likewise regularly run it through an array of torture tests and has found that problems are occurring a whole lot less frequently than they have in the past. The upstream btrfs community in which we participate has also started focusing less on feature development and more on stability and performance.
But these are only anecdotal data points from two file system guys and if my experiences working for a major operating systems vendor have taught me anything, it's that our users can be a lot more creative at finding ways to break things than we are. ;)
So, I'd like to hear your stories. What's worked for you? What hasn't worked? What would you consider the pain points with using btrfs?
Lastly, I'd like to ask that you take the opportunity to test with the latest openSUSE Factory kernel running 3.10-final. 12.3 used the 3.7 kernel since it was the most recent release going into the beta cycle and we've seen a bunch of btrfs fixes since that release.
I look forward to your feedback and the opportunity to improve btrfs for the 13.1 release and future releases.
Some feedback on my btrfs usage : - as I mentioned in another reply, running KVM hosting VM on btrfs is consuming a lot of IO cycle and we should probably disable CoW for such images, by default (I already opened a FATE for that) - I have btrfs running on my main laptop, using two separate partitions : * / is using btrfs since last February (first 12.2, then 12.3 and then Factory since this week). It has been working nicely, except a big crash (on 12.3 caused by Nouveau) which stopped my system to boot at all (btrfs couldn't replay its log). I had to zero btrfs log to be able to recover my system (of course, it was just as I was starting a talk in front of an audience, so I didn't had time to test mount with recovery and nor to take a copy of the FS). We need to improve btrfs reliance in this sort of event (maybe automatically mount with recover when mounting / doesn't work, etc..) * /home over LUKS, since several weeks. No issue found so far. - I'm also using btrfs for / (not /home) at my home, no issue found. - I agree with Matthias on our default snapper configuration which can easily fill a system without user knowledge and causing strange error like: file system full, removing file refused with "no space on device" because snapshot should be removed, not files. Other than that, I'm quite happy with btrfs. -- Frederic Crozat <fcrozat@suse.com> SUSE -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org