Re: LUN ID addition to LVM Redhat

tance-on-ibm-z > > In either case, a running multipathd ensures the new LUN paths are > automatically assembled into a new multipath device representing your new > volume. > > https://public.dhe.ibm.com/software/dw/linux390/lvc/zFCP_Best_Practices-BB-Webcast_201805.pdf#page=15 >

Re: LUN ID addition to LVM Redhat

your new volume. https://public.dhe.ibm.com/software/dw/linux390/lvc/zFCP_Best_Practices-BB-Webcast_201805.pdf#page=15 https://public.dhe.ibm.com/software/dw/linux390/lvc/zFCP_Best_Practices-BB-Webcast_201805.pdf#page=16 You can then prepare the new volume as you did for your already existing LVM

LUN ID addition to LVM Redhat

Hello I must confess that I have little knowledge about Multipathing but still based on my research below is what I understood My storage team has given a LUN ID of 500g So as per df -TH I see /dev/mapper/bradvg2-u03_lv is mounted on /u03 So similarly I have to create another mount point with

Re: LVM does not come online after reboot. PVMOVE used to migrate data.

That was going to my next question. We have run into similar with LVM with ECKD stuff after new disks have been added. We opened tickets and all have been fixed with updates to various pieces (lvm2 being one I remembered). -Original Message- From: Linux on 390 Port On Behalf

Re: LVM does not come online after reboot. PVMOVE used to migrate data.

s390x s390x GNU/Linux multipath-tools-0.7.3+153+suse.80d9ed4-2.16.1.s390x lvm2-2.02.180-9.34.8.s390x Thanks everyone for helping out with this. I got a lot of good information and learned a lot about the internals of LVM. Still far from an expert, but at least a I

Re: LVM does not come online after reboot. PVMOVE used to migrate data.

When it's up, try running grub2-mkconfig -o /boot/grub2/grub.cfg grub2-install dracut -f -Original Message- From: Linux on 390 Port On Behalf Of Duane Beyer Sent: Sunday, December 6, 2020 8:14 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: [LINUX-390] LVM does

Re: LVM does not come online after reboot. PVMOVE used to migrate data.

Thanks Mike, That is the temporary plan as a work around, but I really need to fix the root cause. I did receive a message external to the list about checking the global_filter in /etc/lvm/lvm.conf. That’s what I am going to look at today. I'll post my results. Duane -Original

Re: LVM does not come online after reboot. PVMOVE used to migrate data.

-Original Message- From: Linux on 390 Port On Behalf Of Marcio da Silva Nunes Sent: Saturday, December 5, 2020 2:58 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: LVM does not come online after reboot. PVMOVE used to migrate data. Duane, A possibility that can be verified. When use the text-based

Re: LVM does not come online after reboot. PVMOVE used to migrate data.

-Centro de Dados Diretoria de Operações +55 (61)2021-9099 +55 (61) 99981-0376 - Mensagem original - De: "Duane Beyer" Para: "Linux on 390 Port" Enviadas: Sábado, 5 de dezembro de 2020 12:28:39 Assunto: Re: LVM does not come online after reboot. PVMOVE used to migrate

Re: LVM does not come online after reboot. PVMOVE used to migrate data.

Subject: Re: LVM does not come online after reboot. PVMOVE used to migrate data. Duane, Let's see if it helps. Were the new FCP that are not associated with root included in the zfcp.conf file? If they are part of the root system disk then they must be in zipl.conf. Maybe it works. Marcio da

Re: LVM does not come online after reboot. PVMOVE used to migrate data.

Diretoria de Operações +55 (61)2021-9099 +55 (61) 99981-0376 - Mensagem original - De: "Duane Beyer" Para: LINUX-390@VM.MARIST.EDU Enviadas: Sexta-feira, 4 de dezembro de 2020 18:01:08 Assunto: Re: LVM does not come online after reboot. PVMOVE used to migrate data. I s

Re: LVM does not come online after reboot. PVMOVE used to migrate data.

I should have included this. Status, NOT available This is what LVDISPLAY displays for the LVM disks: --- Logical volume --- LV Path/dev/u01/u01 LV Nameu01 VG Nameu01 LV UUID6qzW2g-xJr4-osII-ULfn-d9nb-VscF-saGdBL LV

LVM does not come online after reboot. PVMOVE used to migrate data.

until we rebooted one of the systems using the new LUNS. The system went into emergency mode. The following action was taken to recover: The LVM disks were commented out of fstab and the system was rebooted. The system came up clean without the SCSI disks. At this point, I issued a lvchange

Re: unstable LVM on SLES 12

message," just a status display. -snip- > 2) The upgrade was very slow and struggle. (The Linux system was useable > after 3 reboot, and there was many device(dasd)/lvm/FS error.) > In the SLES12 I saw many simlar errror messages: > WARNING: Device for PV x5zvM9-l42o-ifVM-zMWC-NgT5-dZ8

Re: Adding disk to root LVM with RHEL 7

From: Linux on 390 Port on behalf of Jan Stodola Sent: Thursday, April 16, 2020 3:36 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: Adding disk to root LVM with RHEL 7 On Wed, Apr 15, 2020 at 10:29 PM Martha McConaghy < martha.mccona...@marist.edu> wrote: > I feel like Alic

Re: Adding disk to root LVM with RHEL 7

/etc/dasd.conf, I ran mkinitrd > and zipl. Then, I rebooted. I did NOT touch the LVM, or anything, at that > point. This resulted in a bunch of dracut timeout errors and am now in > dracut emergency mode. I'm about to give up and just give this darned > thing a TB LUN and be done wi

Re: Adding disk to root LVM with RHEL 7

.conf, I ran mkinitrd and zipl. Then, I rebooted. I did > NOT touch the LVM, or anything, at that point. This resulted in a > bunch of dracut timeout errors and am now in dracut emergency mode. > I'm about to give up and just give this darned thing a TB LUN and be > done with it. But, t

Re: Adding disk to root LVM with RHEL 7

: Linux on 390 Port On Behalf Of Martha McConaghy Sent: Wednesday, April 15, 2020 1:26 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: [LINUX-390] Adding disk to root LVM with RHEL 7 I feel like Alice through the looking glass at this point. I was hopeful that mkinitrd would do the trick, but now I

Re: Adding disk to root LVM with RHEL 7

I feel like Alice through the looking glass at this point. I was hopeful that mkinitrd would do the trick, but now I have a whole new problem. After bringing the disk online, adding it to /etc/dasd.conf, I ran mkinitrd and zipl. Then, I rebooted. I did NOT touch the LVM, or anything

Re: Adding disk to root LVM with RHEL 7

Also make sure that you add the address "0.0.0200" to the /etc/dasd.conf file Larry Davis (z/VM Team) -Original Message- From: Linux on 390 Port On Behalf Of Cohen, Sam Sent: Wednesday, April 15, 2020 12:06 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: Adding disk to root LVM w

Re: Adding disk to root LVM with RHEL 7

On 4/15/20 12:02 PM, Martha McConaghy wrote: > Ah, DOH! I did not run mkinitrd and am now kicking myself. (Its OK, I need > the exercise.) I'll give that a try and see if it makes a difference. Do yourself a favor and remove the cio_ignore parameter from /etc/zipl.conf entirely. It's a z/VM

Re: Adding disk to root LVM with RHEL 7

Sorry Thanks, Sam (217) 862-9227 (office) (602) 327-2134 (cell) -Original Message- From: Linux on 390 Port On Behalf Of Marcy Cortes Sent: Wednesday, April 15, 2020 8:57 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: Adding disk to root LVM with RHEL 7 Martha not Marcy

Re: Adding disk to root LVM with RHEL 7

Martha not Marcy :) -Original Message- From: Linux on 390 Port On Behalf Of Cohen, Sam Sent: Wednesday, April 15, 2020 8:55 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: [LINUX-390] Adding disk to root LVM with RHEL 7 Marcy, Did you check zipl.conf to see if you need to list the disk

Re: Adding disk to root LVM with RHEL 7

From: Linux on 390 Port on behalf of Marcy Cortes Sent: Wednesday, April 15, 2020 11:42 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: Adding disk to root LVM with RHEL 7 I'm kind of assuming RH7 works like sles11 and doesn't use grub2, but did you "mkinird;

Re: Adding disk to root LVM with RHEL 7

t On Behalf Of Rick Troth Sent: Wednesday, April 15, 2020 8:26 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: [LINUX-390] Adding disk to root LVM with RHEL 7 Looks like you did everything right: online, dasdfmt, fdasd, lvextend, vgextend, and using "1" instead of the whole disk (because i

Re: Adding disk to root LVM with RHEL 7

: Wednesday, April 15, 2020 8:43 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: Adding disk to root LVM with RHEL 7 I'm kind of assuming RH7 works like sles11 and doesn't use grub2, but did you "mkinird; zipl" after getting that disk online? You can also "cat / run/initramfs/

Re: Adding disk to root LVM with RHEL 7

or several) in any filesystem, any backing store (CKD, FBA, SCSI/SAN), anymode (LVM, partitioned, whole). Never know when the system or some program will walk to the end "just because". -- R; <>< On 4/15/20 10:58 AM, Martha McConaghy wrote: > I have servers that I'm setting u

Adding disk to root LVM with RHEL 7

I have servers that I'm setting up with RHEL 7.8 on ECKD disk. I installed it with root in an LVM, all of that worked fine. Now, I'm testing adding a 2nd ECKD disk to the LVM as I know that will be required in the future, but I'm running into a confusing problem. Everything works as I expect

Re: unstable LVM on SLES 12

Hello Csaba, My experience leads me to believe that a step or steps in the upgrade process are the root cause of the issues that you are seeing. You mention making a backup of the OS DASD but it is unclear to me if you tried to perform a test upgrade on this backup DASD.  The LVM entries

unstable LVM on SLES 12

from the used disks (PVs, LVs also). This was the staus till the new attempt of Linux upgrade. 1 ) After it (on the last week), I started the OS upgrade again. I created a full backup about the Linux OS (SLES 11) to a new disk before the upgrade. (The Linux itself is only on a pure 1 disk

Re: Replacement the root disk with a larger disk (without LVM)

On 9/12/19 5:19 PM, Marcy Cortes wrote: Just went through all this a while ago! Here's my instructions for my 101 -> 201 move 2. Enlarge the 101 disk if not already 1000 cyl (non LVM) # Allocate a 1000 cyl disk at address 201 vmcp link \* 201 201 chccwdev -e 201 # Lsdasd - get

Re: Replacement the root disk with a larger disk (without LVM)

Csaba, Did you also run zipl? Op do 12 sep. 2019 om 17:14 schreef Csaba Polgar > Hello, > > We have many system with SLES 11 SP4, and would like to upgrade these to > SLES 12 SP4. > The the root filesystem (/, on dasd 201, with ext3, and without LVM, simple > dasd)

Re: Replacement the root disk with a larger disk (without LVM)

Just went through all this a while ago! Here's my instructions for my 101 -> 201 move 2. Enlarge the 101 disk if not already 1000 cyl (non LVM) # Allocate a 1000 cyl disk at address 201 vmcp link \* 201 201 chccwdev -e 201 # Lsdasd - get new disk letter dasdfmt -f /dev/dasd? -b 4

Replacement the root disk with a larger disk (without LVM)

Hello, We have many system with SLES 11 SP4, and would like to upgrade these to SLES 12 SP4. The the root filesystem (/, on dasd 201, with ext3, and without LVM, simple dasd) has the OS (itself the Linux, without the applications). But this root filesystem is too small for the upgrade. So, I did

Re: LVM Program Dinner at SHARE

Hi Rich, On Tue, 12 Mar 2019 12:01:18 -0700 Rich Smrcina wrote: > For those of you at SHARE in Phoenix. If wish to join us for the LVM program > dinner, please let me know either via email or here at SHARE face-to-face. > > We will be going to Steve’s Greenhouse Grill on Adams S

Re: LVM Program Dinner at SHARE

Wednesday. Sent from my iPhone > On Mar 12, 2019, at 12:50 PM, Rick Troth wrote: > >> On 3/12/19 3:01 PM, Rich Smrcina wrote: >> For those of you at SHARE in Phoenix. If wish to join us for the LVM program >> dinner, please let me know either via email or here at SHARE

Re: LVM Program Dinner at SHARE

On 3/12/19 3:01 PM, Rich Smrcina wrote: > For those of you at SHARE in Phoenix. If wish to join us for the LVM program > dinner, please let me know either via email or here at SHARE face-to-face. > > We will be going to Steve’s Greenhouse Grill on Adams Street a half a block >

LVM Program Dinner at SHARE

For those of you at SHARE in Phoenix. If wish to join us for the LVM program dinner, please let me know either via email or here at SHARE face-to-face. We will be going to Steve’s Greenhouse Grill on Adams Street a half a block from of the 2nd Street entrance to the convention center. Feel

Re: LVM root on Ubuntu

. Regards,Anderson Augusto Em segunda-feira, 24 de dezembro de 2018 11:26:04 BRST, Rinaldo escreveu: Hello! I have added a disk to '/' in lvm Ubuntu 18. I did the 'chzdev -e 152' , but I didn't run the command 'update-initramfs -u' before the ipl, so the machine is not recognizing the lvm

Re: LVM root on Ubuntu

to '/' in lvm Ubuntu 18. I did the 'chzdev -e 152' , but I didn't run the command 'update-initramfs -u' before the ipl, so the machine is not recognizing the lvm disk 152. Is it possible to do this command now? I tried, but it seems that the kernel loaded does not have this command. Best Regards

LVM root on Ubuntu

Hello! I have added a disk to '/' in lvm Ubuntu 18. I did the 'chzdev -e 152' , but I didn't run the command 'update-initramfs -u' before the ipl, so the machine is not recognizing the lvm disk 152. Is it possible to do this command now? I tried, but it seems that the kernel loaded does

Re: LVM volume size

On 23.04.2018 19:41, Mariusz Walczak wrote: > The below email is classified: Internal > > Hello group, > > Recently we had a DASD failure and I had to delete and recreate logical > volume in LVM. We had two model-9 DASDs defined as two logical volumes > (different v

Re: Expanding a zLinux non-LVM disk

I take that back something went wrong and the partition wasn’t resized after all. No worries. Cheers On Wed, Apr 25, 2018 at 13:32 Donald Russell wrote: > Thanks Stefan, > That all worked like a charm except I can’t seem to get the file system > expanded. > > I got

Re: Expanding a zLinux non-LVM disk

Thanks Stefan, That all worked like a charm except I can’t seem to get the file system expanded. I got everything copied, deleted and created a new larger partition with the same starting track. The file system is ccs so I booted up the new disk and thought xfs_growfs would do the trick. I’m

Re: Expanding a zLinux non-LVM disk

On 25.04.2018 05:48, Donald Russell wrote: I have a RHEL 7 zLinux on a single Mod-9 ECKD DASD. there are three partitions: 1 - /boot 2 - swap 3 - / From one Linux system I tried attaching a not-in-use zLinux Mod-9 and a Mod-27 and using fdasd and dd to copy the partitions. That didn’t work,

Re: Expanding a zLinux non-LVM disk

I think you need to use fdisk to extend the partition: https://access.redhat.com/articles/1190213 and then resize2fs or the appropriate filesystem resize command as stated in the article... Scott Rohling On Tue, Apr 24, 2018 at 8:48 PM, Donald Russell wrote: > I

Expanding a zLinux non-LVM disk

I have a RHEL 7 zLinux on a single Mod-9 ECKD DASD. there are three partitions: 1 - /boot 2 - swap 3 - / >From one Linux system I tried attaching a not-in-use zLinux Mod-9 and a Mod-27 and using fdasd and dd to copy the partitions. That didn’t work, then I tried a VM DDR of the Mod-9 to

LVM volume size

The below email is classified: Internal Hello group, Recently we had a DASD failure and I had to delete and recreate logical volume in LVM. We had two model-9 DASDs defined as two logical volumes (different volume groups). I used lvcreate -l 1760 to make sure the number of extents

Re: Extended LVM - want to make sure changes are ready for next boot

e M On Fri, Mar 2, 2018 at 12:53 PM, Dave Myers <dave.my...@siriuscom.com> wrote: > This is a SLES12 question. > I extended an LVM and DID NOT run the dasd_configure command. > Extend is fine, but now I'm wondering if my changes will survive a boot ?? > > What does dasd_configur

Re: Extended LVM - want to make sure changes are ready for next boot

>>> On 3/2/2018 at 12:53 PM, Dave Myers <dave.my...@siriuscom.com> wrote: > This is a SLES12 question. > I extended an LVM and DID NOT run the dasd_configure command. > Extend is fine, but now I'm wondering if my changes will survive a boot ?? > > What does dasd_co

Re: Extended LVM - want to make sure changes are ready for next boot

Sent: Friday, March 2, 2018 9:54 AM To: LINUX-390@VM.MARIST.EDU Subject: [LINUX-390] Extended LVM - want to make sure changes are ready for next boot This is a SLES12 question. I extended an LVM and DID NOT run the dasd_configure command. Extend is fine, but now I'm wondering if my changes

Extended LVM - want to make sure changes are ready for next boot

This is a SLES12 question. I extended an LVM and DID NOT run the dasd_configure command. Extend is fine, but now I'm wondering if my changes will survive a boot ?? What does dasd_configure do, and is it too late now to run that command to harden changes?? If so, how do I make sure my LVM extend

Re: SHARE LVM Dinner Wednesday August 9th

) -Original Message- From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Jagos, Brian Sent: Tuesday, August 01, 2017 10:54 AM To: LINUX-390@VM.MARIST.EDU Subject: SHARE LVM Dinner Wednesday August 9th [External Content] Please use caution. Hi All, If you

SHARE LVM Dinner Wednesday August 9th

Hi All, If you are attending SHARE in Providence Rhode Island and would like to attend the LVM Dinner please contact myself or any member of the LVM committee. Please RSVP before Tuesday 12 noon if you are going to attend. We are going to Bravo Brasserie. Below is the link

Re: SHARE LVM dinner and Velocity event in San Jose

re planning to attend SHARE in San Jose, please note the update to > the traditional LVM Program Dinner event. > > Greetings from the SHARE LVM Program volunteer team! > > It is a tradition at SHARE conferences to plan a trip to a local dining > establishment for the LVM Program Dinner

SHARE LVM dinner and Velocity event in San Jose

Last Chance... You must *respond today.* This is being posted to both IBMVM and LINUX-VM. If you are planning to attend SHARE in San Jose, please note the update to the traditional LVM Program Dinner event. Greetings from the SHARE LVM Program volunteer team! It is a tradition at SHARE

Re: Creating root LVM

Thanks for the feedback all! Sent from my iPhone > On Aug 25, 2016, at 10:34, Grzegorz Powiedziuk <gpowiedz...@gmail.com> wrote: > > We have lvroots on all our systems, in the past we had root without lvm and > honestly in both scenarios there always was a way to get to

Re: Creating root LVM

We have lvroots on all our systems, in the past we had root without lvm and honestly in both scenarios there always was a way to get to the data in case of problems of course if all devices were available. But it is always good to have unique vgnames (we do hostname_vgroot for example). LVM

Re: Creating root LVM

no matter what you prefer, your cloud tools won't handle your chosen file system layout unless you like one big vanilla / partition with ext3 and no lvm at all. On Tue, Aug 23, 2016, 13:26 Donald Russell <russell@gmail.com> wrote: > We have rhel5 with rootvg and rootlv. That caused us some g

Re: Creating root LVM

(upgrading to rehl7) we put the "basic Linux system" on a simple-to-use Mod-9 and use LVM for application file systems and a few others. Now it's very simple to mount that / file system on another server if necessary. On Tuesday, August 23, 2016, Michael Weiner <mwei...@infinite-b

Re: Creating root LVM

I don't know if that changed but it used to be that zipl could safely boot from LVM that was on only one physical volume. See this older discussion for details: http://www.mail-archive.com/linux-390%40vm.marist.edu/msg62491.html Tomas Tomas Pavelka CA Technologies Sr Software Engineer CA CZ

Re: Creating root LVM

years. When you get thrown into a rescue situation, the only tools you have available are in the root file system. If you can't get to them because LVM is bent then you have to resort to other means, with the attendant problems others have already discussed. > Or is it recommended to

Re: Creating root LVM

The experts also still debate this .. I myself see nothing wrong with root in an LVM - others shudder in horror. There are pros and cons to both approaches. For recovery - having a bootable LVM free Linux is a good thing so you can mount other guests VG disks without worry of duplicate

Re: Creating root LVM

Keep in mind that LVM's are unique to a Linux guest. If a volume is to be mounted in another system then it can't when an LVM with the same name already exists. Our cloning procedures want to mount a new system in our maintenance Linux guest. This means that the base system (at least /, /etc

Re: Creating root LVM

, the only time we use LVMs is for application data or log files in > directories such as /opt/was/, /oradata/logs/ or something like that. We > used to use an LVM for /var/ but found we didn't need it. > > We use about a 12 GB file system for Linux (/). If the users fill up > regu

Re: Creating root LVM

Michael, When you say 'root directory' I assume you mean / and not /root/. FWIW, the only time we use LVMs is for application data or log files in directories such as /opt/was/, /oradata/logs/ or something like that. We used to use an LVM for /var/ but found we didn't need it. We use about a 12

Re: Creating root LVM

Hi Michael, In our shop we use a normal directory to root, and create a VG for the expandable directories. We usually have VG for /usr and /opt. Our cloning scripts are happy with this setup, and we don't have much headache when we have to link the root mdisk to another machine to diagnostics.

Creating root LVM

Good morning all, I was having a little debate yesterday and I want to get the experts on this list opinions. What's the best practice when it comes to the root directory? Is it acceptable and recommend to create an vgroot and lvroot so it is expandable? Or is it recommended to have the

SHARE LVM TSC Survey reminder

not taken advantage of this opportunity, please point your browser to http://www.surveygizmo.com/s3/2853089/facaa86f1b27 and complete a survey there. Thank you, Rick Barlow SHARE LVM Program Manager -- For LINUX-390 subscribe / signoff

SHARE LVM TSC Survey

The SHARE Linux and VM Program Technical Steering Committee needs your input! Please point your browser to http://www.surveygizmo.com/s3/2853089/facaa86f1b27 and complete a short survey there. Romney Romney White Senior Technical Staff Member z Systems Architecture and

Re: LVM on unpartitioned disks (Was: RE: SLES12 + EDEV + bug)

into the new version anyway. Thanks for explaining the patch comment. Good to know it still works for LDL disks. Actually I had to get the lvm2 package from another SP3 source disk and installed it with rpm. We are now back on the SP3 base version and the LVM is mounted once again. Met vriendelijke

Re: LVM on unpartitioned disks (Was: RE: SLES12 + EDEV + bug)

lled. > > > Mark Post > > And if your system is already down and you can't recover from backup, then link volumes under a different sles machine, mount them and chroot into it and downgrade lvm as Mark said. That's how I've fixed

LVM on unpartitioned disks (Was: RE: SLES12 + EDEV + bug)

lumes will be supported, whether a partition was used (/dev/dasd?1) or not (/dev/dasd?). CDL formatted volumes will only be supported if a partition was used. > Today I have updated an SLES11 SP3 and I can't access the LVM anymore. This > is an LVM based on unpartitioned LDL formatted

LVM on unpartitioned disks (Was: RE: SLES12 + EDEV + bug)

46217)". Is the only for CDL disks and not for LDL disks? Today I have updated an SLES11 SP3 and I can't access the LVM anymore. This is an LVM based on unpartitioned LDL formatted disks. Met vriendelijke groet/With kind regards/Mit freundlichen Grüßen, Berry van Sleeuwen -Original Message

Re: Migrating LVM from LPAR (bare metal) SLES10 server to zVM Guest SLES11 server

On 04/25/2016 11:05 PM, Dave Myers wrote: > By "point and shoot"...do you mean I just need to copy the fstab entries over > to the new server and "mount -a" ?? Yes. If the same PVs are attached to the guest and are online, then the system will see them and by default activate the VG(s). You

Re: Migrating LVM from LPAR (bare metal) SLES10 server to zVM Guest SLES11 server

m.com<mailto:dave.my...@siriuscom.com> Sirius Computer Solutions | www.siriuscom.com<http://www.siriuscom.com/> 10100 Reunion Place, Suite 500, San Antonio, TX 78216 From: Dave Myers Sent: Monday, April 25, 2016 6:47 PM To: 'linux-390@VM.MARIST.EDU' <linux-390@VM.MARIST.EDU> Subjec

Re: Migrating LVM from LPAR (bare metal) SLES10 server to zVM Guest SLES11 server

And if you want zVM to take care of the disk label, you can dedicate the current dasds, add a new set of dasds to the vg, and use the pvmove (man pvmove) command to migrate data seamlessly from the old dasds to the new ones. We did this, in production, on the db2 servers, without taking anything

Re: Migrating LVM from LPAR (bare metal) SLES10 server to zVM Guest SLES11 server

If it's the same DASD, then you should not need vgexport/vgimport. Just point and shoot. The system will see the signatures on the disks and recognize the volume group. -- R; <>< On Apr 25, 2016 8:48 PM, "Dave Myers" wrote: I am migrating a server from LPAR SLES10

Migrating LVM from LPAR (bare metal) SLES10 server to zVM Guest SLES11 server

I am migrating a server from LPAR SLES10 (bare metal) to zVM Guest and a new SLES11 server. I need to migrate some existing LVMs. I know I need to DEDICATE the 3390s in the zVM USER DIRECT for the SLES11 guest and I think I need to maybe VGEXPORT and VGIMPORT ?? Can someone please give me some

Re: Debian install using LVM

run into this > issue. > I think we really should do stable release uploads in Debian of the fixes to have LVM working on jessie for the next point release. Because clearly there are users after it like yourself =) Regards, Dimitri. > Martha > > On Mon, 11 Apr 2016 17:25:05 -0600 Mar

Re: Debian install using LVM

McConaghy <u...@vm.marist.edu> wrote: >> I've been fighting with a Debian install all day and wonder if anyone else >> has run into the same problem. I wanted to use LVM for the root filesystem, >> so created a /boot partition and an LVM for the rest. Everything works fine >>

Re: Debian install using LVM

Thanks, Ray. I thought I was going crazy too! Martha On Mon, 11 Apr 2016 21:01:26 -0400 Ray Mansell said: >Martha... > >I've been fighting the same thing all afternoon. Thought I was going >bonkers, since it all worked so well last week. For the moment I've >installed without L

Re: Debian install using LVM

, Martha McConaghy <u...@vm.marist.edu> wrote: >>> I've been fighting with a Debian install all day and wonder if anyone else >>> has run into the same problem. I wanted to use LVM for the root filesystem, >>> so created a /boot partition and an LVM for the rest. Ever

Re: Debian install using LVM

On 12.04.2016 01:11, Dimitri John Ledkov wrote: > Hello, > > On 12 April 2016 at 00:00, Martha McConaghy <u...@vm.marist.edu> wrote: >> I've been fighting with a Debian install all day and wonder if anyone else >> has run into the same problem. I wanted to use LVM for

Re: Debian install using LVM

Martha... I've been fighting the same thing all afternoon. Thought I was going bonkers, since it all worked so well last week. For the moment I've installed without LVM, but there's certainly a problem. Ray On 4/11/2016 19:00, Martha McConaghy wrote: I've been fighting with a Debian install

Re: Debian install using LVM

>>> On 4/11/2016 at 07:00 PM, Martha McConaghy <u...@vm.marist.edu> wrote: > I've been fighting with a Debian install all day and wonder if anyone else > has run into the same problem. I wanted to use LVM for the root filesystem, > so created a /boot partition and an LVM f

Re: Debian install using LVM

Hello, On 12 April 2016 at 00:00, Martha McConaghy <u...@vm.marist.edu> wrote: > I've been fighting with a Debian install all day and wonder if anyone else > has run into the same problem. I wanted to use LVM for the root filesystem, > so created a /boot partition and an L

Debian install using LVM

I've been fighting with a Debian install all day and wonder if anyone else has run into the same problem. I wanted to use LVM for the root filesystem, so created a /boot partition and an LVM for the rest. Everything works fine until it comes to the step where it tries to write out ZIPL

Re: LVM usage

Actually, those were just examples. The Samba and TSM guests have the biggest LVM filesystems. We have a quite a few linux guests, most of them use LVM. Ranging from a small webserver to a couple of oracle database machines with LVM's up to 40G. I don’t think it matters if we are talking zVM

LVM usage - Thank you very much!

It was very valuable for me, thanks to all of you! WBR, Sergey -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit

Re: LVM usage

I would like also to mention that when it comes to LVM, it makes much more easier to manage such systems especially with FCP involved. Imagine that you break your multipath config for example and you lose your “mpath” names. If you have LVM, you can still boot. LVM will just scan all your paths

LVM usage

Hi All, Could you, please, explain me a real usage of the LVM in the server environments with z/VM or whatever. Do you really need to "online" expand your "opt" or "home" directory which is worth to have additional layer in disk access? Moreover, databases a

Re: LVM usage

please, explain me a real usage of the LVM in the server >environments with z/VM or whatever. >Do you really need to "online" expand your "opt" or "home" directory which >is worth to have additional layer in disk access? >Moreover, databases already have

Re: LVM usage

Two great responses from Bob and Berry. Here's my LVM story too. On 10/05/2015 08:56 AM, Sergey Korzhevsky wrote: > Could you, please, explain me a real usage of the LVM > in the server environments with z/VM or whatever. I was introduced to LVM by colleagues. Since then, I hav

Re: LVM usage

Hi Sergey, Our Samba server has a 180G filesystem on Model 9 DASD. It's obviously an LVM just to get to that size. Our TSM server has a 3.2TB staging filesystem, this guest has 72 model 54 disks to build the LVM filesystem. Striping within LVM can spread IO onto multiple disks. Databases

Re: LVM usage

es you are actually using LVM? Is this Websphere, databases, > Samba, log storage, custom application with a lot of data, anything else? Oh my personal systems, I use LVM for all filesystems except the boot volume. Once the system is up, the boot volume is out of the picture. (I maintain t

Re: LVM usage

We use LVM on EVERY server we build, for all of the disk, with the exception of /boot, and ASM disks for Oracle. Everything else is beneath LVM. Why? Because the users never estimate their space needs sufficiently, so there is always a need to add. Because disk subsystems seldom last the life

Re: LVM usage

Hi Rick, Could you tell me some details, because it is not obvious for what type of services you are actually using LVM? Is this Websphere, databases, Samba, log storage, custom application with a lot of data, anything else? Stories about TSM and Samba are great, but this is one installation

Re: LVM usage

My experience is that LVM is almost always used -- non-LVM is rarer on zLinux.DASD sizes have grown which help limit some needs for using LVM -- but the ability to be expanded dynamically is a pretty big sell point when the goal is 'no outage required' for most shops.. One exception

SHARE Orlando - LVM Program Dinner Invitation

Greetings from the SHARE LVM Program group! We would like to invite anyone who may be interested in meeting with us and learning more about the Linux and VM Program at SHARE to join us for dinner during the next SHARE conference, which is being held in Orlando, Florida. The dinner is scheduled

  1   2   3   4   5   6   7   8   9   10   >