On 6/26/20 9:54 AM, Davis, Larry (National VM Capability) wrote: > I am trying to move a Linux root (/) file system to a larger disk format
I'm not sure what you mean by "a larger disk format" because: > I was able to block copy the data from one device to the other using the DD > command below > dd if=/dev/dasdb1 of=/dev/dasdd1 bs=64K conv=noerror,sync This shows that you just copied an existing partition to a new partition, not an entire disk, and you didn't talk about resizing the file system on it, or how you avoided file system changes being missed on the, presumably active, source file system. > But I need to make the new Device Bootable and normally I would use FDISK on > a normal Linux system but FDASD does not have this function > > Is that the process of ZIPL? > Am I just missing something in my process, or if someone has the steps and > would like to share that would be great Yes, you would use zipl to write out the bootloader, kernel, and initrd. But, you need to make sure it writes things to the new disk, assuming that /boot is part of your root file system. If it's not part of / then you shouldn't have to do anything with this. Is the reason you're doing this because everything is lumped into one large file system, and things like /usr, /tmp, etc., are all in it? If so, then there's a "how to" on linuxvm.org that talks about how you can split off things into separate file systems without having to move / around. Mark Post ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO LINUX-390 or visit http://www2.marist.edu/htbin/wlvindex?LINUX-390
