From: Peter Rajnoha <prajnoha@redhat.com>
To: Vivek Satpute <vivekonline86@gmail.com>
Cc: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] How LVM root volumes gets mounted at boot time ?
Date: Fri, 08 Aug 2014 08:34:07 +0200 [thread overview]
Message-ID: <53E46F5F.1090709@redhat.com> (raw)
In-Reply-To: <CAK4r=d4wtwm+n=JyKrd7yrCqw-EjSoZagtDEMONUTz9acg2C3g@mail.gmail.com>
On 08/07/2014 08:20 PM, Vivek Satpute wrote:
> Thanks a lot Peter for replying.
>
> I know that */sys/devices/virtual**/block/dm-0 *SysFsPath would get
> created by block-layer when corresponding block device gets created.
>
> 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
> *Following=sys-devices-virtual-block-dm\x2d0.device
> *
> [...]
> *SysFSPath=/sys/devices/virtual/block/dm-0*
> *
> *
> /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
> follows *sys-devices-virtual-block-dm\x2d0.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
next prev parent reply other threads:[~2014-08-08 6:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-25 20:50 [linux-lvm] How LVM root volumes gets mounted at boot time ? Vivek Satpute
2014-07-28 8:22 ` Peter Rajnoha
2014-08-07 18:20 ` Vivek Satpute
2014-08-08 6:34 ` Peter Rajnoha [this message]
2014-08-08 8:33 ` Vivek Satpute
2014-08-08 8:38 ` Peter Rajnoha
2014-08-14 18:19 ` Vivek Satpute
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=53E46F5F.1090709@redhat.com \
--to=prajnoha@redhat.com \
--cc=linux-lvm@redhat.com \
--cc=vivekonline86@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).