>>> On 8/19/2013 at 10:08 AM, Tom Huegel <[email protected]> wrote: > FEDORA 18 > > etc/fstab > # Created by anaconda on Tue Jan 22 07:01:13 2013 > # > # Accessible filesystems, by reference, are maintained under '/dev/disk' > # See man pages fstab(5), findfs(8), mount(8) and/or blkid(8) for more info > # > /dev/mapper/fedora_fedora-root / ext4 > defaults 1 1 > /dev/mapper/fedora_fedora-boot /boot ext4 > defaults 1 2 > /dev/disk/by-path/ccw-0.0.025f-part1 swap swap > defaults 0 0 > /dev/mapper/fedora_fedora-swap swap swap > defaults 0 0
OK, you're in luck. Your root file system (which is your only "real" file system) is on an LVM logical volume. You should have a chccwdev command to bring your new DASD volumes online. But, I'm not familiar with the Fedora process to make that persistent across reboots. It could be something in /etc/zipl.conf, or a udev rule somewhere. Don't add the new DASD volume to LVM until you're sure it will come back online after rebooting. If it doesn't, you won't be able to get your system up far enough to (easily) fix things. Once you're sure it's persistent, then most likely this will be /dev/dasdb. If so, then: 1. dasdfmt -b 4096 -p -y /dev/dasdb 2. fdasd -a /dev/dasdb 3. pvcreate /dev/dasdb1 4. vgextend fedora /dev/dasdb1 5. lvresize -L +??? /dev/fedora/root where ??? is the amount of space that "vgdisplay" says you now have available. 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 more information on Linux on System z, visit http://wiki.linuxvm.org/
