Welcome to Linux Knowledge Base and Tutorial
"The place where you learn linux"

 Create an AccountHome | Submit News | Your Account  

Tutorial Menu
Linux Tutorial Home
Table of Contents

· Introduction to Operating Systems
· Linux Basics
· Working with the System
· Shells and Utilities
· Editing Files
· Basic Administration
· The Operating System
· The X Windowing System
· The Computer Itself
· Networking
· System Monitoring
· Solving Problems
· Security
· Installing and Upgrading
· Linux and Windows

Man Pages
Linux Topics
Test Your Knowledge

Site Menu
Site Map
Copyright Info
Terms of Use
Privacy Info
Masthead / Impressum
Your Account

Private Messages

News Archive
Submit News
User Articles
Web Links


The Web

Who's Online
There are currently, 70 guest(s) and 0 member(s) that are online.

You are an Anonymous user. You can register for free by clicking here




       xfs_copy [ -bd ] [ -L log ] source target1 [ target2 target3 ... ]


       xfs_copy  copies  an XFS filesystem to one or more targets
       in parallel (see xfs(5)).   The  first  (source)  argument
       must  be the pathname of the device or file containing the
       XFS filesystem.  The remaining arguments  specify  one  or
       more target devices or file names.  If the pathnames spec­
       ify devices, a copy of the source XFS filesystem  is  cre­
       ated on each device.  The target can also be the name of a
       regular file, in which case an image  of  the  source  XFS
       filesystem  is created in that file.  If the file does not
       exist, xfs_copy creates  the  file.   The  length  of  the
       resulting file is equal to the size of the source filesys­
       tem.  However, if the file is created on an  XFS  filesys­
       tem,  the  file consumes roughly the amount of space actu­
       ally used in the source filesystem by the  filesystem  and
       the  XFS  log.  The space saving is because xfs_copy seeks
       over free blocks instead  of  copying  them  and  the  XFS
       filesystem supports sparse files efficiently.

       xfs_copy  should  only  be used to copy unmounted filesys­
       tems, read-only mounted filesystems, or frozen filesystems
       (see  xfs_freeze(8)).   Otherwise,  the generated filesys­
       tem(s) would be inconsistent or corrupt.

       xfs_copy does not alter the source filesystem in any  way.
       Each  new (target) filesystem is identical to the original
       filesystem except that new filesystems  each  have  a  new
       unique  filesystem  identifier (UUID).  Therefore, if both
       the old and new filesystems will be used as separate  dis­
       tinct  filesystems,  xfs_copy or xfsdump/xfsrestore should
       be used to generate the new filesystem(s) instead of dd(1)
       or other programs that do block-by-block disk copying.

       The  -d  (duplicate) option can be used if a true clone is
       desired.  This should be done only if the  new  filesystem
       will  be used as a replacement for the original filesystem
       (such as in the case of disk replacement).

       xfs_copy uses synchronous  writes  to  ensure  that  write
       errors are detected.

       The  -b  (buffered) option can be used to ensure direct IO
       is not attempted to any of the target files.  This is use­
       ful  when  the filesystem holding the target file does not
       support direct IO.  xfs_copy also uses pthreadss  to  per­
       form  simultaneous  parallel writes.  xfs_copy creates one
       additional thread for each  target  to  be  written.   All
       threads die if xfs_copy terminates or aborts.

       If  all  targets abort or if there is an error reading the
       source filesystem, xfs_copy immediately aborts.

       xfs_copy returns an exit code of 0 if all targets are suc­
       cessfully  copied  and  an  exit  code  of 1 if any target


       When moving filesystems from one disk to another,  if  the
       original  filesystem is significantly smaller than the new
       filesystem, and will be made  larger,  we  recommend  that
       mkfs  and  xfsdump/xfsrestore  be  used  instead  of using
       xfs_copy and xfs_growfs.  The filesystem layout  resulting
       from using xfs_copy/xfs_growfs is almost always worse than
       the result of using  mkfs/xfsdump/xfsrestore  but  in  the
       case of small filesystems, the differences can have a sig­
       nificant performance impact.   This  is  due  to  the  way
       xfs_growfs  works,  and  not  due  to  any  shortcoming in
       xfs_copy itself.


       mkfs.xfs(8),  xfsdump(8),  xfsrestore(8),   xfs_freeze(8),
       xfs_growfs(8), xfs(5).

Show your Support for the Linux Tutorial

Purchase one of the products from our new online shop. For each product you purchase, the Linux Tutorial gets a portion of the proceeds to help keep us going.



Security Code
Security Code
Type Security Code

Don't have an account yet? You can create one. As a registered user you have some advantages like theme manager, comments configuration and post comments with your name.

Help if you can!

Amazon Wish List

Did You Know?
The Linux Tutorial welcomes your suggestions and ideas.


Tell a Friend About Us

Bookmark and Share

Web site powered by PHP-Nuke

Is this information useful? At the very least you can help by spreading the word to your favorite newsgroups, mailing lists and forums.
All logos and trademarks in this site are property of their respective owner. The comments are property of their posters. Articles are the property of their respective owners. Unless otherwise stated in the body of the article, article content (C) 1994-2013 by James Mohr. All rights reserved. The stylized page/paper, as well as the terms "The Linux Tutorial", "The Linux Server Tutorial", "The Linux Knowledge Base and Tutorial" and "The place where you learn Linux" are service marks of James Mohr. All rights reserved.
The Linux Knowledge Base and Tutorial may contain links to sites on the Internet, which are owned and operated by third parties. The Linux Tutorial is not responsible for the content of any such third-party site. By viewing/utilizing this web site, you have agreed to our disclaimer, terms of use and privacy policy. Use of automated download software ("harvesters") such as wget, httrack, etc. causes the site to quickly exceed its bandwidth limitation and are therefore expressly prohibited. For more details on this, take a look here

PHP-Nuke Copyright © 2004 by Francisco Burzi. This is free software, and you may redistribute it under the GPL. PHP-Nuke comes with absolutely no warranty, for details, see the license.
Page Generation: 0.12 Seconds