Comment # 3 on bug 954650 from Stakanov Schufter

I tried now out several scenarios. 
a) normal install without LVM. Success but one erroneous behavior of the
installer. 
Leap does install, as set in the process, "use the whole disc /sdc" in
sdc1,sdc2,sdc3 , but is using as well sdb1 without asking(!) as place for btrfs
snapshots. More curiously, it does neither indicate nor ask to do that, that
is, I had no way to see this during install. However, for the rest leap
installs and is stable in this context, coexisting w/o problems with Tumbleweed
on the same machine (on sda with encrypted lvm). 

b) using the encrypted LVM install approach: this gives the very same error as
the install with EXT4: error 4013 with exactly the same error message. 

I haven't yet tried the pure LVM version. If you deem it useful I will do so. I
can also provide for any of these situations the respective yast2log (again if
you deem it of useful). 

That said: even in situation as of a) the installer should not "just like that"
and without even showing it in the resume of install, attribute an existing
sdb1/XFS partition (even if, as in this case, empty), to write on it btrfs
snapshots. So I see also problems in this config with the very normal
installer.