On Fri, Sep 25, 2015 at 9:25 AM, Bostjan Skufca <bost...@a2o.si> wrote: > > Similar here: I am sticking with 3.19.2 which has proven to work fine for me
I'd recommend still tracking SOME stable series. I'm sure there were fixes in 3.19 for btrfs (to say nothing of other subsystems) that you're missing with that version. 3.19 is also unsupported at this time. You might want to consider moving to either 3.18.21 or 4.1.8 and tracking those series instead. I doubt you'd give up much moving back to 3.18 and there have been a bunch of btrfs fixes in that series (though it seems to me that 3.18 has been slower to receive btrfs patches than some of the other series). I'm on the fence right now about making the move to 4.1. Maybe in a few releases I'll be there, depending on what the noise on the lists sounds like. There was a time when you were better off on bleeding-edge linux for btrfs. If you REALLY want to run btrfs raid5 or something like that then I'd say that is still your best strategy. However, if you stick with features that have been around for a year the longterm kernels seem a lot less likely to hit you with a regression, as long as you don't switch to a new one the day it is declared as such. -- Rich -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
