Sponsored Content
Top Forums Shell Programming and Scripting UNIX file system to Linux file system migration Post 302805821 by jlliagre on Saturday 11th of May 2013 10:56:30 AM
Old 05-11-2013
It would help if you tell what file systems are used on the source and destination machines, what Unix OS is used, and what method you plan to use to perform the copy.

In any case, "du" is the wrong tool to check the proper copy.

If you really want to make sure all the files are copied without any corruption, create a hash/checksum of every file on the source side and use it to check it is correct on the destination one for each file.

You would also need to make sure all (empty) directories are created and possibly decide what to do with files taht are neither plain files nor directories.

Finally, you might also want to check the permissions, owner/group, extended attributes and ACLs if any.
 

8 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

How do I send a file as an attachment (gzip file) on a Unix system

Hi, How do I send a file as an attachment (gzip file) on a Unix system ? Using sendmail. Please help me. :confused: (3 Replies)
Discussion started by: lacca
3 Replies

2. UNIX for Dummies Questions & Answers

how to mount a file system of a remote machine to local file system

Hi friends, In my case, there are serveral PCs running Linux in a LAN. I would like to to mount the directory /A_river of machine-A to the file system of another machine machine-B so that I can access files in that directory. I do not know how to do this. The situation is complicated by... (2 Replies)
Discussion started by: cy163
2 Replies

3. Programming

compare XML/flat file with UNIX file system structure

Before i start doing something, I wanted to know whether the approach to compare XML file with UNIX file system structure. I have a pre-configured file(contains a list of paths to executables) and i need to check against the UNIX directory structure. what are the various approches should i use ? I... (6 Replies)
Discussion started by: shafi2all
6 Replies

4. SCO

file system not getting mounted in read write mode after system power failure

After System power get failed File system is not getting mounted in read- write mode (1 Reply)
Discussion started by: gtkpmbpl
1 Replies

5. Programming

Linux file system insight

I have a basic knowledge of the various structures like file, dentry, inode, superblocks of linux virtual file systems. I want to get a more deep insight as to how these structures are utilized in reality. I mean I want to get an understanding of how and where these structure come up in picture... (4 Replies)
Discussion started by: rupeshkp728
4 Replies

6. Infrastructure Monitoring

Nagios: How to read the Linux system file?

hi 2 all i installed nagios in my linux srvr . check_ftp file is in format of system format . i wants to see the syntax for that script how can i read that file .. ??? please help me ! (4 Replies)
Discussion started by: ponmuthu
4 Replies

7. Shell Programming and Scripting

File name on linux system

Hi, One of the customer wants to receive the file with name //CEC821.K003GUK.DOMD(+1) on their linux system. I am using Java application to send the file to remote system, but I am not able to send the file with that name ane even i am not able to create the file with that name on linux system. ... (6 Replies)
Discussion started by: Satyak
6 Replies

8. HP-UX

how to mount a file system from a solaris server into an hp-ux system

Hi all I wonder if its possible to mount on a hp-ux server a file system that was previously mounted on a solaris 10 server. The LUN is on NetApp stoarge. The problem on hp-ux I cannot do pvcreate on the lun (disk) because contains data. Any help will be appreciated FR (2 Replies)
Discussion started by: fretagi
2 Replies
AFS-UP(1)						       AFS Command Reference							 AFS-UP(1)

NAME
up - Recursively copy directories, preserving AFS metadata SYNOPSIS
up [-v] [-1] [-f] [-r] [-x] [-m] <source directory> <destination directory> DESCRIPTION
The up command recursively copies the files and subdirectories in a specified source directory to a specified destination directory. The command interpreter changes the destination directory and the files and subdirectories in it in the following ways: o It copies the source directory's access control list (ACL) to the destination directory and its subdirectories, overwriting any existing ACLs. o If the issuer is logged on as the local superuser root and has AFS tokens as a member of the group system:administrators, then the source directory's owner (as reported by the "ls -ld" command) becomes the owner of the destination directory and all files and subdirectories in it. Otherwise, the issuer's user name is recorded as the owner. o If a file or directory exists in both the source and destination directories, the source version overwrites the destination version. The overwrite operation fails if the first (user) "w" (write) mode bit is turned off on the version in the destination directory, unless the -f flag is provided. o The modification timestamp on a file (as displayed by the "ls -l" command) in the source directory overwrites the timestamp on a file of the same name in the destination directory, but the timestamp on an existing subdirectory in the destination directory remains unchanged. If the command creates a new subdirectory in the destination directory, the new subdirectory's timestamp is set to the time of the copy operation, rather than to the timestamp that the subdirectory has in the source directory. The up command is idempotent, meaning that if its execution is interrupted by a network, server machine, or process outage, then a subsequent reissue of the same command continues from the interruption point, rather than starting over at the beginning. This saves time and reduces network traffic in comparison to the UNIX commands that provide similar functionality. The up command returns a status code of 0 (zero) only if it succeeds. Otherwise, it returns a status code of 1 (one). This command does not use the syntax conventions of the AFS command suites. Provide the command name and all option names in full. OPTIONS
-v Prints a detailed trace to the standard output stream as the command runs. -1 Copies only the files in the top level source directory to the destination directory, rather than copying recursively through subdirectories. The source directory's ACL still overwrites the destination directory's. (This is the number one, not the letter "l".) -f Overwrites existing directories, subdirectories, and files even if the first (user) "w" (write) mode bit is turned off on the version in the destination directory. -m Recognize and copy mount points rather than traversing the volumes they reference during the recursive copy operation. Without -m, up's default behavior is to copy the contents of all volumes and subvolumes mounted under the source directory into the volume containing the destination directory. -r Creates a backup copy of all files overwritten in the destination directory and its subdirectories, by adding a ".old" extension to each filename. -x Sets the modification timestamp on each file to the time of the copying operation. source directory Names the directory to copy recursively. destination directory Names the directory to which to copy. It does not have to exist already. EXAMPLES
The following command copies the contents of the directory dir1 to directory dir2: % up dir1 dir2 PRIVILEGE REQUIRED
The issuer must have the "a" (administer) permission on the ACL of both the source and destination directories. COPYRIGHT
IBM Corporation 2000. <http://www.ibm.com/> All Rights Reserved. This documentation is covered by the IBM Public License Version 1.0. It was converted from HTML to POD by software written by Chas Williams and Russ Allbery, based on work by Alf Wachsmann and Elizabeth Cassell. OpenAFS 2012-03-26 AFS-UP(1)
All times are GMT -4. The time now is 03:25 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy