Migrating data - Revision history

Zcrayfish: Removed wikilink to an empty/RfD article.

2023-08-14T16:00:41Z

Removed wikilink to an empty/RfD article.

← Older revision		Revision as of 16:00, 14 August 2023
Line 3:		Line 3:
	We include information about some options that aren't available on the BusyBox implementation of these tools, because you may be copying data to/from systems with other Unix tools installed, which do provide those options.		We include information about some options that aren't available on the BusyBox implementation of these tools, because you may be copying data to/from systems with other Unix tools installed, which do provide those options.

	{{Warning\| None of the methods below will copy the ~~[[Partitioning and Bootmanagers\|~~bootmanager]] (ext/syslinux, grub, etc) to a new drive; you'll have to install it there explicitly.}}		{{Warning\| None of the methods below will copy the bootmanager (ext/syslinux, grub, etc) to a new drive; you'll have to install it there explicitly.}}

	== Bit-copying methods ==		== Bit-copying methods ==

Sertonix: use https links

2023-08-07T11:36:14Z

use https links

← Older revision		Revision as of 11:36, 7 August 2023
Line 15:		Line 15:
	{{Cmd\| dd bs{{=}}10M if{{=}}/dev/<var>sourcepart</var> of{{=}}/dev/<var>targetpart</var>}}		{{Cmd\| dd bs{{=}}10M if{{=}}/dev/<var>sourcepart</var> of{{=}}/dev/<var>targetpart</var>}}

	This also copies unoccupied blocks on the <var>sourcepart</var> to the <var>targetpart</var>. A more optimal variant is to use [~~http~~://www.partimage.org/Main_Page partimage], which copies only the used portions of the sourcepart. One limitation is that currently (v0.6.9, released July 2010, current as of Mar 2012) partimage doesn't support ext4 format.		This also copies unoccupied blocks on the <var>sourcepart</var> to the <var>targetpart</var>. A more optimal variant is to use [https://www.partimage.org/Main_Page partimage], which copies only the used portions of the sourcepart. One limitation is that currently (v0.6.9, released July 2010, current as of Mar 2012) partimage doesn't support ext4 format.

	{{Todo\| Generally the target partition will have same partition type (e.g., Linux 0x83) as the source; but is this strictly necessary?}}		{{Todo\| Generally the target partition will have same partition type (e.g., Linux 0x83) as the source; but is this strictly necessary?}}
Line 162:		Line 162:
	* the <code>-H newc</code> cpio format has max 1024 char filenames (though GNU cpio can handle arbitrary lengths) and max 4G filesize. The portable <code>-H ustar</code> tar format has max 256 char filenames and max 8G filesize limits		* the <code>-H newc</code> cpio format has max 1024 char filenames (though GNU cpio can handle arbitrary lengths) and max 4G filesize. The portable <code>-H ustar</code> tar format has max 256 char filenames and max 8G filesize limits
	* in some implementations, cpio wouldn't copy files over 2G properly. Don't have details about which implementations/versions are so limited		* in some implementations, cpio wouldn't copy files over 2G properly. Don't have details about which implementations/versions are so limited
	* <span id="tar_acl">some tar formats are supposed to handle acls, however [~~http~~://unix.stackexchange.com/q/391/4801 in practice this doesn't seem very reliable]. Not sure what the situation is with cpio. rsync is known to work well for such cases</span>		* <span id="tar_acl">some tar formats are supposed to handle acls, however [https://unix.stackexchange.com/q/391/4801 in practice this doesn't seem very reliable]. Not sure what the situation is with cpio. rsync is known to work well for such cases</span>

	<!-- Some more info: ~~http~~://www.suse.de/~aj/linux_lfs.html -->		<!-- Some more info: https://www.suse.de/~aj/linux_lfs.html -->


Line 219:		Line 219:
	* <code>-n</code> or <code>--dry-run</code>		* <code>-n</code> or <code>--dry-run</code>

	[~~http~~://rsync.samba.org/ftp/rsync/rsync.html rsync's full manpage]		[https://rsync.samba.org/ftp/rsync/rsync.html rsync's full manpage]

	rsync's advantages:		rsync's advantages:
Line 236:		Line 236:
	=== lvm ===		=== lvm ===

	"This is one reason I like LVM. Just add the new disk to the volume group, pvmove the logical volumes from the old to new disk, [wait a bit], remove the old disk from the volume group, and then from the system. If it's your boot disk you're replacing then you also need to update your boot loader." <!-- ~~http~~://superuser.com/a/11468/28187 -->		"This is one reason I like LVM. Just add the new disk to the volume group, pvmove the logical volumes from the old to new disk, [wait a bit], remove the old disk from the volume group, and then from the system. If it's your boot disk you're replacing then you also need to update your boot loader." <!-- https://superuser.com/a/11468/28187 -->

	See [[Setting up Logical Volumes with LVM]].		See [[Setting up Logical Volumes with LVM]].

Bt129 at 05:18, 5 July 2021

2021-07-05T05:18:08Z

← Older revision		Revision as of 05:18, 5 July 2021
Line 1:		Line 1:
	We compare several methods for copying/migrating large amounts of data. The aim is to preserve all file permissions and metadata, which ~~will require~~ root access on both source and target filesystems.		We compare several methods for copying/migrating large amounts of data. The aim is to preserve all file permissions and metadata, which requires root access on both source and target filesystems.

	We include information about some options that aren't available on BusyBox's implementation of these tools, because you may be copying data to/from systems with other Unix tools installed, which do provide those options.		We include information about some options that aren't available on the BusyBox implementation of these tools, because you may be copying data to/from systems with other Unix tools installed, which do provide those options.

	{{Warning\| None of the methods below will copy the [[Partitioning and Bootmanagers\|bootmanager]] (ext/syslinux, grub, etc) to a new drive; you'll have to install it there explicitly.}}		{{Warning\| None of the methods below will copy the [[Partitioning and Bootmanagers\|bootmanager]] (ext/syslinux, grub, etc) to a new drive; you'll have to install it there explicitly.}}
Line 24:		Line 24:
	== Higher-level methods ==		== Higher-level methods ==

	The other options we'll discuss ~~suppose that~~ the target filesystem is already formatted and mounted as {{Path\|/target}}.		The other options we'll discuss assume the target filesystem is already formatted and mounted as {{Path\|/target}}.

	If you~~'re proposing~~ to copy volatile data from a running system, you may want to copy from a lvm snapshot, or do the copy from single-user mode, or from a LiveCD or other boot medium so ~~that~~ your source data is ~~no longer~~ in use during the copy. If you~~'re just proposing~~ to copy from {{Path\|/home}} or such, no such precautions are necessary.		If you need to copy volatile data from a running system, you may want to copy from a lvm snapshot, or do the copy from single-user mode, or from a LiveCD or other boot medium so your source data is not in use during the copy. If you want to copy from {{Path\|/home}} or such, no such precautions are necessary.

	If you're copying a complete filesystem, you'll probably only want to copy the {{Path\|/sys}} and {{Path\|/proc}} mountpoints, but not their current contents. Remember to copy {{Path\|/boot}} and {{Path\|/dev}} and {{Path\|/tmp}}, the last two of which may require special attention. Pay attention to other mountpoints (such as {{Path\|/mnt}}, {{Path\|/media}}) and RAM-based filesystems (such as {{Path\|/run}} and {{Path\|/lib/rc/init.d}}).		If you're copying a complete filesystem, you'll probably only want to copy the {{Path\|/sys}} and {{Path\|/proc}} mountpoints, but not their current contents. Remember to copy {{Path\|/boot}} and {{Path\|/dev}} and {{Path\|/tmp}}, the last two of which may require special attention. Pay attention to other mountpoints (such as {{Path\|/mnt}}, {{Path\|/media}}) and RAM-based filesystems (such as {{Path\|/run}} and {{Path\|/lib/rc/init.d}}).

	{{Todo\|The preceding comments assume you know what you are doing, and only serve as reminders. Would be good to link to a fuller explanation.}}		{{Todo\|The preceding comments assume you know what you are doing, and only serve as reminders. Would be a good idea to link to a fuller explanation.}}

	{{Note\| /dev is tricky ~~nowadays~~ on some systems since it's hidden by udev. Here's a possible solution:		{{Note\| nowadays, /dev is tricky on some systems since it's hidden by udev. Here's a possible solution:
	{{Cmd\|mkdir /tmp/dev		{{Cmd\|mkdir /tmp/dev
	mount --move /dev /tmp/dev		mount --move /dev /tmp/dev
Line 42:		Line 42:

	=== cp ===		=== cp ===
	Depending on ~~what~~ system you're working with, and what kind of data you're copying, you ''may'' be able to do a satisfactory ''local'' copy using just <code>cp</code>. ~~But~~ there are a number of limits ~~here~~ that prevent this from being a general solution.		Depending on which system you're working with, and what kind of data you're copying, you ''may'' be able to do a satisfactory ''local'' copy using just <code>cp</code>. However, there are a number of limits that prevent this from being a general solution.

	The Gnu implementation of <code>cp</code> provides the following options (among others):		The Gnu implementation of <code>cp</code> provides the following options (among others):
Line 54:		Line 54:
	* <code>-x</code>, <code>--one-file-system</code>: skip subdirectories on different volumes		* <code>-x</code>, <code>--one-file-system</code>: skip subdirectories on different volumes

	The BusyBox version provides all of the ~~Gnu~~ options except <code>--sparse</code> ~~and~~ <code>-u</code> and <code>-x</code>, and may lack the <code>context</code> and <code>xattr</code> options to <code>--preserve</code>. It will preserve hard links: if {{Path\|/source/A}} and {{Path\|/source/B}} are hard links, {{Path\|/target/A}} and {{Path\|/target/B}} will also be hard links with each other (though not with the originals). BusyBox's <code>cp</code> seems to silently ignore the <code>-v</code> option.		The BusyBox version provides all of the GNU options except <code>--sparse</code>, <code>-u</code> and <code>-x</code>, and may lack the <code>context</code> and <code>xattr</code> options to <code>--preserve</code>. It will preserve hard links: if {{Path\|/source/A}} and {{Path\|/source/B}} are hard links, {{Path\|/target/A}} and {{Path\|/target/B}} will also be hard links with each other (though not with the originals). BusyBox's <code>cp</code> seems to silently ignore the <code>-v</code> option.

	The FreeBSD implementation provides all of these except <code>-s</code> ~~and~~ <code>--sparse</code> and <code>-u</code>, and the <code>--preserve</code> options from <code>links</code> on: in particular, it always copies hard links as separate files. The Mac version shares the limitations of the FreeBSD version, and additionally lacks <code>-x</code>. Also, on the Mac version the <code>-a</code> shortcut isn't available, you must explicitly say <code>-RPp</code>.		The FreeBSD implementation provides all of these except <code>-s</code>, <code>--sparse</code> and <code>-u</code>, and the <code>--preserve</code> options from <code>links</code> on: in particular, it always copies hard links as separate files. The Mac version shares the limitations of the FreeBSD version, and additionally lacks <code>-x</code>. Also, on the Mac version the <code>-a</code> shortcut isn't available, you must explicitly say <code>-RPp</code>.

	{{Note\| As just explained, some of these implementations will break hard links.}}		{{Note\| As just explained, some of these implementations will break hard links.}}
Line 110:		Line 110:
	</ul>		</ul>

	~~Gnu~~ options (~~also~~ Mac and FreeBSD unless noted) ~~also~~ include:		GNU options (Mac and FreeBSD as well, unless noted) include:

	* <code>--one-file-system</code>: when creating archive, stay on the volume(s) where the specified roots are located, and don't cross mountpoints		* <code>--one-file-system</code>: when creating archive, stay on the volume(s) where the specified roots are located, and don't cross mountpoints
Line 121:		Line 121:


	Some ~~Gnu~~ tar formats:		Some GNU tar formats:
	* in future, will default to <code>-H posix/pax</code>, which is the POSIX.1-2001 format		* in the future, it will default to <code>-H posix/pax</code>, which is the POSIX.1-2001 format
	* v.1.13 - current (v1.26 released Mar 2011, still current in Mar 2012): defaults to <code>-H gnu</code>, which is not very different from the <code>-H oldgnu</code> format.		* v.1.13 - current (v1.26 released Mar 2011, still current in Mar 2012): defaults to <code>-H gnu</code>, which is not very different from the <code>-H oldgnu</code> format.
	* <code>-H ustar</code> is the portable POSIX.1-1988 format, some limits including max 256 char filenames, max 8G filesize; supports special files, but not sparse files~~; also~~ seems not to support xattrs and ACLs (other tar formats are meant to handle ACLs, but see [[#tar_acl\|comments below]])		* <code>-H ustar</code> is the portable POSIX.1-1988 format, some limits including max 256 char filenames, max 8G filesize; supports special files, but not sparse files. Also seems not to support xattrs and ACLs (other tar formats are meant to handle ACLs, but see [[#tar_acl\|comments below]])


Line 147:		Line 147:
	=== cpio ===		=== cpio ===

	cpio operates in one of ~~these~~ four modes:		cpio operates in one of four modes:
	* <code>-o -H newc</code>: create archive on stdout (or <code>-F <var>archive</var></code>), including filenames supplied from stdin (like <code>tar -cf- -T-</code>)		* <code>-o -H newc</code>: create archive on stdout (or <code>-F <var>archive</var></code>), including filenames supplied from stdin (like <code>tar -cf- -T-</code>)
	: <code>-H newc</code>: (on Mac, <code>-H sv4cpio</code> and/or <code>-c</code>) specifies to use SVR4 ASCII format, this is required to create archives in BusyBox		: <code>-H newc</code>: (on Mac, <code>-H sv4cpio</code> and/or <code>-c</code>) specifies to use SVR4 ASCII format, this is required to create archives in BusyBox
Line 156:		Line 156:

	tar vs cpio:		tar vs cpio:
	* if you have includes/excludes, it's easier to use <code>find</code> than unfamiliar and non-portable options of ~~Gnu~~ tar		* if you have includes/excludes, it's easier to use <code>find</code> than the unfamiliar and non-portable options of GNU tar
	* cpio handles special files (block and char devices, fifos, etc); traditional tar (<code>-H v7</code> format) didn't, also didn't store symbolic owner/group		* cpio handles special files (block and char devices, fifos, etc) traditional tar (<code>-H v7</code> format) didn't, also didn't store symbolic owner/group
	* when extracting hard links, tar must always include the first		* when extracting hard links, tar must always include the first
	* tar and the <code>-H newc</code> cpio format handle 32-bit inodes; though some older cpio formats didn't		* tar and the <code>-H newc</code> cpio format handle 32-bit inodes; though some older cpio formats didn't
	* the <code>-H newc</code> cpio format has max 1024 char filenames (though ~~Gnu~~ cpio can handle arbitrary lengths) and max 4G filesize~~; the~~ portable <code>-H ustar</code> tar format has max 256 char filenames and max 8G filesize		* the <code>-H newc</code> cpio format has max 1024 char filenames (though GNU cpio can handle arbitrary lengths) and max 4G filesize. The portable <code>-H ustar</code> tar format has max 256 char filenames and max 8G filesize limits
	* in some implementations, cpio wouldn't copy files over 2G properly~~; don~~'t have details about which implementations/versions are so limited		* in some implementations, cpio wouldn't copy files over 2G properly. Don't have details about which implementations/versions are so limited
	* <span id="tar_acl">some tar formats are supposed to handle acls, however [http://unix.stackexchange.com/q/391/4801 in practice this doesn't seem very reliable]~~; not~~ sure what the situation is with cpio; rsync is known to work well for such cases</span>		* <span id="tar_acl">some tar formats are supposed to handle acls, however [http://unix.stackexchange.com/q/391/4801 in practice this doesn't seem very reliable]. Not sure what the situation is with cpio. rsync is known to work well for such cases</span>

	<!-- Some more info: http://www.suse.de/~aj/linux_lfs.html -->		<!-- Some more info: http://www.suse.de/~aj/linux_lfs.html -->
Line 213:		Line 213:
	<ul>		<ul>
	<li><code>--inplace</code>: overwrite existing files in place<br />		<li><code>--inplace</code>: overwrite existing files in place<br />
	rsync's default behavior is to write new files and move them into place when complete~~; this~~ breaks any hard links the existing file may have had and makes a copy-on-write filesystem see the file as entirely new. <code>--inplace</code> specifies an alternate behavior, of writing updated data directly into the existing file.		rsync's default behavior is to write new files and move them into place when complete. This breaks any hard links the existing file may have had and makes a copy-on-write filesystem see the file as entirely new. <code>--inplace</code> specifies an alternate behavior, of writing updated data directly into the existing file.
	</ul>		</ul>
	* <code>-h</code> or <code>--human-readable</code>: report statistics in prettier form (use once for powers of 10, twice for powers of 2)		* <code>-h</code> or <code>--human-readable</code>: report statistics in prettier form (use once for powers of 10, twice for powers of 2)
Line 222:		Line 222:

	rsync's advantages:		rsync's advantages:
	* like cp, can handle ACLs and xattrs~~; many~~ tar and cpio implementations don't		* like cp, can handle ACLs and xattrs. Many tar and cpio implementations don't
	* like cpio, can optionally work over ~~the~~ network		* like cpio, can optionally work over a network
	* can resume incomplete transfers, and can do incremental updates if the data is being copied multiple times		* can resume incomplete transfers, and can do incremental updates if the data is being copied multiple times

Mcrute: Remove tools that don't work on Alpine

2020-06-01T01:52:32Z

Remove tools that don't work on Alpine

← Older revision		Revision as of 01:52, 1 June 2020
Line 242:		Line 242:

	=== Other tools ===		=== Other tools ===

	~~{{Cmd\|cd /target~~
	~~dump 0af - /source {{!}} restore rf -}}~~

	{{Cmd\|cd /source		{{Cmd\|cd /source

Dubiousjim: Bootmanagers -> Partitioning and Bootmanagers

2015-01-20T14:28:32Z

Bootmanagers -> Partitioning and Bootmanagers

← Older revision		Revision as of 14:28, 20 January 2015
Line 3:		Line 3:
	We include information about some options that aren't available on BusyBox's implementation of these tools, because you may be copying data to/from systems with other Unix tools installed, which do provide those options.		We include information about some options that aren't available on BusyBox's implementation of these tools, because you may be copying data to/from systems with other Unix tools installed, which do provide those options.

	{{Warning\| None of the methods below will copy the [[~~bootmanagers~~\|bootmanager]] (ext/syslinux, grub, etc) to a new drive; you'll have to install it there explicitly.}}		{{Warning\| None of the methods below will copy the [[Partitioning and Bootmanagers\|bootmanager]] (ext/syslinux, grub, etc) to a new drive; you'll have to install it there explicitly.}}

	== Bit-copying methods ==		== Bit-copying methods ==

Dubiousjim: /* tar */ link to #tar_acl

2012-11-09T17:58:36Z

tar: link to #tar_acl

← Older revision		Revision as of 17:58, 9 November 2012
Line 124:		Line 124:
	* in future, will default to <code>-H posix/pax</code>, which is the POSIX.1-2001 format		* in future, will default to <code>-H posix/pax</code>, which is the POSIX.1-2001 format
	* v.1.13 - current (v1.26 released Mar 2011, still current in Mar 2012): defaults to <code>-H gnu</code>, which is not very different from the <code>-H oldgnu</code> format.		* v.1.13 - current (v1.26 released Mar 2011, still current in Mar 2012): defaults to <code>-H gnu</code>, which is not very different from the <code>-H oldgnu</code> format.
	* <code>-H ustar</code> is the portable POSIX.1-1988 format, some limits including max 256 char filenames, max 8G filesize; supports special files, but not sparse files; also seems not to support xattrs and ACLs		* <code>-H ustar</code> is the portable POSIX.1-1988 format, some limits including max 256 char filenames, max 8G filesize; supports special files, but not sparse files; also seems not to support xattrs and ACLs (other tar formats are meant to handle ACLs, but see [[#tar_acl\|comments below]])


Line 144:		Line 144:
	Example of copying from remote machine:		Example of copying from remote machine:
	{{Cmd\|ssh root@machine "tar -czf- [--one-file-system] /source" {{!}} sudo tar -xpz[v]f- -C /target}}		{{Cmd\|ssh root@machine "tar -czf- [--one-file-system] /source" {{!}} sudo tar -xpz[v]f- -C /target}}




	=== cpio ===		=== cpio ===

Dubiousjim: /* cpio */ note about tar shortcomings with ACLs

2012-11-09T17:57:20Z

cpio: note about tar shortcomings with ACLs

← Older revision		Revision as of 17:57, 9 November 2012
Line 165:		Line 165:
	* the <code>-H newc</code> cpio format has max 1024 char filenames (though Gnu cpio can handle arbitrary lengths) and max 4G filesize; the portable <code>-H ustar</code> tar format has max 256 char filenames and max 8G filesize		* the <code>-H newc</code> cpio format has max 1024 char filenames (though Gnu cpio can handle arbitrary lengths) and max 4G filesize; the portable <code>-H ustar</code> tar format has max 256 char filenames and max 8G filesize
	* in some implementations, cpio wouldn't copy files over 2G properly; don't have details about which implementations/versions are so limited		* in some implementations, cpio wouldn't copy files over 2G properly; don't have details about which implementations/versions are so limited
			* <span id="tar_acl">some tar formats are supposed to handle acls, however [http://unix.stackexchange.com/q/391/4801 in practice this doesn't seem very reliable]; not sure what the situation is with cpio; rsync is known to work well for such cases</span>

	<!-- Some more info: http://www.suse.de/~aj/linux_lfs.html -->		<!-- Some more info: http://www.suse.de/~aj/linux_lfs.html -->
Line 193:		Line 194:
	{{Cmd\|cd /source		{{Cmd\|cd /source
	sudo find . [-xdev] -depth [-print0] {{!}} sudo cpio -o -H newc [-0] {{!}} [gzip -3 {{!}}] ssh root@machine "cd /target; gunzip {{!}} cpio -idm[vu]"}}		sudo find . [-xdev] -depth [-print0] {{!}} sudo cpio -o -H newc [-0] {{!}} [gzip -3 {{!}}] ssh root@machine "cd /target; gunzip {{!}} cpio -idm[vu]"}}



	=== rsync ===		=== rsync ===

Dubiousjim: /* rsync */ removed warning, problems with large copies weren't rsync-specific and have disappeared with later kernels

2012-11-09T17:52:57Z

rsync: removed warning, problems with large copies weren't rsync-specific and have disappeared with later kernels

← Older revision		Revision as of 17:52, 9 November 2012
Line 229:		Line 229:
	* like cpio, can optionally work over the network		* like cpio, can optionally work over the network
	* can resume incomplete transfers, and can do incremental updates if the data is being copied multiple times		* can resume incomplete transfers, and can do incremental updates if the data is being copied multiple times

	{{Warning\| I've several times had it stop in the middle of a large copy because of some funky filenames, or corrupt packets. Using cpio or tar over ssh seemed to work fine. It ''may'' be more reliable to use one of the other methods for initial bulk copies, and restrict the use of rsync to incremental updates. Or it may be that the other methods are just silently ignoring issues that rsync more decently chooses to announce.}}

Dubiousjim: /* rsync */ fix markup

2012-04-01T10:54:41Z

rsync: fix markup

← Older revision		Revision as of 10:54, 1 April 2012
Line 230:		Line 230:
	* can resume incomplete transfers, and can do incremental updates if the data is being copied multiple times		* can resume incomplete transfers, and can do incremental updates if the data is being copied multiple times

	{{Warning: I've several times had it stop in the middle of a large copy because of some funky filenames, or corrupt packets. Using cpio or tar over ssh seemed to work fine. It ''may'' be more reliable to use one of the other methods for initial bulk copies, and restrict the use of rsync to incremental updates. Or it may be that the other methods are just silently ignoring issues that rsync more decently chooses to announce.}}		{{Warning\| I've several times had it stop in the middle of a large copy because of some funky filenames, or corrupt packets. Using cpio or tar over ssh seemed to work fine. It ''may'' be more reliable to use one of the other methods for initial bulk copies, and restrict the use of rsync to incremental updates. Or it may be that the other methods are just silently ignoring issues that rsync more decently chooses to announce.}}

Dubiousjim: /* rsync */ add include,exclude, identify tricky filenames?

2012-04-01T10:53:55Z

rsync: add include,exclude, identify tricky filenames?

← Older revision		Revision as of 10:53, 1 April 2012
Line 230:		Line 230:
	* can resume incomplete transfers, and can do incremental updates if the data is being copied multiple times		* can resume incomplete transfers, and can do incremental updates if the data is being copied multiple times

			{{Warning: I've several times had it stop in the middle of a large copy because of some funky filenames, or corrupt packets. Using cpio or tar over ssh seemed to work fine. It ''may'' be more reliable to use one of the other methods for initial bulk copies, and restrict the use of rsync to incremental updates. Or it may be that the other methods are just silently ignoring issues that rsync more decently chooses to announce.}}

	{{Todo\| Warning: I had it stop in the middle of a large copy because of some funky filenames; cpio handled them fine. I had assumed these filenames included <code>\n</code>s, but allegedly rsync should be fine with those. Now I've lost track of which files it was.}}

			Including/excluding from transfers:
			* <code>--include=<var>pattern</var>[/]</code>
			* <code>--exclude=<var>pattern</var>[/]</code>
			Each of these may be repeated. The <var>pattern</var>s may contain <code></code>, <code>*</code>, <code>?</code>, <code>[a-z]</code>.
			A trailing <code><var>dir</var>/***</code> matches both <var>dir</var> and its contents.
			If <var>pattern</var> contains a <code>**</code> or (non-trailing) <code>/</code>, it matches against the full path from {{Path\|/target}}, else it only matches against the final path element.

	=== lvm ===		=== lvm ===