@kageurufu Nice. And thanks for sharing your findings on this one.
You could also custom edit our kiwi-ng installer definition, in your chosen profile, so that these updated packages get backed into a custom installer. Take care with changing output from newer kernels / btrfs as we parse this and they occasionally make syntactic / data changes. Report these if you find any however as then we can see what’s coming. We used to build for tumbleweed for this reason but our own technical debt (still Python 2) caught up with us on that front. Note also that we currently build rpms for Leap 15.3 and have installer profiles for this as well.
Linking for context to prior forum threads on issues / plans for the newer raid profiles:
and more specifically:
Big and deep changes but ultimately entirely doable. But just with care.
Note that Rockstor will enforce it’s ‘way’ and likely return raid profiles to be within it’s currently more limited knowledge. So watch out for that. Also the number of disks (minimum etc) fences / warnings will also be inaccurate / misleading so you will also be on your own on that front. I.e. btrfs raid1c3 required a minimum of 3 disks. Rockstor only knows about btrfs raid1 (c2 default), so will likely only enforce/ward about a minimum of 2 disks for a raid1c* arrangement.
As to your import. Rockstor has a necessary and by-design narrow understanding of subvolume arrangements. It looks like, from your import, that you were able to arrange your prior subvolumes to be appropriate to this. Anything outside this arrangement, which can be found by creating native Rockstor subvols (shares in Rockstor speak), will likely be either ignored or a source of confusion.
In short we don’t support the import of btrfs volumes that were not created by a prior Rockstor install. But only because of the subvol arrangement. If this is compatible there all is good. We should have a tecnical doc on exactly what this is. Oh well, much to do. Bit by bit.
Thanks again for sharing your findings on this one. Maybe a pull request in our DIY installer maker:
with the additional repos added and a script addition to edit (i.e. sed) any system files (the zypp.conf bit) to adapt the resulting system to these kernels would be good. All remarked out/disabled would be best. Then folks wishing to run these cutting edge kernels could un-remark these within the installer config and be off to the races. In case you end up playing with creating a installer addition that is. Would be good for emergency re-install type arrangements once you have this system setup.
Do keep us informed of the Web-UI shortcoming, i.e. pics with suggested missing/wrong bits here. I.e. where we currently fail to represent this for-now unsupported raid profile. These findings could then form the basis for a new feature issue in the rockstor-core repo.
Cheers. I’m looking forward to extending our raid profiles actually but again, bit by bit.