On Sun, Sep 11, 2016 at 02:39:14PM +0200, Waxhead wrote: > Martin Steigerwald wrote: > >Am Sonntag, 11. September 2016, 13:43:59 CEST schrieb Martin Steigerwald: > >>>>Thing is: This just seems to be when has a feature been implemented > >>>>matrix. > >>>>Not when it is considered to be stable. I think this could be done with > >>>>colors or so. Like red for not supported, yellow for implemented and > >>>>green for production ready. > >>>Exactly, just like the Nouveau matrix. It clearly shows what you can > >>>expect from it. > >I mentioned this matrix as a good *starting* point. And I think it would be > >easy to extent it: > > > >Just add another column called "Production ready". Then research / ask about > >production stability of each feature. The only challenge is: Who is > >authoritative on that? I´d certainly ask the developer of a feature, but I´d > >also consider user reports to some extent. > > > >Maybe thats the real challenge. > > > >If you wish, I´d go through each feature there and give my own estimation. > >But > >I think there are others who are deeper into this. > That is exactly the same reason I don't edit the wiki myself. I > could of course get it started and hopefully someone will correct > what I write, but I feel that if I start this off I don't have deep > enough knowledge to do a proper start. Perhaps I will change my mind > about this.
Given that nobody else has done it yet, what are the odds that someone else will step up to do it now? I would say that you should at least try. Yes, you don't have as much knowledge as some others, but if you keep working at it, you'll gain that knowledge. Yes, you'll probably get it wrong to start with, but you probably won't get it *very* wrong. You'll probably get it horribly wrong at some point, but even the more knowledgable people you're deferring to didn't identify the problems with parity RAID until Zygo and Austin and Chris (and others) put in the work to pin down the exact issues. So I'd strongly encourage you to set up and maintain the stability matrix yourself -- you have the motivation at least, and the knowledge will come with time and effort. Just keep reading the mailing list and IRC and bugzilla, and try to identify where you see lots of repeated problems, and where bugfixes in those areas happen. So, go for it. You have a lot to offer the community. Hugo. > >I do think for example that scrubbing and auto raid repair are stable, except > >for RAID 5/6. Also device statistics and RAID 0 and 1 I consider to be > >stable. > >I think RAID 10 is also stable, but as I do not run it, I don´t know. For me > >also skinny-metadata is stable. For me so far even compress=lzo seems to be > >stable, but well for others it may not. > > > >Since what kernel version? Now, there you go. I have no idea. All I know I > >started BTRFS with Kernel 2.6.38 or 2.6.39 on my laptop, but not as RAID 1 at > >that time. > > > >See, the implementation time of a feature is much easier to assess. Maybe > >thats part of the reason why there is not stability matrix: Maybe no one > >*exactly* knows *for sure*. How could you? So I would even put a footnote on > >that "production ready" row explaining "Considered to be stable by developer > >and user oppinions". > > > >Of course additionally it would be good to read about experiences of > >corporate > >usage of BTRFS. I know at least Fujitsu, SUSE, Facebook, Oracle are using it. > >But I don´t know in what configurations and with what experiences. One Oracle > >developer invests a lot of time to bring BTRFS like features to XFS and > >RedHat > >still favors XFS over BTRFS, even SLES defaults to XFS for /home and other > >non > >/-filesystems. That also tells a story. > > > >Some ideas you can get from SUSE releasenotes. Even if you do not want to use > >it, it tells something and I bet is one of the better sources of information > >regarding your question you can get at this time. Cause I believe SUSE > >developers invested some time to assess the stability of features. Cause they > >would carefully assess what they can support in enterprise environments. > >There > >is also someone from Fujitsu who shared experiences in a talk, I can search > >the URL to the slides again. > By all means, SUSE's wiki is very valuable. I just said that I > *prefer* to have that stuff on the BTRFS wiki and feel that is the > right place for it. > > > >I bet Chris Mason and other BTRFS developers at Facebook have some idea on > >what they use within Facebook as well. To what extent they are allowed to > >talk > >about it… I don´t know. My personal impression is that as soon as Chris went > >to Facebook he became quite quiet. Maybe just due to being busy. Maybe due to > >Facebook being concerned much more about the privacy of itself than of its > >users. > > > >Thanks, > -- Hugo Mills | How do you become King? You stand in the marketplace hugo@... carfax.org.uk | and announce you're going to tax everyone. If you http://carfax.org.uk/ | get out alive, you're King. PGP: E2AB1DE4 | Harry Harrison
signature.asc
Description: Digital signature
