Thanks a much Peter. This really helped a lot :-)
Regards
On Fri, Aug 8, 2014 at 12:04 PM, Peter Rajnoha <prajnoha@redhat.com> wrote:
On 08/07/2014 08:20 PM, Vivek Satpute wrote:> I know that */sys/devices/virtual**/block/dm-0 *SysFsPath would get
> Thanks a lot Peter for replying.
>
> created by block-layer when corresponding block device gets created.> *Following=sys-devices-virtual-block-dm\x2d0.device
>
> Actually I am looking for how below dependencies is getting created for
> LVM volume by systemd:
>
> [root@host]# systemctl show dev-rhel_host-root.device
> Id=dev-rhel_host-root.device
> Names=dev-rhel_host-root.device
> *
> [...]
> *SysFSPath=/sys/devices/virtual/block/dm-0*
> *
> *> follows *sys-devices-virtual-block-dm\x2d0.device ?*
> /dev/rhel_host/root (path of LVM volume) is actually a symbolic link
> pointing to /dev/dm-0, then how systemd recognize that
> device dev-rhel_host-root.device
> *
Systemd can read this information from udev events (or udev database records).
The information about all existing symlinks and their names, the dev node name
("kernel name") and related sysfs link is all recorded in udev database so systemd
just makes the .device unit out of this information.
--
Peter
_______________________________________________ linux-lvm mailing list linux-lvm@redhat.com https://www.redhat.com/mailman/listinfo/linux-lvm read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/