First, I'd like to thank everyone who responded. Following the instructions on linuxvm.org Moving Part of A File System page, I was able to successfully copy two of the 3390-1 volumes to mini-disks, and they work. No fuss, no muss. These were not root file systems, the original volumes were mounted on the root, and I was able to re-boot the system with the new volumes without any problems after I updated the directory.
Now though I'm trying to copy a volume that contains a Suse 9 (31 bit) root file system, along with all the other directories that are in root. I took the system down, attached the volume to a Suse 10 system, didn't like the results, so unmounted it and remounted the volume on a Suse 9 64 bit system. I also attached and mounted the new 3390-9. Then I carefully typed in the tar command, which seemed to work for the most part, and seemed to copy everything much faster than I expected. I did get 24 messages that I wasn't expecting similar to the following: tar: ./var/run/.resmgr_socket: socket ignored tar: ./var/spool/postfix/private/rewrite: socket ignored tar: ./var/spool/postfix/private/bounce: socket ignored All the messages except 1 were in either /var/spool/postfix/private or /var/spool/postfix/public, and every single one said "socket ignored". Can someone shed some light on this for me please? I have no idea what it means, or if it's something I need to worry about. The end of the diff listing has a bunch of "Only in /mnt/old" messages that, without matching one for one, look like they match the files named in each of the socket ignorred messages. Then I issued a diff command, and the screen filled with a boatload of messages saying that /mnt/old/dev/filename is a character (or block) special file followed by the same message for /mnt/new/dev/same_filename. I also got "No such file or directory" messages for 9 or 10 sets of files - similar to: /mnt/old/lib/modules/2.6.5-7.97-s390/build /mnt/new/lib/modules/2.6.5-7.97-s390/build /mnt/old/lib/modules/2.6.5-7.97-s390/source /mnt/new/lib/modules/2.6.5-7.97-s390/source followed by the same message for several of the sub directories in /usr. Any ideas on the best way to move a 3390-3 to a 3390-9? Do I need to tar/copy each directory separately instead of doing the whole volume in one command? Do I need to issue the tar/copy command from the system that I'm trying to move while it's running? I think some of these problems may have something to do with aliases, but I don't know enough to know if that's the case. Additional info - The mod3 is/was dedicated and data starts at cyl 0, the mod9 is defined with a mini-disk that starts at cyl 1, and uses about 3/4 of the pack. df for the mod3 - suse9:~ # df df Filesystem 1K-blocks Used Available Use% Mounted on /dev/dasda1 2126644 989080 1029536 50% / tmpfs 61872 0 61872 0% /dev/shm suse9:~ # df for both old and new volumes (after copy) when mounted on suse9a system suse9a:/mnt # df df Filesystem 1K-blocks Used Available Use% Mounted on /dev/dasda1 2339260 2171456 48976 98% / tmpfs 124696 4 124692 1% /dev/shm /dev/dasdn1 2126644 989128 1029488 50% /mnt/old <== old vol /dev/dasdo1 6578448 989040 5255240 16% /mnt/new <== new vol suse9a:/mnt # Sue Sivets ---------------------------------------------------------------------- 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
