Ploop/sparse - Revision history

Kir: rm translate tags

2021-03-10T15:27:15Z

rm translate tags

Sergey Bronnikov: Marked this version for translation

2015-12-26T08:42:46Z

Marked this version for translation

Sergey Bronnikov: add 'translate' tags

2015-12-25T22:39:49Z

add 'translate' tags

Kir: more error messages

2014-04-17T17:00:10Z

more error messages

Kir: added to Troubleshooting category

2014-01-24T02:28:59Z

added to Troubleshooting category

Kir: added to Storage category

2014-01-23T19:03:06Z

added to Storage category

Kir: more info

2013-12-16T21:45:35Z

more info

Paparaciz: missed closing bracket

2013-11-20T12:42:05Z

missed closing bracket

Kir: created

2013-11-20T12:02:19Z

created

New page

'''Sparse file''' is a file that contains blocks of zeroes that are not allocated on disk (see [[w:Sparse file]]). By design, ploop images can't contain such non-allocated blocks.

While ploop is never creating sparse image files, they can be accidentally made so when tools such as <code>rsync --sparse</code> or <code>cp --sparse=always</code are used to copy images. So, one should not use backup or copy tools that create sparse files out of non-sparse ones.

Since [[Download/ploop/1.10|ploop-1.10]], ploop images are checked for being sparse and are automatically fixed on mount, in case DiskDescriptor.xml is used. Otherwise, you can use <code>ploop check --repair-sparse</code> to check for and repair such images.

== See also ==

* [[Ploop]]
* [[w:Sparse file]]

[[Category: ploop]]

@@ Line 1: / Line 1: @@
 '''Sparse file''' is a file that contains blocks of zeroes that are not allocated on disk (see [[w:Sparse file]]). By design, ploop images can't contain such non-allocated blocks.
 While ploop is never creating sparse image files, they can be accidentally made so when tools such as <code>rsync --sparse</code> or <code>cp --sparse=always</code> are used to copy images. So, one should not use backup or copy tools that create sparse files out of non-sparse ones.
-== Kernel warning == <!--T:3-->
+== Kernel warning ==
 In case sparse file is detected by the kernel, it gives a warning in dmesg, for example:
-  <!--T:5-->
+  Nov 21 20:37:27 sun kernel: [43451.057489] ploop(24002): a hole in image file detected (0)
 In case there are no other ploop-related warnings or errors immediately after, this one is harmless ({{B|2825}}).
-== Userspace warnings == <!--T:7-->
+== Userspace warnings ==
 You might see something like this (reported by ploop library) during container start or mount:
-  <!--T:9-->
+  Error in check_and_repair_sparse (check.c:542): Delta file /vz/private/1407/root.hdd/root.hdd contains uninitialized blocks (offset=135573536768 len=1323008) which are not aligned to cluster size
   Error in fill_hole (check.c:456): Warning: ploop image '/vz/private/1407/root.hdd/root.hdd' is sparse
   Reallocating sparse blocks back
 The last line tells that ploop library is going to fix the problem.
-== How to fix == <!--T:11-->
+== How to fix ==
 Since [[Download/ploop/1.10|ploop-1.10]], ploop images are checked for being sparse and are automatically fixed on mount, in case DiskDescriptor.xml is used. Otherwise, you can use <code>ploop check --repair-sparse</code> to check for and repair such images.
-<!--T:13-->
+Alternatively, you can just do something like this to get rid of holes. Make sure ploop file is not used!
-  <!--T:14-->
+  cat root.hdd > root.hdd2 && mv root.hdd2 root.hdd
 cat root.hdd > root.hdd2 && mv root.hdd2 root.hdd
 * [[Ploop]]
 * [[w:Sparse file]]
 [[Category: Storage]]
 [[Category: Troubleshooting]]

@@ Line 1: / Line 1: @@
 <translate>
 '''Sparse file''' is a file that contains blocks of zeroes that are not allocated on disk (see [[w:Sparse file]]). By design, ploop images can't contain such non-allocated blocks.
 While ploop is never creating sparse image files, they can be accidentally made so when tools such as <code>rsync --sparse</code> or <code>cp --sparse=always</code> are used to copy images. So, one should not use backup or copy tools that create sparse files out of non-sparse ones.
-== Kernel warning ==
+== Kernel warning == <!--T:3-->
 In case sparse file is detected by the kernel, it gives a warning in dmesg, for example:
-  Nov 21 20:37:27 sun kernel: [43451.057489] ploop(24002): a hole in image file detected (0)
+  <!--T:5-->
 In case there are no other ploop-related warnings or errors immediately after, this one is harmless ({{B|2825}}).
-== Userspace warnings ==
+== Userspace warnings == <!--T:7-->
 You might see something like this (reported by ploop library) during container start or mount:
-  Error in check_and_repair_sparse (check.c:542): Delta file /vz/private/1407/root.hdd/root.hdd contains uninitialized blocks (offset=135573536768 len=1323008) which are not aligned to cluster size
+  <!--T:9-->
   Error in fill_hole (check.c:456): Warning: ploop image '/vz/private/1407/root.hdd/root.hdd' is sparse
   Reallocating sparse blocks back
 The last line tells that ploop library is going to fix the problem.
-== How to fix ==
+== How to fix == <!--T:11-->
 Since [[Download/ploop/1.10|ploop-1.10]], ploop images are checked for being sparse and are automatically fixed on mount, in case DiskDescriptor.xml is used. Otherwise, you can use <code>ploop check --repair-sparse</code> to check for and repair such images.
 Alternatelely, you can just do something like this to get rid of holes. Make sure ploop file is not used!
-  cat root.hdd > root.hdd2 && mv root.hdd2 root.hdd
+  <!--T:14-->
-== See also ==
+== See also == <!--T:15-->
 * [[Ploop]]
 * [[w:Sparse file]]

@@ Line 1: / Line 1: @@
 '''Sparse file''' is a file that contains blocks of zeroes that are not allocated on disk (see [[w:Sparse file]]). By design, ploop images can't contain such non-allocated blocks.
@@ Line 33: / Line 34: @@
 * [[Ploop]]
 * [[w:Sparse file]]
 [[Category: Storage]]
 [[Category: Troubleshooting]]

← Older revision		Revision as of 17:00, 17 April 2014
Line 10:		Line 10:

	In case there are no other ploop-related warnings or errors immediately after, this one is harmless ({{B\|2825}}).		In case there are no other ploop-related warnings or errors immediately after, this one is harmless ({{B\|2825}}).
		+
		+	== Userspace warnings ==
		+
		+	You might see something like this (reported by ploop library) during container start or mount:
		+
		+	Error in check_and_repair_sparse (check.c:542): Delta file /vz/private/1407/root.hdd/root.hdd contains uninitialized blocks (offset=135573536768 len=1323008) which are not aligned to cluster size
		+	Error in fill_hole (check.c:456): Warning: ploop image '/vz/private/1407/root.hdd/root.hdd' is sparse
		+	Reallocating sparse blocks back
		+
		+	The last line tells that ploop library is going to fix the problem.

	== How to fix ==		== How to fix ==

← Older revision		Revision as of 02:28, 24 January 2014
Line 25:		Line 25:

	[[Category: Storage]]		[[Category: Storage]]
		+	[[Category: Troubleshooting]]

← Older revision		Revision as of 19:03, 23 January 2014
Line 24:		Line 24:
	* [[w:Sparse file]]		* [[w:Sparse file]]

−	[[Category: ~~ploop~~]]	+	[[Category: Storage]]