line 163 is the tar command - but here ya go.

#1

vadnais:/etc # cat create_system | sed -e '160,165 !d'
echo "copying single disk clone to target dasd"
cd /
tar -clpSf - . | (cd /mnt ; tar -xpSf - )
echo "Copy complete"

echo "Chroot to /mnt and run mkinitrd and zipl!"

and #2

vadnais:/etc # cat -evT create_system | sed -e '160,165 !d'
echo "copying single disk clone to target dasd"$
cd /$
tar -clpSf - . | (cd /mnt ; tar -xpSf - )$
echo "Copy complete"$
$
echo "Chroot to /mnt and run mkinitrd and zipl!"$
vadnais:/etc #





             "Post, Mark K"
             <[EMAIL PROTECTED]
             m>                                                         To
             Sent by: Linux on         LINUX-390@VM.MARIST.EDU
             390 Port                                                   cc
             <[EMAIL PROTECTED]
             IST.EDU>                                              Subject
                                       Re: Trying to move a file system
                                       recursively using tar
             10/20/2005 04:55
             PM


             Please respond to
             Linux on 390 Port
             <[EMAIL PROTECTED]
                 IST.EDU>






My experience has been that tar just keeps chugging unless it can't read
something from the archive itself.  You're not seeing that, just getting
informational messages.  I would bet you that it finished, after doing
as well as it could.

The hard link errors are because you're copying a file (with a hard
link) onto two separate file systems.  Hard links cannot go across file
systems, only soft links.  Since /usr is frequently a mounted file
system, separate from /etc in the root file system, I'm surprised that
those links to the time zone are hard ones, not soft ones.  You should
be able to recreate the links easily enough after you get the new system
up.

I'd like to see line 163 of the create_system script:
cat create_system | sed -e '160,165 !d'
cat -evT create_system | sed -e '160,165 !d'


Mark Post

-----Original Message-----
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of
James Melin
Sent: Thursday, October 20, 2005 5:46 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Trying to move a file system recursively using tar


Is there a limit to how many 'errors' tar will accept in a copy
operation and if so can it be overridden?

I am copying a single disk system to a 'broken out' multiple HFS
structure
via:

cd /
tar -clpSf - . | (cd /mnt ; tar -xpSf - )

the mounted file systems:  (percentage use is after copy)

/dev/dasdb1            2125924   1926936     90996  96% /
tmpfs                   510532         0    510532   0% /dev/shm
/dev/dasdc1             209120    141744     56584  72% /mnt
/dev/dasdd1              52200      8948     40560  19% /mnt/boot
/dev/dasde1              34764       460     32512   2% /mnt/root
/dev/dasdf1             191680     90384     91404  50% /mnt/home
/dev/dasdk1             418344     65280    331472  17% /mnt/var
/dev/dasdi1             850292        20    807080   1% /tmp
/dev/dasda1             850292        20    807080   1% /mnt/work
/dev/dasdg1            2763768    141052   2482324   6% /mnt/opt
/dev/dasdj1            2976336   1446328   1378816  52% /mnt/usr
/dev/dasdh1             237720         4    225448   1%
/mnt/opt/IBM/WebSphere


Mostly I get socket errors. I've been told in the past that those are
not anything I should worry about, but the last few  'Cannot hard link'
errors and then the unrevealing last message are strange. The copy
failed complaining:

./create_system: line 163: syntax error near unexpected token `)'
./create_system: line 163: `- )'

and the only occurrence of -) in the thing is in the tar command shown
above. The methodology I used to get here is shown in:
http://www.linuxvm.org/Info/HOWTOs/movefs.html  If anyone has any
advice/insight, I'd appreciate any input.

tar: ./dev/log: socket ignored
tar: ./var/lib/ntp/dev/log: socket ignored
tar: ./var/run/.resmgr_socket: socket ignored
tar: ./var/run/.nscd_socket: socket ignored
tar: ./var/spool/postfix/private/rewrite: socket ignored
tar: ./var/spool/postfix/private/bounce: socket ignored
tar: ./var/spool/postfix/private/defer: socket ignored
tar: ./var/spool/postfix/private/trace: socket ignored
tar: ./dev/log: socket ignored
tar: ./var/lib/ntp/dev/log: socket ignored
tar: ./var/run/.resmgr_socket: socket ignored
tar: ./var/run/.nscd_socket: socket ignored

----- snips 20 lines from example-----

tar: ./var/spool/postfix/public/cleanup: socket ignored
tar: ./var/spool/postfix/public/flush: socket ignored
tar: ./var/spool/postfix/public/showq: socket ignored
tar: ./usr/share/zoneinfo/America/Chicago: Cannot hard link to
`./etc/localtime': No such file or directory
tar: ./usr/share/zoneinfo/SystemV/CST6CDT: Cannot hard link to
`./etc/localtime': No such file or directory
tar: ./usr/share/zoneinfo/US/Central: Cannot hard link to
`./etc/localtime': No such file or directory
tar: ./usr/share/zoneinfo/CST6CDT: Cannot hard link to
`./etc/localtime': No such file or directory
tar: Error exit delayed from previous errors

----------------------------------------------------------------------
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 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

Reply via email to