Re: yast and rpm are broken
English is OK. I say update and upgrade to be the same. Yes, this is to be SLES12 upgrade. Was doing updates though in Yast. Kept getting dependency errors on some packages at the same time disks were filling up. So it looked like yast began removing packages. If this is large problem, what can be done about it? Thank you very much! Andrew Westerfield Systems Specialist MS Department of Information Technology Services 601-432-8082 | www.its.ms.gov DISCLAIMER: This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. If you are not the intended recipient you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited -Original Message- From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Mark Post Sent: Friday, November 3, 2017 5:41 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: yast and rpm are broken >>> On 11/3/2017 at 03:35 PM, Ram Jam wrote: > Hello, > I was updating a test mainframe server running SLES 11.3 and received > error that disks were filling up. > Not so concerned with the server I kep telling error OK, but apparntly > some packages like yast and rpm were deleted as result i keep getting > error when I command rpm -ql rpm-libs > > rpm: symbol lookup error: /usr/lib64/librpm.so.3: undefined symbol: > selinux_status_ close This is a much bigger problem than missing packages. SUSE didn't ship a version of RPM using that library naming convention until SLES12. Prior to that it would have been /usr/lib64/librpm-4.4.so or similar. If I had to guess, you were not just updating it, you were _upgrading_ it. Is that correct? Mark Post -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/ -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
Re: Expand root filesystem, SLES 11
Ram, I too have been working on copying the root filesystem to a larger volume. And, like you, followed The Cookbook by originally allocating 372MB for root. If you haven't figured it out yet, I'd like to offer some help and hopefully get you on the right path. You moved root to a larger volume, right? But you also need to move the logical volume data, as Mark said, on that same old root disk over to a larger (or equal sized) volume. You can either allocate a new minidisk OR you can use empty space on a unused disk partition (if large enough). Let's say you have a new volume /dev/dasdz and the old logical volume data is in volume group linux-vg on /dev/dasdy 1. Create a new physical volume from /dev/dasdz using the pvcreate command. 2. Extend volume group linux-vg using the vgextend command to add /dev/dasdz to the volume group. 3. Move the LV data from /dev/dasdy over to /dev/dasdz using the pvmove command. 4. Once you've moved the data over to the new volume, you can remove /dev/dasdy from volume group linux-vg. I hope this helps or even makes sense. If anyone sees anything wrong with this or has a better method, please let me know. This method has worked for me. Good luck! Andrew Westerfield Systems Specialist MS Department of Information Technology Services www.its.ms.gov -Original Message- From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Mark Post Sent: Wednesday, January 27, 2016 3:13 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: Expand root filesystem, SLES 11 >>> On 1/27/2016 at 10:56 AM, Ram Jam wrote: > My apologies Mark. Will remember to post more info next time. > Errors on the z/VM console are as follows when I boot up the Linux guest. > --Scanning for LVM volume > groups... Reading all > physicalvolumes. This may take a while... Found > duplicate PVEBdleGPWJNX77h8jgpTskuXHtMUWfWPx: using /dev/dasdc1 > not/dev/dasdb1 Couldn't find devicewith uuid > 'K6Ec0V-DClh-pFhp-vLAE-yWWf-ZH4u-GtVUIX'.Couldn't find devicewith > uuid 'ecXHA7-CLLe-g3iN-mEeE-ayxE-KUOn-xtpmFe'.Couldn't find > devicewith uuid 'ughcI9-ed8q-FQSX-GjJc-JVpn-yTBc-AP4fqK'.Couldn't > find devicewith uuid 'gDK29H-4fsY-afS8-ARWW-bzqG-KTjK-3Y0GmT'.Found OK, now we're getting somewhere. The problem isn't the duplicate UUIDs, it's the missing ones. Thinking about it, the Cookbook has you create a partition on the DASD volume containing the root file system to use for LVM. So, that means we have more work to do than just moving the one partition. We also need to move the contents of the PV to a new PV. The other problem is, just what happened to the other disks that are providing these UUIDS: K6Ec0V-DClh-pFhp-vLAE-yWWf-ZH4u-GtVUIX ecXHA7-CLLe-g3iN-mEeE-ayxE-KUOn-xtpmFe ughcI9-ed8q-FQSX-GjJc-JVpn-yTBc-AP4fqK gDK29H-4fsY-afS8-ARWW-bzqG-KTjK-3Y0GmT It looks like your non-root DASD volumes are not coming online. When you have your system booted with the old root device, what does cat /proc/dasd/devices show, and what does it show with the new root device? -snip- > Also, do you mind explaining in a little more detail, maybe provide an > example, of what my /etc/fstab should look like after Step 8 of your > procedures? > Mine looks like this: > /dev/disk/by-path/ccw-0.0.0100-part1 / ext3 acl,user_xattr > 1 1 > /dev/system-vg/opt-lv /opt ext3 acl,user_xattr > 1 2 > /dev/system-vg/tmp-lv /tmp ext3 acl,user_xattr > 1 2 > /dev/system-vg/usr-lv /usr ext3 acl,user_xattr > 1 2 > /dev/system-vg/var-lv /var ext3 acl,user_xattr > 1 2 > proc /procproc defaults 0 > 0 > sysfs/sys sysfs noauto0 > 0 > debugfs /sys/kernel/debugdebugfsnoauto0 > 0 > devpts /dev/pts devpts mode=0620,gid=5 0 > 0 That's how it should look both before and after. That's part of the beauty of VM. If you swap out hardware but keep the same virtual device address, a lot of things in the guest don't have to be changed. Mark Post -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/ DISCLAIMER: This email and any files transm
Re: zVM/Linux Upgrade
This is what I did. From the command prompt, I ftp to my z/VM system and sign in as maint. MAINT logged in; working directory = MAINT 191 Issue command > cd maint.2cc You can issue the 'LS' command here to view the contents of the working directory and see if USER.DIRECT is there. I use my H:\ for downloads, so issue some similar command > lcd H:\ Issue command > get USER.DIRECT userdirect.txt Andrew Westerfield Systems Specialist MS Department of Information Technology Services www.its.ms.gov -Original Message- From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Dazzo, Matt Sent: Wednesday, April 29, 2015 10:45 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: zVM/Linux Upgrade Is there a way to get a copy of the 'user direct' to my desk top? When I ftp to zvm I sign on with the maint id, that brings me to maint.191 disk. User direct is located on C1. As you can tell a newbie to vm here. Tks Matt -Original Message- From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Bruce Hayden Sent: Tuesday, April 14, 2015 3:35 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: zVM/Linux Upgrade Yes - your biggest problem is that RH 7.1 will not run (or even IPL) on a z10 (EC or BC). RH 6.6 will though. On Tue, Apr 14, 2015 at 3:17 PM, Dazzo, Matt wrote: > We currently have zvm v6.1 and RH Linux 5.5 on a z10bc-2098 up and > running, this is a sand box environment for now. But it's not staying > that way for long, there is a requirement coming to run a linux server > in production. I'd like to upgrade this environment before creating > any new production servers. Anyone know of any problems running zvm > 6.3 and RH 7.1 on our hardware? This is my first go around so any > pointers or helpful documentation would be appreciated. > > Thanks, > > Matt > > -- > For LINUX-390 subscribe / signoff / archive access instructions, send > email to lists...@vm.marist.edu with the message: INFO LINUX-390 or > visit > http://www.marist.edu/htbin/wlvindex?LINUX-390 > -- > For more information on Linux on System z, visit > http://wiki.linuxvm.org/ > -- Bruce Hayden z/VM and Linux on z Systems ATS IBM, Endicott, NY -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/ DISCLAIMER: This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. If you are not the intended recipient you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited.
Re: Unable to get device online
Matt, Who has ownership of the LN4F85 volume? Maint? System? According to your system config entry for all LN* volumes, the volume should belong to SYSTEM if you restarted z/VM. Whenever I've gotten your same error, it's usually because I've formatted the volume under maint and forgot to reattach it to the system. Did you "directxa" after editing the USER DIRECT file? Andrew www.its.ms.gov -Original Message- From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Dazzo, Matt Sent: Wednesday, March 11, 2015 2:29 PM To: LINUX-390@VM.MARIST.EDU Subject: Unable to get device online Seems to be the day for device issues on the forum. We are running RHEL 5.5 on zvm, I am trying to get a additional mdisk online to extend a vgroup. This is a mod-27, I did these same steps last week for a new vgroup and it worked fine. Would like to mention I am very new to linux and at a loss what to try next. Thanks Matt Steps taken so far in vm; cpfmtxa - that appeared to run fine. xedit user direct and added mdisk. MDISK 207 3390 0001 32759 LN4F85 MR READ WRITE MULTIPLE There is a generic entry on the vm system config file for all LN/ volumes. Restart zvm - I understand the user direct can be dynamically added but that did not work the last time I went to add a mdisk so I did a restart. linux Restart the linux server. chccwdev -e 0207 Then get Device 0.0.0207 not found. -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/ DISCLAIMER: This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. If you are not the intended recipient you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited. -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
Re: Adding Memory Question
Yep, there are options. If you want your intended server to have 4GB of memory, it's going to eat up most of the storage you have defined as central. Are you running any other servers in the same z/VM LPAR, and is the z/VM memory backed up with any page space? Before adding any memory to your intended server, s'good to make sure there's memory to give. Andrew Westerfield MS Department of Information Technology Services www.its.ms.gov -Original Message- From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Dazzo, Matt Sent: Tuesday, February 17, 2015 11:59 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: Adding Memory Question Yes I can shutdown the servers linux and or vm if need be. I looked on the HMC and the vm lpar is configured with central - 4608MB, Expanded - 1536MB. Do I have any options? tks Matt q stor STORAGE = 4608M CONFIGURED = 4608M INC = 128M STANDBY = 0 RESERVED = 0 Ready; T=0.01/0.01 12:54:31 -Original Message- From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Andrew Westerfield Sent: Tuesday, February 17, 2015 12:50 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: Adding Memory Question Hi Matt, Couple of questions. 1. You mention your servers were intended as a sandbox. Does this mean you can shut down the intended server? 2. Does your z/VM LPAR have real memory to give? The easiest way to add more memory would be to shutdown the intended server, add more memory to the server's USER DIRECTORY on z/VM, and restart the server. There is a way to dynamically add more memory to a running server if you can't shut down the server and memory had already been set aside prior. The command 'q stor' on your z/VM system will show how much memory the LPAR has defined. Good luck Andrew Westerfield MS Department of Information Technology Services www.its.ms.gov -Original Message- From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Dazzo, Matt Sent: Tuesday, February 17, 2015 11:28 AM To: LINUX-390@VM.MARIST.EDU Subject: Adding Memory Question We are running z/vm 6.0 with 2 RH 5.5 servers that was intended as a sand box for an application that never launched several years ago. We are now looking at testing an application that calls for 4GB memory to run. The intended server only has 1GB, pls see below. I am a newbie at best with vm / linux, what is the process to add 4GB of memory and how do I know if can? Thanks Matt [root@lnftp01 DB2_ESE]# free -m total used free sharedbuffers cached Mem: 10004365630 90 283 -/+ buffers/cache: 62 937 Swap: 2271 0 2271 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/ DISCLAIMER: This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. If you are not the intended recipient you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited. -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/ -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/ -- For LINUX-390 subscribe / signoff / archive acces
Re: Adding Memory Question
Hi Matt, Couple of questions. 1. You mention your servers were intended as a sandbox. Does this mean you can shut down the intended server? 2. Does your z/VM LPAR have real memory to give? The easiest way to add more memory would be to shutdown the intended server, add more memory to the server's USER DIRECTORY on z/VM, and restart the server. There is a way to dynamically add more memory to a running server if you can't shut down the server and memory had already been set aside prior. The command 'q stor' on your z/VM system will show how much memory the LPAR has defined. Good luck Andrew Westerfield MS Department of Information Technology Services www.its.ms.gov -Original Message- From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Dazzo, Matt Sent: Tuesday, February 17, 2015 11:28 AM To: LINUX-390@VM.MARIST.EDU Subject: Adding Memory Question We are running z/vm 6.0 with 2 RH 5.5 servers that was intended as a sand box for an application that never launched several years ago. We are now looking at testing an application that calls for 4GB memory to run. The intended server only has 1GB, pls see below. I am a newbie at best with vm / linux, what is the process to add 4GB of memory and how do I know if can? Thanks Matt [root@lnftp01 DB2_ESE]# free -m total used free sharedbuffers cached Mem: 10004365630 90 283 -/+ buffers/cache: 62 937 Swap: 2271 0 2271 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/ DISCLAIMER: This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. If you are not the intended recipient you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited. -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
