On Tue, 03 May 2011 11:41:28 -0500, Hugo Vanwoerkom wrote:

> I have installed lvm2 and created pv's, vg's and lv's. E.g.:

(...)

> and blkid says:
>
> ...
> /dev/mapper/vgHDB-HDB3: LABEL="HD502HJ.03"
> UUID="b12819b7-8f07-4bf6-af66-9bb9410536a1" TYPE="ext2"

(...)

> I have a question: who creates exactly those /dev/ entries?

I'd say "udev".

> The reason I ask is that sometimes with mondorescue they are not created
> and I cnnot access the lv's.

I dunno how does mondo works. Is it a program to be run on live
installations or needs to be loaded from a livecd or...? :-?

Greetings,

--
Camaleón


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: pan.2011.05.03.17.53.39@gmail.com">http://lists.debian.org/pan.2011.05.03.17.53.39@gmail.com

On Tue, May 3, 2011 at 12:41 PM, Hugo Vanwoerkom <hvw59601@care2.com> wrote:
>
> I have installed lvm2 and created pv's, vg's and lv's. E.g.:
>
> root@Debian:/home/hugo# lvdisplay
> *--- Logical volume ---
> *LV Name * * * * * * * */dev/vgHDB/HDB3
> *VG Name * * * * * * * *vgHDB
> *LV UUID * * * * * * * *SCHlBs-acvc-FLzz-TgwV-0IGX-aXBM-AdbPsB
> *LV Write Access * * * *read/write
> *LV Status * * * * * * *available
> *# open * * * * * * * * 0
> *LV Size * * * * * * * *12.00 GiB
> *Current LE * * * * * * 3072
> *Segments * * * * * * * 1
> *Allocation * * * * * * inherit
> *Read ahead sectors * * auto
> *- currently set to * * 256
> *Block device * * * * * 254:1
>
> ...
>
> and blkid says:
>
> ...
> /dev/mapper/vgHDB-HDB3: LABEL="HD502HJ.03"
> UUID="b12819b7-8f07-4bf6-af66-9bb9410536a1" TYPE="ext2"
> /dev/mapper/vgHDB-HDB7: LABEL="HD502HJ.07"
> UUID="c889aa6c-e0c3-4954-b8fe-b87d257c1cc6" TYPE="ext2"
> /dev/mapper/vgHDB-HDB5: LABEL="HD502HJ.05"
> UUID="18027b86-2b1f-4e24-ab5a-eb56ba0509c9" TYPE="ext2"
> /dev/mapper/vgHDB-HDB6: LABEL="HD502HJ.06"
> UUID="238dd5dc-012f-46e1-b680-84dbe9287d2b" TYPE="ext2"
> /dev/mapper/vgHDB-HDBB: LABEL="HD502HJ.0B"
> UUID="d7bc3d22-238a-47d4-86c8-6aa3384404e5" TYPE="ext2"
> ...
>
> I have a question: who creates exactly those /dev/ entries?
>
> The reason I ask is that sometimes with mondorescue they are not created and
> I cnnot access the lv's.

I think that it's dmsetup - or a combination of dmsetup and udev.


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: BANLkTinO6zy7FHV1+6cWedc7Rbjb=h7i0A@mail.gmail.com ">http://lists.debian.org/BANLkTinO6zy7FHV1+6cWedc7Rbjb=h7i0A@mail.gmail.com

Camaleón wrote:

On Tue, 03 May 2011 11:41:28 -0500, Hugo Vanwoerkom wrote:


I have installed lvm2 and created pv's, vg's and lv's. E.g.:


(...)


and blkid says:

...
/dev/mapper/vgHDB-HDB3: LABEL="HD502HJ.03"
UUID="b12819b7-8f07-4bf6-af66-9bb9410536a1" TYPE="ext2"


(...)


I have a question: who creates exactly those /dev/ entries?


I'd say "udev".


The reason I ask is that sometimes with mondorescue they are not created
and I cnnot access the lv's.


I dunno how does mondo works. Is it a program to be run on live
installations or needs to be loaded from a livecd or...? :-?




Mondoarchive creates a bootable media and that is booted to restore the
data archived. But saying 'udev' is very general...


Hugo


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

Archive: ipphp2$k22$1@dough.gmane.org">http://lists.debian.org/ipphp2$k22$1@dough.gmane.org

Tom H wrote:

On Tue, May 3, 2011 at 12:41 PM, Hugo Vanwoerkom <hvw59601@care2.com> wrote:

I have installed lvm2 and created pv's, vg's and lv's. E.g.:

root@Debian:/home/hugo# lvdisplay
--- Logical volume ---
LV Name /dev/vgHDB/HDB3
VG Name vgHDB
LV UUID SCHlBs-acvc-FLzz-TgwV-0IGX-aXBM-AdbPsB
LV Write Access read/write
LV Status available
# open 0
LV Size 12.00 GiB
Current LE 3072
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 254:1

...

and blkid says:

...
/dev/mapper/vgHDB-HDB3: LABEL="HD502HJ.03"
UUID="b12819b7-8f07-4bf6-af66-9bb9410536a1" TYPE="ext2"
/dev/mapper/vgHDB-HDB7: LABEL="HD502HJ.07"
UUID="c889aa6c-e0c3-4954-b8fe-b87d257c1cc6" TYPE="ext2"
/dev/mapper/vgHDB-HDB5: LABEL="HD502HJ.05"
UUID="18027b86-2b1f-4e24-ab5a-eb56ba0509c9" TYPE="ext2"
/dev/mapper/vgHDB-HDB6: LABEL="HD502HJ.06"
UUID="238dd5dc-012f-46e1-b680-84dbe9287d2b" TYPE="ext2"
/dev/mapper/vgHDB-HDBB: LABEL="HD502HJ.0B"
UUID="d7bc3d22-238a-47d4-86c8-6aa3384404e5" TYPE="ext2"
...

I have a question: who creates exactly those /dev/ entries?

The reason I ask is that sometimes with mondorescue they are not created and
I cnnot access the lv's.


I think that it's dmsetup - or a combination of dmsetup and udev.




Sure enough, from 'man dmsetup':

...
create
device_name [-u uuid] [--notable | --table <table> | table_file]

Creates a device with the given name. If table_file or <table> is
supplied, the table is loaded and made live. Otherwise a table is read
from standard input unless --notable is used. The optional uuid can be
used in place of device_name in subsequent dmsetup commands. If
successful a device will appear as /dev/device-mapper/<device-name>. See
below for information on the table format.

...
























--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

Archive: ippjdq$v8e$1@dough.gmane.org">http://lists.debian.org/ippjdq$v8e$1@dough.gmane.org

On Tue, 03 May 2011 13:33:06 -0500, Hugo Vanwoerkom wrote:

> Camaleón wrote:

>>> I have a question: who creates exactly those /dev/ entries?
>>
>> I'd say "udev".
>>
>>> The reason I ask is that sometimes with mondorescue they are not
>>> created and I cnnot access the lv's.
>>
>> I dunno how does mondo works. Is it a program to be run on live
>> installations or needs to be loaded from a livecd or...? :-?
>>
>>
> Mondoarchive creates a bootable media and that is booted to restore the
> data archived. But saying 'udev' is very general...

Ah, that could explain why mondo fails the detection. "udev" create
devices on the fly -at booting- so mondo may use another nomenclature or
method to create them :-?

Greetings,

--
Camaleón


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: pan.2011.05.03.19.05.26@gmail.com">http://lists.debian.org/pan.2011.05.03.19.05.26@gmail.com

Camaleón wrote:

On Tue, 03 May 2011 13:33:06 -0500, Hugo Vanwoerkom wrote:


Camaleón wrote:



I have a question: who creates exactly those /dev/ entries?

I'd say "udev".


The reason I ask is that sometimes with mondorescue they are not
created and I cnnot access the lv's.

I dunno how does mondo works. Is it a program to be run on live
installations or needs to be loaded from a livecd or...? :-?



Mondoarchive creates a bootable media and that is booted to restore the
data archived. But saying 'udev' is very general...


Ah, that could explain why mondo fails the detection. "udev" create
devices on the fly -at booting- so mondo may use another nomenclature or
method to create them :-?




Well, the actual situation is very interesting:

1. I can create the mondorescue bootable DVD from an lv and that, when
booted, correctly creates the 'dev/mapper' entries under Squeeze.


2. But I cannot do that under Sid, the 'dev/mapper' enries are not
created consistently...


3. Meaning, when I do a Debian install of Squeeze, upgrade that to Sid
and start installing the complete system, initially mondorescue DVD's
generate the 'dev/mapper' entries, but after a while they do not.


4. Until I have a mondorescue DVD that generates the 'dev/mapper' enries
correctly and restore that to an lv. Then boot that lv and immediately
run mondoarchive to generate another rescue DVD, and that DVD does *not*
generate the 'dev/mapper' entries...


Prompting me to find out how those things are created...

Hugo






--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

Archive: ippl95$b45$1@dough.gmane.org">http://lists.debian.org/ippl95$b45$1@dough.gmane.org

Hugo Vanwoerkom <hvw59601@care2.com> schrieb:
> Hi,
>
> I have installed lvm2 and created pv's, vg's and lv's. E.g.:

(...)

> I have a question: who creates exactly those /dev/ entries?
>
> The reason I ask is that sometimes with mondorescue they are not created
> and I cnnot access the lv's.
>

I don't know mondorescue. To access lv from my rescue system (grml) I
use the following commands:
/sbin/vgscan
/sbin/vgchange -ay

This creates the /dev/mapper/ entries - and is what is done in debian's
lvm2 init script.

Martin



--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: ippvl3$949$1@dough.gmane.org">http://lists.debian.org/ippvl3$949$1@dough.gmane.org

Martin wrote:

Hugo Vanwoerkom <hvw59601@care2.com> schrieb:

Hi,

I have installed lvm2 and created pv's, vg's and lv's. E.g.:


(...)


I have a question: who creates exactly those /dev/ entries?

The reason I ask is that sometimes with mondorescue they are not created
and I cnnot access the lv's.




I don't know mondorescue. To access lv from my rescue system (grml) I
use the following commands:
/sbin/vgscan
/sbin/vgchange -ay

This creates the /dev/mapper/ entries - and is what is done in debian's
lvm2 init script.



That's exactly what the mondorescue init script does but in some cases
this does not create the /dev/mapper/ entries. I'd sure like to know
why. I have a hunch that it is not able to create the lockfile.


Hugo


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

Archive: iprqbe$sn6$1@dough.gmane.org">http://lists.debian.org/iprqbe$sn6$1@dough.gmane.org