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
OCF_HEARTBEAT_VIRTUA(7) 					OCF resource agents					   OCF_HEARTBEAT_VIRTUA(7)

NAME
ocf_heartbeat_VirtualDomain - Manages virtual domains through the libvirt virtualization framework SYNOPSIS
VirtualDomain [start | stop | status | monitor | migrate_to | migrate_from | meta-data | validate-all] DESCRIPTION
Resource agent for a virtual domain (a.k.a. domU, virtual machine, virtual environment etc., depending on context) managed by libvirtd. This resource agent may be configured for native migration if available in the cluster manager. For Pacemaker, the allow-migrate="true" meta attribute enables native migration. SUPPORTED PARAMETERS
config Absolute path to the libvirt configuration file, for this virtual domain. (unique, required, string, no default) hypervisor Hypervisor URI to connect to. See the libvirt documentation for details on supported URI formats. The default is system dependent. Determine the system's default uri by running 'virsh --quiet uri'. (optional, string, no default) force_stop Always forcefully shut down ("destroy") the domain on stop. The default behavior is to resort to a forceful shutdown only after a graceful shutdown attempt has failed. You should only set this to true if your virtual domain (or your virtualization backend) does not support graceful shutdown. (optional, boolean, default 0) migration_transport Transport used to connect to the remote hypervisor while migrating. Please refer to the libvirt documentation for details on transports available. If this parameter is omitted, the resource will use libvirt's default transport to connect to the remote hypervisor. (optional, string, no default) migration_network_suffix Use a dedicated migration network. The migration URI is composed by adding this parameters value to the end of the node name. If the node name happens to be an FQDN (as opposed to an unqualified host name), insert the suffix immediately prior to the first period (.) in the FQDN. At the moment Qemu/KVM and Xen migration via a dedicated network is supported. Note: Be sure this composed host name is locally resolveable and the associated IP is reachable through the favored network. (optional, string, no default) monitor_scripts To additionally monitor services within the virtual domain, add this parameter with a list of scripts to monitor. Note: when monitor scripts are used, the start and migrate_from operations will complete only when all monitor scripts have completed successfully. Be sure to set the timeout of these operations to accommodate this delay. (optional, string, no default) autoset_utilization_cpu If set true, the agent will detect the number of domainU's vCPUs from virsh, and put it into the CPU utilization of the resource when the monitor is executed. (optional, boolean, default true) autoset_utilization_hv_memory If set true, the agent will detect the number of *Max memory* from virsh, and put it into the hv_memory utilization of the resource when the monitor is executed. (optional, boolean, default true) migrateport This port will be used in the qemu migrateuri. If unset, the port will be a random highport. (optional, integer, no default) snapshot Path to the snapshot directory where the virtual machine image will be stored. When this parameter is set, the virtual machine's RAM state will be saved to a file in the snapshot directory when stopped. If on start a state file is present for the domain, the domain will be restored to the same state it was in right before it stopped last. This option is incompatible with the 'force_stop' option. (optional, string, no default) SUPPORTED ACTIONS
This resource agent supports the following actions (operations): start Starts the resource. Suggested minimum timeout: 90000. stop Stops the resource. Suggested minimum timeout: 90000. status Performs a status check. Suggested minimum timeout: 30. Suggested interval: 10. monitor Performs a detailed status check. Suggested minimum timeout: 30. Suggested interval: 10. migrate_from Executes steps necessary for migrating the resource away from the node. Suggested minimum timeout: 60. migrate_to Executes steps necessary for migrating the resource to the node. Suggested minimum timeout: 120. meta-data Retrieves resource agent metadata (internal use only). Suggested minimum timeout: 5. validate-all Performs a validation of the resource configuration. Suggested minimum timeout: 5. EXAMPLE
The following is an example configuration for a VirtualDomain resource using the crm(8) shell: primitive p_VirtualDomain ocf:heartbeat:VirtualDomain params config=string meta allow-migrate="true" op monitor depth="0" timeout="30" interval="10" SEE ALSO
http://www.linux-ha.org/wiki/VirtualDomain_(resource_agent) AUTHOR
Linux-HA contributors (see the resource agent source for information about individual authors) resource-agents UNKNOWN 06/09/2014 OCF_HEARTBEAT_VIRTUA(7)
All times are GMT -4. The time now is 10:47 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy