Dne 12.3.2018 v 12:09 Jitendra napsal(a):
On Mon, Mar 12, 2018 at 10:49:02AM +0100, Zdenek Kabelac wrote:
Dne 10.3.2018 v 11:47 Jitendra napsal(a):
Once kernel is booted and 'ramdisk' is processed - you have plenty of
time and lots of binaries there (typically with lvm2 built-in) - so
On Mon, Mar 12, 2018 at 10:49:02AM +0100, Zdenek Kabelac wrote:
Dne 10.3.2018 v 11:47 Jitendra napsal(a):
lvm2 is exactly solving this problem as it maintains consistent
'metadata' on every device - so upon reboot devices are discovered and
from their metadata dm tables are actived/restored.
Dne 10.3.2018 v 11:47 Jitendra napsal(a):
lvm2 is exactly solving this problem as it maintains consistent
'metadata' on every device - so upon reboot devices are discovered and
from their metadata dm tables are actived/restored.
Got it.
So are you looking for recreation of all the lvm2
lvm2 is exactly solving this problem as it maintains consistent
'metadata' on every device - so upon reboot devices are discovered and
from their metadata dm tables are actived/restored.
Got it.
So are you looking for recreation of all the lvm2 infrastructure for
this relatively quite
Dne 9.3.2018 v 10:58 jitendra kumar khasdev napsal(a):
Hi All,
I wrote the basic target using device mapper framework. Using dmsetup utility
I am able to create device node under /dev/mapper/my_custom_mapper.
But when I do reboot the system, it lost the mapping. Is there any way by
which I
Hi All,
I wrote the basic target using device mapper framework. Using dmsetup
utility I am able to create device node under /dev/mapper/my_custom_mapper.
But when I do reboot the system, it lost the mapping. Is there any way by
which I can create mapping during boot like LVM does.
---
Jitendra
