Chris Murphy posted on Thu, 19 Oct 2017 21:04:26 +0100 as excerpted: > On Thu, Oct 19, 2017 at 6:43 PM, Lentes, Bernd > <bernd.len...@helmholtz-muenchen.de> wrote: >> Hi, >> >> this is the continuation of a thread i started on a SLES forum >> (https://forums.suse.com/showthread.php?10109-lv-with-btrfs-corrupt- some-tips-please), >> but i think this is the more appropriate place. > > Maybe, but as this is SLES, you're effectively paying for support, and > it's actually better to open a support instance, in my opinion.
This is what I'd recommend as well. That 3.0.x kernel is well out of the range this list tends to support, given that it's a forward-focused development list, not a stability- focused enterprise release support list. We generally go back a couple release series each in the mainline current and LTS release series, which means 4.13 and 4.12 on current, and 4.9 and 4.4 on LTS, but even 4.4 is getting pretty long in the tooth for this list, so it's fortunate that the coming 4.14 is going to be an LTS as well. While your knoppix had kernel 4.12.x which is list-reasonable for runtime, where the kernel code is primary, once something's going wrong and you can't mount, it's the userspace code that is responsible for check/rescue/ restore, and there your knoppix was a bit behind at 4.7.x. So your choices are to go really current and build a 4.13.x btrfs-progs to try, or to go with the SLES support you're paying for anyway, in which case you run what they say they'll support. Given that you were running that old code (plus backports we don't track as we're focused on mainline and forward development) already, and a 3.0 kernel really is scary- ancient in btrfs terms, they really are best positioned to support it, and given that you're presumably paying good money for that support already, you might as well use what you're paying for. -- Duncan - List replies preferred. No HTML msgs. "Every nonfree program has a lord, a master -- and if you use the program, he is your master." Richard Stallman -- 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
