Re: LVM Question

2008-06-17 Thread Walters, Gene P 
The funny thing is when I go into yast, those inactive volumes don't
show as being in any VG, it just has -- for the group name.

-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of
Mark Post
Sent: Tuesday, June 17, 2008 1:12 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: LVM Question

>>> On Tue, Jun 17, 2008 at  1:07 PM, in message
<[EMAIL PROTECTED]
.gov>,
"Walters, Gene P" <[EMAIL PROTECTED]> wrote: 
> Here's what I see when I do the PVSCAN
> 
> pvscan -- reading all physical volumes (this may take a while...)
> pvscan -- ACTIVE   PV "/dev/dasdc1" of VG "oraclevg" [2.29 GB / 0
free]
> pvscan -- ACTIVE   PV "/dev/dasdd1" of VG "oraclevg" [2.29 GB / 0
free]
> pvscan -- ACTIVE   PV "/dev/dasde1" of VG "oraclevg" [2.29 GB / 0
free]
> pvscan -- ACTIVE   PV "/dev/dasdh1" of VG "oraclevg" [6.87 GB / 24 MB
> free]
> pvscan -- inactive PV "/dev/dasdk1" of VG "oraclevg" [6.87 GB / 6.87
GB
> free]
> pvscan -- inactive PV "/dev/dasdl1" of VG "oraclevg" [6.87 GB / 6.87
GB
> free]
> pvscan -- inactive PV "/dev/dasdm1" is in no VG  [6.88 GB]
> pvscan -- total: 7 [34.39 GB] / in use: 6 [27.51 GB] / in no VG: 1
[6.88
> GB]

Ok, that looks fine.  The "inactive" just means that no Physical Extents
(PEs) have been allocated on the new volumes yet.  You've got 24MB left
on your dasdh1 PV, so if you create a 30MB logical volume and re-run the
pvscan, it should show one of the new volumes as being ACTIVE (most
likely dasdk1).


Mark Post

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or
visit
http://www.marist.edu/htbin/wlvindex?LINUX-390

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390

Re: LVM Question

2008-06-17 Thread Mark Post 
>>> On Tue, Jun 17, 2008 at  1:07 PM, in message
<[EMAIL PROTECTED]>,
"Walters, Gene P" <[EMAIL PROTECTED]> wrote: 
> Here's what I see when I do the PVSCAN
> 
> pvscan -- reading all physical volumes (this may take a while...)
> pvscan -- ACTIVE   PV "/dev/dasdc1" of VG "oraclevg" [2.29 GB / 0 free]
> pvscan -- ACTIVE   PV "/dev/dasdd1" of VG "oraclevg" [2.29 GB / 0 free]
> pvscan -- ACTIVE   PV "/dev/dasde1" of VG "oraclevg" [2.29 GB / 0 free]
> pvscan -- ACTIVE   PV "/dev/dasdh1" of VG "oraclevg" [6.87 GB / 24 MB
> free]
> pvscan -- inactive PV "/dev/dasdk1" of VG "oraclevg" [6.87 GB / 6.87 GB
> free]
> pvscan -- inactive PV "/dev/dasdl1" of VG "oraclevg" [6.87 GB / 6.87 GB
> free]
> pvscan -- inactive PV "/dev/dasdm1" is in no VG  [6.88 GB]
> pvscan -- total: 7 [34.39 GB] / in use: 6 [27.51 GB] / in no VG: 1 [6.88
> GB]

Ok, that looks fine.  The "inactive" just means that no Physical Extents (PEs) 
have been allocated on the new volumes yet.  You've got 24MB left on your 
dasdh1 PV, so if you create a 30MB logical volume and re-run the pvscan, it 
should show one of the new volumes as being ACTIVE (most likely dasdk1).


Mark Post

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390

Re: LVM Question

2008-06-17 Thread Walters, Gene P 
Here's what I see when I do the PVSCAN

pvscan -- reading all physical volumes (this may take a while...)
pvscan -- ACTIVE   PV "/dev/dasdc1" of VG "oraclevg" [2.29 GB / 0 free]
pvscan -- ACTIVE   PV "/dev/dasdd1" of VG "oraclevg" [2.29 GB / 0 free]
pvscan -- ACTIVE   PV "/dev/dasde1" of VG "oraclevg" [2.29 GB / 0 free]
pvscan -- ACTIVE   PV "/dev/dasdh1" of VG "oraclevg" [6.87 GB / 24 MB
free]
pvscan -- inactive PV "/dev/dasdk1" of VG "oraclevg" [6.87 GB / 6.87 GB
free]
pvscan -- inactive PV "/dev/dasdl1" of VG "oraclevg" [6.87 GB / 6.87 GB
free]
pvscan -- inactive PV "/dev/dasdm1" is in no VG  [6.88 GB]
pvscan -- total: 7 [34.39 GB] / in use: 6 [27.51 GB] / in no VG: 1 [6.88
GB]

-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of
Mark Post
Sent: Tuesday, June 17, 2008 12:50 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: LVM Question

>>> On Tue, Jun 17, 2008 at 10:46 AM, in message
<[EMAIL PROTECTED]
.gov>,
"Walters, Gene P" <[EMAIL PROTECTED]> wrote: 
> I did a pvscan, and it shows that I have 4 active and 3 inactive PV's
> that belong to volume group oraclevg.  My question is, how does a PV
> become inactive, and is it really in my VG if it says inactive?

Can you show the actual output from that?  I can't say I've seen it
before.  And yes, the PVs are in the VG, even if they're marked
inactive.  Just try taking them offline and doing a vgscan.  Should be
ugly.


Mark Post

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or
visit
http://www.marist.edu/htbin/wlvindex?LINUX-390

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390

Re: LVM Question

2008-06-17 Thread Mark Post 
>>> On Tue, Jun 17, 2008 at 10:46 AM, in message
<[EMAIL PROTECTED]>,
"Walters, Gene P" <[EMAIL PROTECTED]> wrote: 
> I did a pvscan, and it shows that I have 4 active and 3 inactive PV's
> that belong to volume group oraclevg.  My question is, how does a PV
> become inactive, and is it really in my VG if it says inactive?

Can you show the actual output from that?  I can't say I've seen it before.  
And yes, the PVs are in the VG, even if they're marked inactive.  Just try 
taking them offline and doing a vgscan.  Should be ugly.


Mark Post

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390

Re: lvm question

2006-06-22 Thread Richard Pinion 
Everything except /boot is in the LVM.  That's the way the install set it up 
and I didn't bother to change it.  Next time I'll know better!

>>> [EMAIL PROTECTED] 6/22/2006 11:57 AM >>>
From: Richard Pinion <[EMAIL PROTECTED]>

> I am running Centos 4.3 under Hercules, kernel 2.6.9.  I recompiled the 
> kernel source and installed it.  I forgot to do the zipl command.  Now my 
> image fails during boot.  Luckily I backed up the Hercules disk images before 
> any of my changes.  I have re-ipled using the good images.  I would like to 
> mount the corrupted disks and run zipl.  I've attached the bad dasd images 
> and varied the new devices addresses online.   My problem is the corrupted 
> disk images belong to a logical volume group.  I'm not sure how to build 
> another lv group with the existing dasd images with a new lv group name.  The 
> good lv group names is /dev/VolGroup00.  I've done a pvscan and lvscan and 
> the newly attached devices are showing up.  But again, how do I form the new 
> vg

Richard, is the root FS really in the LVM you talk about? I.e you have the 
whole zLinux in LVM?

Assuming not, i.e. you have "/", "/boot", "/etc" in a non LVM FS, then you can 
forget the LVM disks, attach the disk with the root FS and mount the root FS on 
/mnt.

Then run command
chroot /mnt zipl

I'm doing this from my head, so can someone confirm :-)

Mark

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390

Re: lvm question

2006-06-22 Thread Mark Perry 
From: Richard Pinion <[EMAIL PROTECTED]>

> I am running Centos 4.3 under Hercules, kernel 2.6.9.  I recompiled the 
> kernel source and installed it.  I forgot to do the zipl command.  Now my 
> image fails during boot.  Luckily I backed up the Hercules disk images before 
> any of my changes.  I have re-ipled using the good images.  I would like to 
> mount the corrupted disks and run zipl.  I've attached the bad dasd images 
> and varied the new devices addresses online.   My problem is the corrupted 
> disk images belong to a logical volume group.  I'm not sure how to build 
> another lv group with the existing dasd images with a new lv group name.  The 
> good lv group names is /dev/VolGroup00.  I've done a pvscan and lvscan and 
> the newly attached devices are showing up.  But again, how do I form the new 
> vg

Richard, is the root FS really in the LVM you talk about? I.e you have the 
whole zLinux in LVM?

Assuming not, i.e. you have "/", "/boot", "/etc" in a non LVM FS, then you can 
forget the LVM disks, attach the disk with the root FS and mount the root FS on 
/mnt.

Then run command
chroot /mnt zipl

I'm doing this from my head, so can someone confirm :-)

Mark

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390

Re: LVM Question

2005-03-17 Thread Post, Mark K 
Once I found out about the e2fsadm command, I stopped using lvextend,
because e2fsadm does everything for you:
umount the file system
e2fsadm -L +1G /dev/vg01/lv0l1
mount the file system

It does the lvextend, then the fsck that resize2fs always requires, then the
resize2fs.  Lovely, and works just fine on ext3 file systems as well.


Mark Post

-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Hugo
Rivera
Sent: Thursday, March 17, 2005 11:14 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: LVM Question


I'm sorry, I forgot the main step, before you mount your file system you
MUST resize your logical volume:

resize2fs  /dev/vgroup/volx

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390

Re: LVM Question

2005-03-17 Thread Hugo Rivera 
I'm sorry, I forgot the main step, before you mount your file system you MUST 
resize your logical volume:

resize2fs  /dev/vgroup/volx

Hugo Rivera
SSA II
County of Contra Costa
Department of Information Technology
30 Douglas Drive,
Martinez, CA 94553-4068

Tel:(925) 313-1309
Nextel:   (925) 383-5781
Fax:   (925) 313-1459
Pager:   (925) 975-7479
email: [EMAIL PROTECTED]



   
  José Raúl Barón
  RodríguezTo:   LINUX-390@VM.MARIST.EDU
  <[EMAIL PROTECTED]cc: 
  a.es>Subject:  LVM Question  
  Sent by: Linux on
  390 Port 
  <[EMAIL PROTECTED]
  IST.EDU> 
   
   
  03/17/2005 12:29 
  AM   
  Please respond to
  jbaron   
   
   




I have currently a database in a filesystem located in a DASD. I would
like to add 2 more DASD to this filesystem using LVM.

Do I have to erase previously all the data in my first DASD ? or does
this disk enhancement respect the previously existing data ?

Saludos,




José Raúl Barón
Dpto. Sistemas
CALCULO S.A.
Tel. 91 330 86 44
e-mail: [EMAIL PROTECTED]



-Mensaje original-
De: Linux on 390 Port [mailto:[EMAIL PROTECTED] En nombre de
Kelly, Patrick
Enviado el: miércoles, 16 de marzo de 2005 21:02
Para: LINUX-390@VM.MARIST.EDU
Asunto: Re: LVM - maximum PV's?


Is there a device defined for it in the /dev directory?
For example, /dev/dasdaa, /dev/dasdaa1, /dev/dasdaa2, /dev/dasdaa3. You
can create them with the mknod command.

Patrick Kelly
System Programmer
State Teachers Retirement System of Ohio
Information Technology Services (ITS)
E-mail: [EMAIL PROTECTED]
Phone:  614-227-2908



-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of
Kinnear, Mike
Sent: Wednesday, March 16, 2005 2:47 PM
To: LINUX-390@VM.MARIST.EDU
Subject: LVM - maximum PV's?

On a SUSE SLES8 system I've created an LVM with 15 full mod-3 3390's and
8 mod-9's. I cannot get the 9th mod-9 to becoem a member of LVM. the
pvcreate appears to work OK, but the volume is not on the pvscan list,
nor included in the vgdisplay total. Any ideas?

--
For LINUX-390 subscribe / signoff / archive access instructions, send
email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or
visit http://www.marist.edu/htbin/wlvindex?LINUX-390

--
For LINUX-390 subscribe / signoff / archive access instructions, send
email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or
visit http://www.marist.edu/htbin/wlvindex?LINUX-390

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390


--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390

Re: LVM Question

2005-03-17 Thread Hugo Rivera 
You don't have to.
First create new physical volumes:

pvcreate  /dev/dasdx1 /dev/dasdy1

Add new volumes to your volume group:

vgextend /dev/vgroup /dev/dasdx1 /dev/dasdy1

At this time you may see the new volumes added using "vgdisplay /dev/vgroup"

Unmount your file system:

umount /uxxx

Extend your logical volume:

 lvextend -L+1G /dev/vgroupx/volx (if you want to extend 1 giga).

Mount your file system:

mount  /dev/vgroup/volx  /uxx

I hope this can help you.


Hugo Rivera
SSA II
County of Contra Costa
Department of Information Technology




   
  José Raúl Barón
  RodríguezTo:   LINUX-390@VM.MARIST.EDU
  <[EMAIL PROTECTED]cc: 
  a.es>Subject:  LVM Question  
  Sent by: Linux on
  390 Port 
  <[EMAIL PROTECTED]
  IST.EDU> 
   
   
  03/17/2005 12:29 
  AM   
  Please respond to
  jbaron   
   
   




I have currently a database in a filesystem located in a DASD. I would
like to add 2 more DASD to this filesystem using LVM.

Do I have to erase previously all the data in my first DASD ? or does
this disk enhancement respect the previously existing data ?

Saludos,




José Raúl Barón
Dpto. Sistemas
CALCULO S.A.
Tel. 91 330 86 44
e-mail: [EMAIL PROTECTED]



-Mensaje original-
De: Linux on 390 Port [mailto:[EMAIL PROTECTED] En nombre de
Kelly, Patrick
Enviado el: miércoles, 16 de marzo de 2005 21:02
Para: LINUX-390@VM.MARIST.EDU
Asunto: Re: LVM - maximum PV's?


Is there a device defined for it in the /dev directory?
For example, /dev/dasdaa, /dev/dasdaa1, /dev/dasdaa2, /dev/dasdaa3. You
can create them with the mknod command.

Patrick Kelly
System Programmer
State Teachers Retirement System of Ohio
Information Technology Services (ITS)
E-mail: [EMAIL PROTECTED]
Phone:  614-227-2908



-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of
Kinnear, Mike
Sent: Wednesday, March 16, 2005 2:47 PM
To: LINUX-390@VM.MARIST.EDU
Subject: LVM - maximum PV's?

On a SUSE SLES8 system I've created an LVM with 15 full mod-3 3390's and
8 mod-9's. I cannot get the 9th mod-9 to becoem a member of LVM. the
pvcreate appears to work OK, but the volume is not on the pvscan list,
nor included in the vgdisplay total. Any ideas?

--
For LINUX-390 subscribe / signoff / archive access instructions, send
email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or
visit http://www.marist.edu/htbin/wlvindex?LINUX-390

--
For LINUX-390 subscribe / signoff / archive access instructions, send
email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or
visit http://www.marist.edu/htbin/wlvindex?LINUX-390

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390


--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390

Re: LVM question

2004-12-10 Thread Michael Lambert 
> Is there some magic now that I need to perform to make this permanent?  What
>should be my next step?

Compare the output of lsmod both before and after the reboot. Unless you ran
mk_initrd after the LVM modules were loaded it's very likely that they aren't
included in your initrd and, consequently, aren't being loaded at reboot.

Michael Lambert
Louisiana State University

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390

Re: LVM question

2004-12-08 Thread dclark 
I went through the yast panels and added the unit "113e"; created the volume
group usrdata; added the physical volume (/dev/dasdd1) to the volume group
usrdata; and added the logical volume /dev/usrdata/srv.

Output from "pvscan," "vgscan," and "lvscan" shows:

>   techlnux:~ # pvscan
> PV /dev/dasdd1   VG usrdata   lvm2 [2.29 GB / 1.80 GB free]
> PV /dev/dasdc1   VG systemlvm2 [2.29 GB / 0free]
> PV /dev/dasda1   VG systemlvm2 [2.29 GB / 68.00 MB free]
> Total: 3 [6.87 GB] / in use: 3 [6.87 GB] / in no VG: 0 [0   ]
>   techlnux:~ # vgscan
> Reading all physical volumes.  This may take a while...
> Found volume group "usrdata" using metadata type lvm2
> Found volume group "system" using metadata type lvm2
>   techlnux:~ # lvscan
> ACTIVE'/dev/usrdata/srv' [500.00 MB] next free
(default)
> ACTIVE'/dev/system/var' [3.30 GB] next free (default)
> ACTIVE'/dev/system/home' [512.00 MB] next free
(default)

Output from "vgdisplay" shows:

>   techlnux:~ # vgdisplay
> --- Volume group ---
> VG Name   usrdata
> System ID
> Formatlvm2
> Metadata Areas1
> Metadata Sequence No  2
> VG Access read/write
> VG Status resizable
> MAX LV255
> Cur LV1
> Open LV   1
> Max PV255
> Cur PV1
> Act PV1
> VG Size   2.29 GB
> PE Size   4.00 MB
> Total PE  586
> Alloc PE / Size   125 / 500.00 MB
> Free  PE / Size   461 / 1.80 GB
> VG UUID   F4TBxx-SrI3-70gb-RSaE-hWCX-MHHY-BUEHgP
>
> --- Volume group ---
> VG Name   system
> System ID
> Formatlvm2
> Metadata Areas2
> Metadata Sequence No  10
> VG Access read/write
> VG Status resizable
> MAX LV255
> Cur LV3
> Open LV   3
> Max PV255
> Cur PV2
> Act PV2
> VG Size   4.58 GB
> PE Size   4.00 MB
> Total PE  1172
> Alloc PE / Size   1155 / 4.51 GB
> Free  PE / Size   17 / 68.00 MB
> VG UUID   udixdw-j6fY-Sgqn-vo9w-VgL4-w6gq-Xy72m3

Output from "ls -l /dev/usrdata" shows:

>   techlnux:~ # ls -l /dev/usrdata
>   total 88
>   dr-x--   2 root root  4096 Dec  8 09:07 .
>   drwxr-xr-x  14 root root 81920 Dec  8 09:07 ..
>   lrwxrwxrwx   1 root root23 Dec  8 09:07 srv ->
/dev/mapper/usrdata-srv

Output from "ls -l /dev/mapper" shows:

>   techlnux:~ # ls -l /dev/mapper
>   total 88
>   drwxr-xr-x   2 root root   4096 Dec  8 09:07 .
>   drwxr-xr-x  14 root root  81920 Dec  8 09:07 ..
>   lrwxrwxrwx   1 root root 16 Dec  7 16:56 control ->
../device-mapper
>   brw---   1 root root 253, 2 Nov  4 13:03 system-home
>   brw---   1 root root 253, 1 Nov  4 13:03 system-opt
>   brw---   1 root root 253, 0 Nov  4 13:03 system-var
>   brw---   1 root root 253, 3 Dec  8 09:07 usrdata-srv

Is there some magic now that I need to perform to make this permanent?  What
should be my next step?

-Original Message-
From: Mark Post [mailto:[EMAIL PROTECTED]
Sent: Tuesday, December 07, 2004 6:01 PM
To: [EMAIL PROTECTED]
Subject: Re: LVM question


Ok, this looks like a difference between LVM and the LVM2 that comes with
2.6.  I guess "vgdisplay" and "ls -l /dev/usrdata" might tell us something.


Mark Post

-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of
[EMAIL PROTECTED]
Sent: Tuesday, December 07, 2004 8:06 PM
To: [EMAIL PROTECTED]
Subject: Re: LVM question


I crossed up too many systems trying to get this to work and I had to
restore from backups.

I then ran "pvscan" sans quotes

>   techlnux:/proc # pvscan
> PV /dev/dasdc1   VG system   lvm2 [2.29 GB / 0free]
> PV /dev/dasda1   VG system   lvm2 [2.29 GB / 68.00 MB free]
> Total: 2 [4.58 GB] / in use: 2 [4.58 GB] / in no VG: 0 [0   ]

When I ran "cat /proc/lvm/global" sans quotes I received:

No such file or directory

http://www.marist.edu/htbin/wlvinde

Re: LVM question

2004-12-07 Thread dclark 
I had to restore back to a state previous to the creation of usrdata.  I
have LVM with system VG and so I captured it.  I get the same error when I
tried to add a logical volume to system also.


techlnux:~ # vgdisplay
  --- Volume group ---
  VG Name   system
  System ID
  Formatlvm2
  Metadata Areas2
  Metadata Sequence No  10
  VG Access read/write
  VG Status resizable
  MAX LV255
  Cur LV3
  Open LV   3
  Max PV255
  Cur PV2
  Act PV2
  VG Size   4.58 GB
  PE Size   4.00 MB
  Total PE  1172
  Alloc PE / Size   1155 / 4.51 GB
  Free  PE / Size   17 / 68.00 MB
  VG UUID   udixdw-j6fY-Sgqn-vo9w-VgL4-w6gq-Xy72m3

techlnux:~ # ls -l /dev/system
total 88
dr-x--   2 root root  4096 Dec  7 16:56 .
drwxr-xr-x  13 root root 81920 Dec  7 16:57 ..
lrwxrwxrwx   1 root root23 Dec  7 16:56 home -> /dev/mapper/system-home
lrwxrwxrwx   1 root root22 Dec  7 16:56 opt -> /dev/mapper/system-opt
lrwxrwxrwx   1 root root22 Dec  7 16:56 var -> /dev/mapper/system-var
techlnux:~ # ls -l /dev/usrdata

-Original Message-
From: Mark Post [mailto:[EMAIL PROTECTED]
Sent: Tuesday, December 07, 2004 6:01 PM
To: [EMAIL PROTECTED]
Subject: Re: LVM question


Ok, this looks like a difference between LVM and the LVM2 that comes with
2.6.  I guess "vgdisplay" and "ls -l /dev/usrdata" might tell us something.


Mark Post

-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of
[EMAIL PROTECTED]
Sent: Tuesday, December 07, 2004 8:06 PM
To: [EMAIL PROTECTED]
Subject: Re: LVM question


I crossed up too many systems trying to get this to work and I had to
restore from backups.

I then ran "pvscan" sans quotes

>   techlnux:/proc # pvscan
> PV /dev/dasdc1   VG system   lvm2 [2.29 GB / 0free]
> PV /dev/dasda1   VG system   lvm2 [2.29 GB / 68.00 MB free]
> Total: 2 [4.58 GB] / in use: 2 [4.58 GB] / in no VG: 0 [0   ]

When I ran "cat /proc/lvm/global" sans quotes I received:

No such file or directory

http://www.marist.edu/htbin/wlvindex?LINUX-390

--
For LINUX-390 subscribe / signoff / archive access instructions, send email
to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390

Re: LVM question

2004-12-07 Thread Mark Post 
Ok, this looks like a difference between LVM and the LVM2 that comes with
2.6.  I guess "vgdisplay" and "ls -l /dev/usrdata" might tell us something.


Mark Post

-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of
[EMAIL PROTECTED]
Sent: Tuesday, December 07, 2004 8:06 PM
To: [EMAIL PROTECTED]
Subject: Re: LVM question


I crossed up too many systems trying to get this to work and I had to
restore from backups.

I then ran "pvscan" sans quotes

>   techlnux:/proc # pvscan
> PV /dev/dasdc1   VG system   lvm2 [2.29 GB / 0free]
> PV /dev/dasda1   VG system   lvm2 [2.29 GB / 68.00 MB free]
> Total: 2 [4.58 GB] / in use: 2 [4.58 GB] / in no VG: 0 [0   ]

When I ran "cat /proc/lvm/global" sans quotes I received:

No such file or directory

http://www.marist.edu/htbin/wlvindex?LINUX-390

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390

Re: LVM question

2004-12-07 Thread dclark 
I crossed up too many systems trying to get this to work and I had to
restore from backups.

I then ran "pvscan" sans quotes

>   techlnux:/proc # pvscan
> PV /dev/dasdc1   VG system   lvm2 [2.29 GB / 0free]
> PV /dev/dasda1   VG system   lvm2 [2.29 GB / 68.00 MB free]
> Total: 2 [4.58 GB] / in use: 2 [4.58 GB] / in no VG: 0 [0   ]

When I ran "cat /proc/lvm/global" sans quotes I received:

No such file or directory


-Original Message-
From: Mark Post [mailto:[EMAIL PROTECTED]
Sent: Tuesday, December 07, 2004 4:47 PM
To: [EMAIL PROTECTED]
Subject: Re: LVM question


What does the output of "cat /proc/lvm/global" show you?


Mark Post

-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of
[EMAIL PROTECTED]
Sent: Tuesday, December 07, 2004 7:20 PM
To: [EMAIL PROTECTED]
Subject: LVM question


SLES9 for S/390 (31-bit) in an LPAR > (no VM) using a shared IFL

I must be missing something -- but things may be different under SLES9

Currently I have /srv filesytem under root.  I would like to "/srv" under
LVM.

I keep getting an error during the IPL stating "/sbin/fsck.reiserfs /srv
failed open the device /dev/usrdata/srv"?  What am I missing.  I have
successfully created the new volume group, added the physical dasd volume to
the group.  Created the logical volume group.  Ran fsck.reiserfs mounted the
device updated fstab and ran zipl.  There must be something else but I don't
see it.

Thanks

--
For LINUX-390 subscribe / signoff / archive access instructions, send email
to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390

--
For LINUX-390 subscribe / signoff / archive access instructions, send email
to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390

Re: LVM question

2004-12-07 Thread Mark Post 
What does the output of "cat /proc/lvm/global" show you?


Mark Post

-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of
[EMAIL PROTECTED]
Sent: Tuesday, December 07, 2004 7:20 PM
To: [EMAIL PROTECTED]
Subject: LVM question


SLES9 for S/390 (31-bit) in an LPAR > (no VM) using a shared IFL

I must be missing something -- but things may be different under SLES9

Currently I have /srv filesytem under root.  I would like to "/srv" under
LVM.

I keep getting an error during the IPL stating "/sbin/fsck.reiserfs /srv
failed open the device /dev/usrdata/srv"?  What am I missing.  I have
successfully created the new volume group, added the physical dasd volume to
the group.  Created the logical volume group.  Ran fsck.reiserfs mounted the
device updated fstab and ran zipl.  There must be something else but I don't
see it.

Thanks

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or
visit
http://www.marist.edu/htbin/wlvindex?LINUX-390

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390

Re: LVM Question

2004-02-25 Thread Hall, Ken (IDS ECCS) 
Yes, we confirmed this some time ago.  The number of stripes HAS to equal the number 
of physical volumes in the LV.

You can have a VG of, say, 10 PV's, with two striped LV's, 5 and 5 (both 5 stripes) or 
6 and 4 (6 and 4 stripes), but if you want all 10 PV's in one LV, it has to be 10 
stripes.

We have some very large LV's that are 29 stripes.  Seems to work fine.

> -Original Message-
> From: Linux on 390 Port [mailto:[EMAIL PROTECTED]
> Behalf Of Vic
> Cross
> Sent: Saturday, February 21, 2004 7:31 AM
> To: [EMAIL PROTECTED]
> Subject: Re: [LINUX-390] LVM Question
>
>
> G'day Dave,
>
> On Fri, 20 Feb 2004, Dave MYERS wrote:
>
> > I tried using more mod 9's...but kept getting the same msg.
> > The only way it would let me build this 100gb filesystem
> was with STRIPE=1.
>
> What value(s) did you use for stripe?  I have seen someplace
> (and it makes
> sense to me, and indeed has worked for me) that the number of
> stripes for
> the logical volume should equal the number of physical volumes in the
> volume group.  (It makes sense to me because this way you would be
> spreading the data access evenly over all of the PVs in the VG.)
>
> Did the volume group already have one or more logical volumes
> allocated?
>
> Cheers,
> Vic Cross
>

==

If you are not an intended recipient of this e-mail, please notify
the sender, delete it and do not read, act upon, print, disclose,
copy, retain or redistribute it.

Click here for important additional terms relating to this e-mail.
 

==

Re: LVM Question

2004-02-21 Thread Vic Cross 
G'day Dave,

On Fri, 20 Feb 2004, Dave MYERS wrote:

> I tried using more mod 9's...but kept getting the same msg.
> The only way it would let me build this 100gb filesystem was with STRIPE=1.

What value(s) did you use for stripe?  I have seen someplace (and it makes
sense to me, and indeed has worked for me) that the number of stripes for
the logical volume should equal the number of physical volumes in the
volume group.  (It makes sense to me because this way you would be
spreading the data access evenly over all of the PVs in the VG.)

Did the volume group already have one or more logical volumes allocated?

Cheers,
Vic Cross

Re: LVM question

2002-07-26 Thread Konkol, Josh 

Don't know what happened to my earlier reply, but I told him he needed to
create a logical volume as well as the volume group.

Josh

-Original Message-
From: Post, Mark K [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, July 24, 2002 3:33 PM
To: [EMAIL PROTECTED]
Subject: Re: LVM question


That sounds like a perfectly legitimate reason to me.  Josh's reply hasn't
hit my inbox or the list archives yet.  What was it he suggested?

Mark Post

-Original Message-
From: Marcy Cortes [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, July 24, 2002 3:02 PM
To: [EMAIL PROTECTED]
Subject: Re: LVM question


Thanks Josh!  That is what I needed to do.

Mark, I rebooted just because!  I wanted to see
if it really was there and how the messages
changed at start up.  Newbie learning I guess.
It was pretty clear to me that I didn't need to
reboot from the stuff in the distributions
redbook.

__
Marcy Cortes, Wells Fargo Services Co

Re: LVM question

2002-07-24 Thread Post, Mark K 

That sounds like a perfectly legitimate reason to me.  Josh's reply hasn't
hit my inbox or the list archives yet.  What was it he suggested?

Mark Post

-Original Message-
From: Marcy Cortes [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, July 24, 2002 3:02 PM
To: [EMAIL PROTECTED]
Subject: Re: LVM question


Thanks Josh!  That is what I needed to do.

Mark, I rebooted just because!  I wanted to see
if it really was there and how the messages
changed at start up.  Newbie learning I guess.
It was pretty clear to me that I didn't need to
reboot from the stuff in the distributions
redbook.

__
Marcy Cortes, Wells Fargo Services Co

Re: LVM question

2002-07-24 Thread Marcy Cortes 

Thanks Josh!  That is what I needed to do.

Mark, I rebooted just because!  I wanted to see
if it really was there and how the messages
changed at start up.  Newbie learning I guess.
It was pretty clear to me that I didn't need to
reboot from the stuff in the distributions
redbook.

__
Marcy Cortes, Wells Fargo Services Co

Re: LVM question

2002-07-24 Thread Marist EDU 

After you create the volume group you need to hit F3 and add a Logical
Volume.

Then the name is:  /dev/NAMEOFVOLUMEGROUP/NAMEOFLOGICALVOLUME.

After that you mke2fs it.

Josh

-Original Message-
From: Marcy Cortes [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, July 24, 2002 1:07 PM
To: [EMAIL PROTECTED]
Subject: LVM question


I've been trying to search through the archives, but it
never comes back to me so I'll ask here (sorry, I'm
sure this has been asked before).

I'm trying to use LVM for the first time.  I'm running
SuSE 2.4 kernel.   So I created my 2 minidisks,
dasdfmt 'd them, fdasd'd them, went into Yast and
chose the 2 disks and created a volume group called "prod".

I rebooted and see these messages so I'm pretty sure
it exists:

Scanning for LVM volume groups...
LVM version 0.9.1_beta7  by Heinz Mauelshagen  (10/04/2001)
lvm -- Module successfully initialized
vgscan -- reading all physical volumes (this may take a while...)
vgscan -- found inactive volume group "prod"
vgscan -- "/etc/lvmtab" and "/etc/lvmtab.d" successfully created
vgscan -- WARNING: This program does not do a VGDA backup of your volume
group

Activating LVM volume groups...
vgchange -- volume group "prod" successfully activated

Now, I suspect I need to mke2fs it, right?  My question is
what is it called?   The s/390 distributions redbook seems to
indicate that it might be /dev/prod/lvol1, but this doens't
work or seem to exist.

Can someone buy me a clue?

__
Marcy Cortes, VM Systems Programming, 415-243-6343