В Mon, 27 Jul 2015 08:15:45 +0300 Oleksii Shevchuk <alx...@gmail.com> пишет:
> Andrei Borzenkov <arvidj...@gmail.com> writes: > > > So that it the problem. Does it happen if you use cryptsetup directly? > > Yes, with cryptsetup behavior is the same. > > I have cryptsetup (1.6.7) and lvm2 (2.02.116). > > Btw, does your system behave differently? > Yes. bor@opensuse:~> sudo cryptsetup open --type plain /dev/mapper/system-docker --key-file /dev/urandom test bor@opensuse:~> LC_ALL=C ll /dev/mapper/ total 0 crw------- 1 root root 10, 236 Jun 28 11:05 control lrwxrwxrwx 1 root root 7 Jun 29 20:24 loop0p2 -> ../dm-5 lrwxrwxrwx 1 root root 7 Jun 28 11:05 system-datastore -> ../dm-3 lrwxrwxrwx 1 root root 7 Jul 27 12:18 system-docker -> ../dm-4 lrwxrwxrwx 1 root root 7 Jun 28 11:05 system-home -> ../dm-2 lrwxrwxrwx 1 root root 7 Jun 28 11:05 system-root -> ../dm-1 lrwxrwxrwx 1 root root 7 Jun 28 11:05 system-swap -> ../dm-0 lrwxrwxrwx 1 root root 7 Jul 27 12:18 test -> ../dm-6 bor@opensuse:~> rpm -q cryptsetup device-mapper cryptsetup-1.6.6-1.1.x86_64 device-mapper-1.02.78-20.2.2.x86_64 bor@opensuse:~> You should ask on cryptsetup/device-mapper list why it behaves differently in your case. _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
