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
dcopy(1M)																 dcopy(1M)

NAME
dcopy - copy HFS file system with compaction SYNOPSIS
fsize[source_fs destination_fs DESCRIPTION
The command copies an existing HFS file system (source_fs) to a new HFS file system (destination_fs), appropriately sized to hold the reor- ganized results. For best results, the source file system should be a raw device, and the destination file system should be a block device. Always run on unmounted file systems. (In the case of the root file system, copy it to a new minidisk.) If no options are specified, copies files from source_fs, compressing directories by removing vacant entries and spacing consecutive blocks in a file by the optimal rotational gap. If options such as or are specified, the destination file system structure will be different from that of the source file system. makes the destination file system identical to the source file system and preserves the pack and volume labels. Thus, to compress a file system without moving it, use to copy the files to another file system and the command to copy the file back (see dd(1)). Directory compression is accomplished by running on the primary copy of the file system and allowing the modified directories to propagate to the other copies of the file system in the normal manner. Options recognizes the following options: Move subdirectories to the beginning of directories. Specify the file system size (fsize) and inode-list size (isize) in blocks. If this option is not specified, the source file-system value is used. Specify the HFS file system type. The type of a file system can be determined with the command (see fstyp(1M)). See Supply device information for creating the best organization of blocks in a file. cyl is the number of block per cylinder; skip is the number of blocks to skip. Report size of source and destination file system. Echo the completed command line, but performs no other actions. The command line is generated by incorporating the user-specified options and other information derived from This option allows you to verify the command line. EXAMPLES
can be executed with or without options. If no options are specified as in this example, the source and destination file systems are iden- tical. Any differences between the two file systems lie only in the available disk space. If options are specified, expect a major difference between the source and destination file system structure: WARNINGS
produces invalid results if run on a mounted file system. The figures specified in option arguments cannot be smaller than corresponding figures in the source file system. DEPENDENCIES
only operates on HFS file systems. AUTHOR
was developed by HP. SEE ALSO
dd(1), fstyp(1M), disk(7). STANDARDS CONFORMANCE
dcopy(1M)
All times are GMT -4. The time now is 01:50 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy