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 <ramja...@yahoo.com> 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 /proc proc defaults 0 > 0 > sysfs /sys sysfs noauto 0 > 0 > debugfs /sys/kernel/debug debugfs noauto 0 > 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 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/
