On Thu, Apr 20, 2017 at 8:04 AM, L A Walsh <suse@tlinx.org> wrote:
Andrei Borzenkov wrote:
19.04.2017 04:38, L A Walsh пишет: Why do you expect them to autoload?
Most needed modules autoload as I use them on my sysV system that boots from the hard disk.
I almost hit DEL ... yet again you start blaming systemd for every dead kitten. To make myself clear - your question sounded like you *know* that there is mechanism to autoload DM modules and this mechanism stopped working. I myself am not aware of this from kernel side, so I do not see why you expect *autoload*. That something loaded it in the past for you (or that you probably used your own monolithic kernel that did not need modules) does not mean it was *autoloaded*. ...
You use thin provisioning pool which is not supported by YaST
---- Not supported? Sure looked supported to me. It knew that a thin provisioned lv needed a pool, and when I was trying to figure the problem by deleting the extended volume -- it warned me that the pool was needed for the thin volume to function.
Yeah, I must have been confused or did not look there carefully for a long time. Sorry. Indeed, YaST offers thin pool - which makes this issue topic of bug report. I am not sure what component though - it is not exactly kernel bug as far as I can tell (it could be considered missing feature) so options are to either load modules from DM library or statically configure them for loading by YaST when thin pool is created. Given that currently even simple "lvcreate -T" fails, I'd vote for the former. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org