From: Patrick Boutilier <boutilpj@ednet.ns.ca>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] Weird UUIDs
Date: Tue, 17 Jul 2001 10:21:33 -0300 [thread overview]
Message-ID: <3B543BDD.5040008@ednet.ns.ca> (raw)
In-Reply-To: 20010717145454.A17967@sistina.com
Heinz,
I created and them removed a small LV and now the UUIDs look more
familiar. :-) Thanks.
pvdata /dev/sda7
--- Physical volume ---
PV Name /dev/sda7
VG Name data_vg
PV Size 133.36 GB / NOT usable 321 KB [LVM: 255 KB]
PV# 1
PV Status available
Allocatable yes
Cur LV 6
PE Size (KByte) 4096
Total PE 34140
Free PE 7015
Allocated PE 27125
PV UUID C4Txkv-FIqY-RKJ4-OEoo-cTWc-LqZb-wFDBH0
--- Volume group ---
VG Name
VG Access read/write
VG Status NOT available/resizable
VG # 0
MAX LV 256
Cur LV 6
Open LV 0
MAX LV Size 255.99 GB
Max PV 256
Cur PV 1
Act PV 1
VG Size 133.36 GB
PE Size 4 MB
Total PE 34140
Alloc PE / Size 27125 / 105.96 GB
Free PE / Size 7015 / 27.4 GB
VG UUID XXUlZt-SdDC-3who-JMDC-13P1-adqU-MKgQrv
.......
Heinz J. Mauelshagen wrote:
>On Tue, Jul 17, 2001 at 09:23:23AM -0300, Patrick Boutilier wrote:
>
>>I tried running pvdata -U on one of my LVM servers and it segfaulted
>>(LVM driver version 0.9.1_beta6). Check out the UUIDs.
>>
>
>Output just tells you, that no UUIDs have been created dynamically so far.
>If you create/remove a dummy LV, they should be there...
>
>>Everything is
>>working OK but I wonder if this is a serious problem or not?
>>
>
>No, it is not. Just try the lvcreate/lvremove pair on a small (-l 1) dummy LV.
>
>Regards,
>Heinz -- The LVM Guy --
>
prev parent reply other threads:[~2001-07-17 13:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-17 12:23 [linux-lvm] Weird UUIDs Patrick Boutilier
2001-07-17 12:54 ` Heinz J. Mauelshagen
2001-07-17 13:21 ` Patrick Boutilier [this message]
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=3B543BDD.5040008@ednet.ns.ca \
--to=boutilpj@ednet.ns.ca \
--cc=linux-lvm@sistina.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