I've still always had excellent luck with the following: cp -avx / /new
This will copy (a)rchive, (v)erbose, (x) one filesystem from / to /new. Preserves all permissions, symlinks, etc, and much easier than a tarball. Verbose being of course optional. Just my $0.02 on it. -m On Wed, Jan 02, 2002 at 01:12:01PM -0600, Keith Reynolds wrote: > Mark, > > I too need to move my Linux images to another volume. I am having a > problem with this command: > > tar -clpSf . | (cd /newmntpt ; tar -xpSf - ) > > I get - > tar: Cowardly refusing to create an empty archive > Try 'tar --help' for more information. > > I know I must be misplacing a space or something. Would you please > clearify this command for me? > > Thanks, > Keith > > > > > >>> [EMAIL PROTECTED] 12/11/01 08:55AM >>> > Andrew, > > How much work this requires depends on several things. If you can add > the > new DASD to the LPAR _before_ removing the old DASD, then it's pretty > straightforward. If you can't do that, then take a look at > http://www.marist.edu/htbin/wlvtype?LINUX-VM.21315. Sandy Gelbard > recently > needed to do the same thing, and had success with those instructions. > It > does require having OS/390 on another LPAR with access to the same DASD > volumes. (You might decide to use that process, regardless.) > > If you can have both sets of DASD online concurrently then > 1. Update your dasd= parameter with the new device numbers _after_ your > existing ones. > 2. Re-run silo. > 3. Re-IPL your Linux/390. > 4. Format your new DASD and run mke2fs on them. > 5. Create a mount point for the new root file system, and mount the > appropriate DASD volume on it. > 6. Create mount points on the new DASD for your other file systems, and > mount them on the new root file system. (Or just do step 7 to create > your > new mount points and then mount the volumes.) > 7. Copy your current root file system to the new volume: > cd / > tar -clpSf . | (cd /newmntpt ; tar -xpSf - ) > 8. Repeat for all your other file systems, such as /usr: > cd /usr > tar -clpSf . | (cd /newmntpt/usr ; tar -xpSf - ) > 9. Update your boot parameters for the new volume: > cd /mnt/boot (or /mnt/etc/ if you use silo.conf) > vi parmfile or silo.conf - remove all the _current_ device > numbers > so only the new device numbers are left. > 10. Re-run silo - make sure the output looks right. > 11. Shutdown Linux/390 and reboot from the new IPL volume. > > Mark Post > > -----Original Message----- > From: Davis, Andrew Phillip (SWD) > [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, December 11, 2001 4:45 AM > To: [EMAIL PROTECTED] > Subject: Moving Linux DASD > > > We have SuSe linux running on S/390 in an LPAR and all was well until > the > hardware team purchased new DASD and de-creed that we need to move from > our > existing UCBs to new devices. > > /proc/dasd/devices currently shows: > > 10A8(ECKD) at (94:0) is dasda:active at blocksize: 4096, 601020 > blocks, > 2347 MB > 10A9(ECKD) at (94:4) is dasdb:active at blocksize: 4096, 601020 > blocks, > 2347 MB > 10AA(ECKD) at (94:8) is dasdc:active at blocksize: 4096, 601020 > blocks, > 2347 MB > > /boot/parmfile shows: > > dasd=10A8,10A9,10AA root=/dev/dasdb1 noinitrd > > The UCB addresses 10A8, 10A9 and 10AA need to be replaced with 2B47, > 2B48 > and 2B49. > > Is it a simple case of editing the boot/parmfile ? Or is there more ? > > Many thanks > > > Andrew Davis > > > > > > Important: > > Internet communications are not necessarily secure and may be > intercepted or > changed after they are sent. > The Abbey National Group does not accept liability for any such changes. > If > you wish to confirm the origin or content of this communication, please > contact the sender using an alternative means of communication. > > This communication does not create or modify any contract. > > If you are not the intended recipient of this communication you should > destroy it without copying, disclosing or otherwise using its contents. > Please notify the sender immediately of the error. > > The Abbey National Group comprises Abbey National plc and its subsidiary > group of companies. > > Abbey National plc. Registered Office: Abbey National House, 2 Triton > Square, Regents Place, London, NW1 3AN. Reg. No. 2294747. > Registered in England. > > > > NOTE: This e-mail message may contain information that may be privileged, > confidential, and exempt from disclosure. It is intended for use only by > the person to whom it is addressed. If you have received this message in > error, please do not forward or use this information in any way, delete it > immediately, and contact the sender as soon as possible by the reply option > or by telephone at the telephone number listed (if available). Thank you. -- Michael Kershaw [EMAIL PROTECTED] Linux Systems Programmer, Information Technology "Don't worry, I'm sure they'll listen to Reason." -- Fisheye, Snowcrash