Is there a quick command in Linux to display all physical volumes that are
in a volume group?
I can do a "pvdisplay /dev/dasdc1" and it will tell me what volume group
dasdc1 is in, but aside from doing that command for all volumes (or going
through the menus in yast), can I tell what volumes are i
LVM volume groups...
Partial mode. Incomplete logical volumes will be processed.
1 logical volume(s) in volume group "VG1" now active
Thanks as always!
David M. Dean
[cid:image001.jpg@01CE61F5.A4E18D10]
-
Please see the following li
I want to set up a lv, but i find that clefOS does not have any of the
commands installed (pvcreate, vgcreate, lvcreate)
do i need to install some package(s) in order to get this capability?
--
Phillip Gramly
Systems Programmer
Communications Data Group
Champaign, Illinois
-
On Wed, 22 Aug 2018, Phillip Gramly wrote:
> I want to set up a lv, but i find that clefOS does not have any of the
> commands installed (pvcreate, vgcreate, lvcreate)
>
> do i need to install some package(s) in order to get this capability?
yes
A general solution to identify the owning package
As root, issue pvscan to see physcial volumes and what groups they are
in
vgscan shows active volume groups
lvscan shows active logical volumes
Betsie Spann
VM Systems Programmer
- Original Message -
From: "Robert J Brenneman" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECT
Robert J Brenneman
> Reply To: Linux on 390 Port
> Sent: Thursday, October 24, 2002 12:35 PM
> To: [EMAIL PROTECTED]
> Subject: Re: Logical Volumes
>
> vgdisplay -v
>
> Jay Brenneman
>
>
>
>
>
>
vgdisplay -v
Jay Brenneman
"Wolfe, Gordon W"
cc:
Sent by: Linux onSubject: Logical Volumes
390 Port
<[EMAIL PROTECTED]
cat /proc/lvm
Mark Post
-Original Message-
From: Wolfe, Gordon W [mailto:gordon.w.wolfe@;boeing.com]
Sent: Thursday, October 24, 2002 3:26 PM
To: [EMAIL PROTECTED]
Subject: Logical Volumes
Is there a quick command in Linux to display all physical volumes that are
in a volume group?
I
6 PM
> To: [EMAIL PROTECTED]
> Subject: Logical Volumes
>
> Is there a quick command in Linux to display all physical volumes that are
> in a volume group?
>
> I can do a "pvdisplay /dev/dasdc1" and it will tell me what volume group
> dasdc1 is in, but aside from d
physical volumes. This may take a while...
> Found volume group "VG1" using metadata type lvm2
> Activating LVM volume groups...
> Partial mode. Incomplete logical volumes will be processed.
> 1 logical volume(s) in volume gro
"Incomplete logical volumes"
-Original Message-
From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Mark Post
Sent: Wednesday, June 05, 2013 2:12 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Incomplete logical volumes
>>> On 6/5/2013 at 02:04 PM
>>> On 6/5/2013 at 02:15 PM, "Dean, David (I/S)" wrote:
> "Incomplete logical volumes"
"Partial mode. Incomplete logical volumes will be processed." is an
informational message that comes out when "-P" or "--partial" is specified on
t: Re: Incomplete logical volumes
>>> On 6/5/2013 at 02:15 PM, "Dean, David (I/S)" wrote:
> "Incomplete logical volumes"
"Partial mode. Incomplete logical volumes will be processed." is an
informational message that comes out when "-P" or "--p
>>> On 6/5/2013 at 02:38 PM, "Dean, David (I/S)" wrote:
> Ok, so no harm. Is this a failsafe for LVM's going bad, but that can be
> partially loaded?
>From what I can gather, yes. I would guess that the hope was the backup
>information under /etc/lvm/ might still be accessible to help recove
Subject: clefOS logical volumes
I want to set up a lv, but i find that clefOS does not have any of the commands
installed (pvcreate, vgcreate, lvcreate)
do i need to install some package(s) in order to get this capability?
--
Phillip Gramly
Systems Programmer
Communications Data Group
Cham
UX-390@VM.MARIST.EDU
Subject: clefOS logical volumes
I want to set up a lv, but i find that clefOS does not have any of the commands
installed (pvcreate, vgcreate, lvcreate)
do i need to install some package(s) in order to get this capability?
--
Phillip Gramly
Systems Programmer
Communications Data
I was so proud of myself yesterday after I created two
Logical-Volume-Groups, then their Logical-Volumes along with their
mount-points using Yast2 on a SuSE 9/LPAR-zSeries.
Today, the IPL could not take place due to the following messages:
Activating device mapper ...
device-mapper: 4.3.0
I just discovered a problem that I did not know I had. When building a new
server today on 11.2 I discovered it will not allow me to choose "by path" for
my logical volumes. We upgraded over 50 servers which all used "by path" with
no issues and they seemed to operating
I am wondering if anybody knows how to clean up a LV group that was not
properly removed by Yast.
I can see a soft link from /dev/bad-lv-name to /dev/mapper/bad-lv-name.
However, vgdisplay bad-lv-name cannot see it.
Yast cannot see it until I tried to re-use the bad-lv-name.
suggestions will be
Logical-Volumes along with their
mount-points using Yast2 on a SuSE 9/LPAR-zSeries.
Today, the IPL could not take place due to the following messages:
Activating device mapper ...
device-mapper: 4.3.0-ioctl (2004-09-30) initialized:
... done
Scanning for LVM Volume Groups
No volume groups
Volumes Disappeared after IPL
I was so proud of myself yesterday after I created two Logical-Volume-Groups,
then their Logical-Volumes along with their mount-points using Yast2 on a SuSE
9/LPAR-zSeries. Today, the IPL could not take place due to the following
messages: Activating device mapper
ST.EDU
Sent by: Linux oncc:
390 Port Subject: Re: Logical Volumes
Disappeared aft
David,
Logical volumes are usually referenced in /etc/fstab by their /dev entry.
For example:
/dev/opt_vg/opt_lv /opt ext3 acl,user_xattr 1
2
That is probably why by-path is not an option.
Then you write:
> caught this when I DDR'd our "golden image&q
ge in the 70's..?
-Original Message-
From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Michael
MacIsaac
Sent: Tuesday, December 03, 2013 9:56 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: sles11.2 mount logical volumes by path
David,
Logical volumes are usually refer
7;Linux on 390 Port'
Subject: sles11.2 mount logical volumes by path
I just discovered a problem that I did not know I had. When building a new
server today on 11.2 I discovered it will not allow me to choose "by path" for
my logical volumes. We upgraded over 50 servers which al
LVM --> BC4A
>
>
> Maybe I should not have attended college in the 70's..?
>
>
>
> -Original Message-
> From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of
> Michael MacIsaac
> Sent: Tuesday, December 03, 2013 9:56 AM
> To: LINUX-390@VM.
Dave,
Can you also post the contents of your /etc/fstab file, and perhaps the
output of pvdisplay, vgdisplay and lvdisplay?
"Mike MacIsaac"
--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists
rt [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Scott
Rohling
Sent: Tuesday, December 03, 2013 10:56 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: sles11.2 mount logical volumes by path
Since it looks like you're DDRing a whole DASD rather then a minidisk --
are you relabelling, etc?I'm c
4.00 MiB
> Total PE 11514
> Alloc PE / Size 11514 / 44.98 GiB
> Free PE / Size 0 / 0
> VG UUID l9PjbN-u8Ai-8BxO-d3sf-6KAM-htkA-uIf72w
>
>
>
>
>
> -Original Message-
> From: Linux on 390 Port [mailto
2
> Act PV2
> VG Size 44.98 GiB
> PE Size 4.00 MiB
> Total PE 11514
> Alloc PE / Size 11514 / 44.98 GiB
> Free PE / Size 0 / 0
> VG UUID l9PjbN-u8Ai-8BxO-d3sf-6KA
The flashing is done as full volumes starting at cylinder 0.
David Kreuter
Original message
From: Scott Rohling
Date: 12-03-2013 14:51 (GMT-05:00)
To: LINUX-390@VM.MARIST.EDU
Subject: Re: sles11.2 mount logical volumes by path
Is the clone directory entry a typo
Sent: Tuesday, December 03, 2013 2:51 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: sles11.2 mount logical volumes by path
Is the clone directory entry a typo? 32259 instead of 32759 ? Your gold
image also uses 32259 for the 202 disk.. so a little confusing in the numbers
between the 2 dire
Rohling
> Sent: Tuesday, December 03, 2013 2:51 PM
> To: LINUX-390@VM.MARIST.EDU
> Subject: Re: sles11.2 mount logical volumes by path
>
> Is the clone directory entry a typo? 32259 instead of 32759 ? Your gold
> image also uses 32259 for the 202 disk.. so a little confusing in
Behalf Of
>> Scott Rohling
>> Sent: Tuesday, December 03, 2013 2:51 PM
>> To: LINUX-390@VM.MARIST.EDU
>> Subject: Re: sles11.2 mount logical volumes by path
>>
>> Is the clone directory entry a typo? 32259 instead of 32759 ? Your gold
>> image also use
The 701 mdisk statement for the target newclone is incorrect.
David Kreuter
Original message
From: "Nix, Robert P."
Date: 12-04-2013 09:24 (GMT-05:00)
To: LINUX-390@VM.MARIST.EDU
Subject: Re: sles11.2 mount logical volumes by path
Actually, both entries a
S) >wrote:
> >
> >> Scott, I think you've got it, I will try tomorrow. Look at the LVM DASD
> >> sizes, I made the same mistake again! Hard to put 6 gallons in a 5
> gallon
> >> bucket. I will let you know.
> >>
> >> -Original Mess
36 matches
Mail list logo
