Talk:LiveOS image - Revision history

FGrose: Replaced content with "Previous content for this page is now at the Fedora Project wiki, fedora:Talk:LiveOS image. --~~~~"

2012-08-22T02:15:38Z

Replaced content with "Previous content for this page is now at the Fedora Project wiki, fedora:Talk:LiveOS image. --~~~~"

← Older revision		Revision as of 22:15, 21 August 2012
Line 1:		Line 1:
	~~It turns out that it is possible to merge down the persistent overlay into the base image, if you have access to another OS installation and sufficient disk space.~~		Previous content for this page is now at the Fedora Project wiki, [[fedora:Talk:LiveOS image]]. --[[User:FGrose\|FGrose]] 22:15, 21 August 2012 (EDT)
	~~: Another OS installation is optional. (See [[LiveOS image#Image recompression and overlay refreshment]].)~~
	~~: Thanks~~ for ~~demonstrating~~ this ~~technique. --[[User:FGrose\|FGrose]] 01:21, 20 August 2012 (EDT)~~
	~~I like that result better than just having to increase the overlay size without bounds.~~

	Tested and working on a Fedora 17 x86_64 Live image installed via livecd-iso-to-disk to a USB stick, all commands as root. You will need disk space sufficient for the uncompressed size of the root filesystem, 4 GB in the case of Fedora 17. I assume only one image and one user on the machine.

	~~Step 1: Get access to read-write base image, note that I got loop2 and loop3 here, YMMV.~~
	~~<nowiki>mkdir squashfs~~
	~~mount -o loop /run/media/*/LIVE/LiveOS/squashfs.img squashfs/~~
	~~cp squashfs/LiveOS/ext3fs.img .</nowiki>~~

	~~Step 2: Set up loopback and device mapper devices for persistent overlay, base device mapper and snapshot.~~
	~~<nowiki>losetup -f ext3fs.img~~
	losetup -f /run/media//LIVE/LiveOS/overlay-
	~~echo 0 $(blockdev --getsize /dev/loop2) linear /dev/loop2 0 \|dmsetup create orig~~
	~~echo 0 $(blockdev --getsize /dev/mapper/orig) snapshot /dev/mapper/orig /dev/loop3 p 8 \| dmsetup create top</nowiki>~~

	~~Step 3: Stop the snapshot device and merge the snapshot with the base~~
	~~<nowiki>dmsetup suspend top~~
	~~echo 0 $(blockdev --getsize /dev/loop2) snapshot-merge /dev/loop2 /dev/loop3 p 8 \| dmsetup create mergeomatic && dmsetup status mergeomatic</nowiki>~~

	~~Step 4: Wait for merge to complete. When the status report on mergeomatic reports allocated blocks equal to the metadata blocks, the merge~~ is ~~finished.~~
	~~dmsetup status~~

	~~Step 5: Remove the merge target.~~
	~~dmsetup remove mergeomatic~~

	~~Step 6: Set the top device to no snapshot, and inspect the filesystem for results, if desired.~~
	~~<nowiki>echo 0 $(blockdev --getsize /dev/loop2) linear /dev/loop2 0 \| dmsetup load top~~
	~~dmsetup resume top~~
	~~mkdir root~~
	~~mount /dev/mapper/top root~~
	~~cd root~~
	~~chroot .</nowiki>~~

	~~Step 7: Clean up.~~
	~~<nowiki>cd ..~~
	~~umount root~~
	~~dmsetup remove top~~
	~~dmsetup remove orig~~
	~~losetup -d /dev/loop2~~
	~~losetup -d /dev/loop3~~
	~~umount squashfs/</nowiki>~~

	~~Step 8: Copy~~ the ~~root filesystem image back into the squashfs image, you may need -noappend~~
	~~<nowiki>mkdir LiveOS~~
	~~mv ext3fs.img LiveOS~~
	~~rm /run/media/*/LIVE/LiveOS/squashfs.img~~
	~~mksquashfs LiveOS /run/media/*/LIVE/LiveOS/squashfs.img -keep-as-directory</nowiki>~~

	~~Sources: <br>~~
	*http://smorgasbord.gavagai.nl/2010/03/online-merging-of-cow-volumes-with-dm-snapshot <br>
	*http://www.kernel.org/doc/Documentation/device-mapper/snapshot.txt<br>
	*http://linuxgazette.net/114/kapil.html<br>

	~~--[[User:Andrew Gilmore\|Andrew Gilmore]]~~

	~~: I have copied most of this~~ Fedora ~~content to the Fedoraproject~~ wiki, at [[fedora:LiveOS image]]. --[[User:FGrose\|FGrose]] 23:38, 20 August 2012 (EDT)

FGrose at 03:38, 21 August 2012

2012-08-21T03:38:03Z

← Older revision		Revision as of 23:38, 20 August 2012
Line 57:		Line 57:
	--[[User:Andrew Gilmore\|Andrew Gilmore]]		--[[User:Andrew Gilmore\|Andrew Gilmore]]

	: I ~~think we should move~~ most of this Fedora content to the Fedoraproject wiki, ~~probably as a subpage to~~ [[fedora:~~How to create and use Live USB~~]]. --[[User:FGrose\|FGrose]] 01:21, 20 August 2012 (EDT)		: I have copied most of this Fedora content to the Fedoraproject wiki, at [[fedora:LiveOS image]]. --[[User:FGrose\|FGrose]] 23:38, 20 August 2012 (EDT)

FGrose at 05:21, 20 August 2012

2012-08-20T05:21:05Z

← Older revision		Revision as of 01:21, 20 August 2012
Line 1:		Line 1:
	It turns out that it is possible to merge down the persistent overlay into the base image, if you have access to another OS installation and sufficient disk space.		It turns out that it is possible to merge down the persistent overlay into the base image, if you have access to another OS installation and sufficient disk space.
			: Another OS installation is optional. (See [[LiveOS image#Image recompression and overlay refreshment]].)
			: Thanks for demonstrating this technique. --[[User:FGrose\|FGrose]] 01:21, 20 August 2012 (EDT)
	I like that result better than just having to increase the overlay size without bounds.		I like that result better than just having to increase the overlay size without bounds.

Line 54:		Line 56:

	--[[User:Andrew Gilmore\|Andrew Gilmore]]		--[[User:Andrew Gilmore\|Andrew Gilmore]]

			: I think we should move most of this Fedora content to the Fedoraproject wiki, probably as a subpage to [[fedora:How to create and use Live USB]]. --[[User:FGrose\|FGrose]] 01:21, 20 August 2012 (EDT)

Andrew Gilmore: Sources, more information about merge steps. Signed.

2012-08-19T16:55:08Z

Sources, more information about merge steps. Signed.

← Older revision		Revision as of 12:55, 19 August 2012
Line 2:		Line 2:
	I like that result better than just having to increase the overlay size without bounds.		I like that result better than just having to increase the overlay size without bounds.

	Tested and working on Fedora 17, all commands as root. You will need disk space sufficient for the uncompressed size of the root filesystem, 4 GB in the case of Fedora 17 ~~LiveCD/USB~~. I assume only one image and one user on the machine.		Tested and working on a Fedora 17 x86_64 Live image installed via livecd-iso-to-disk to a USB stick, all commands as root. You will need disk space sufficient for the uncompressed size of the root filesystem, 4 GB in the case of Fedora 17. I assume only one image and one user on the machine.

	Step 1: Get access to read-write base image, note that I got loop2 and loop3 here, YMMV.		Step 1: Get access to read-write base image, note that I got loop2 and loop3 here, YMMV.

Andrew Gilmore at 16:51, 19 August 2012

2012-08-19T16:51:57Z

← Older revision		Revision as of 12:51, 19 August 2012
Line 17:		Line 17:
	Step 3: Stop the snapshot device and merge the snapshot with the base		Step 3: Stop the snapshot device and merge the snapshot with the base
	<nowiki>dmsetup suspend top		<nowiki>dmsetup suspend top
	echo 0 $(blockdev --getsize /dev/loop2) snapshot-merge /dev/loop2 /dev/loop3 p 8 \| dmsetup create mergeomatic && dmsetup status ~~mergeomatic~~		echo 0 $(blockdev --getsize /dev/loop2) snapshot-merge /dev/loop2 /dev/loop3 p 8 \| dmsetup create mergeomatic && dmsetup status mergeomatic</nowiki>
	~~dmsetup status~~
	~~dmsetup remove~~ mergeomatic</nowiki>

	Step 4: Set the top device to no snapshot, and inspect the filesystem for results, if desired.		Step 4: Wait for merge to complete. When the status report on mergeomatic reports allocated blocks equal to the metadata blocks, the merge is finished.
			dmsetup status

			Step 5: Remove the merge target.
			dmsetup remove mergeomatic

			Step 6: Set the top device to no snapshot, and inspect the filesystem for results, if desired.
	<nowiki>echo 0 $(blockdev --getsize /dev/loop2) linear /dev/loop2 0 \| dmsetup load top		<nowiki>echo 0 $(blockdev --getsize /dev/loop2) linear /dev/loop2 0 \| dmsetup load top
	dmsetup resume top		dmsetup resume top
Line 29:		Line 33:
	chroot .</nowiki>		chroot .</nowiki>

	Step 5: Clean up.		Step 7: Clean up.
	<nowiki>cd ..		<nowiki>cd ..
	umount root		umount root
Line 38:		Line 42:
	umount squashfs/</nowiki>		umount squashfs/</nowiki>

	Step 6: Copy the root filesystem image back into the squashfs image, you may need -noappend		Step 8: Copy the root filesystem image back into the squashfs image, you may need -noappend
	<nowiki>mkdir LiveOS		<nowiki>mkdir LiveOS
	mv ext3fs.img LiveOS		mv ext3fs.img LiveOS
	rm /run/media/*/LIVE/LiveOS/squashfs.img		rm /run/media/*/LIVE/LiveOS/squashfs.img
	mksquashfs LiveOS /run/media/*/LIVE/LiveOS/squashfs.img -keep-as-directory</nowiki>		mksquashfs LiveOS /run/media/*/LIVE/LiveOS/squashfs.img -keep-as-directory</nowiki>

			Sources: <br>
			*http://smorgasbord.gavagai.nl/2010/03/online-merging-of-cow-volumes-with-dm-snapshot <br>
			*http://www.kernel.org/doc/Documentation/device-mapper/snapshot.txt<br>
			*http://linuxgazette.net/114/kapil.html<br>

			--[[User:Andrew Gilmore\|Andrew Gilmore]]

Andrew Gilmore: Updated mksquashfs line

2012-08-17T04:56:57Z

Updated mksquashfs line

← Older revision		Revision as of 00:56, 17 August 2012
Line 6:		Line 6:
	Step 1: Get access to read-write base image, note that I got loop2 and loop3 here, YMMV.		Step 1: Get access to read-write base image, note that I got loop2 and loop3 here, YMMV.
	<nowiki>mkdir squashfs		<nowiki>mkdir squashfs
	mount -o loop /run/media/*/LIVE/LiveOS/squashfs.img squashfs/		mount -o loop /run/media/*/LIVE/LiveOS/squashfs.img squashfs/
	cp squashfs/LiveOS/ext3fs.img .</nowiki>		cp squashfs/LiveOS/ext3fs.img .</nowiki>

	Step 2: Set up loopback and device mapper devices for persistent overlay, base device mapper and snapshot.		Step 2: Set up loopback and device mapper devices for persistent overlay, base device mapper and snapshot.
	<nowiki>losetup -f ext3fs.img		<nowiki>losetup -f ext3fs.img
	losetup -f /run/media//LIVE/LiveOS/overlay-		losetup -f /run/media//LIVE/LiveOS/overlay-
	echo 0 $(blockdev --getsize /dev/loop2) linear /dev/loop2 0 \|dmsetup create orig		echo 0 $(blockdev --getsize /dev/loop2) linear /dev/loop2 0 \|dmsetup create orig
	echo 0 $(blockdev --getsize /dev/mapper/orig) snapshot /dev/mapper/orig /dev/loop3 p 8 \| dmsetup create top</nowiki>		echo 0 $(blockdev --getsize /dev/mapper/orig) snapshot /dev/mapper/orig /dev/loop3 p 8 \| dmsetup create top</nowiki>

	Step 3: Stop the snapshot device and merge the snapshot with the base		Step 3: Stop the snapshot device and merge the snapshot with the base
	<nowiki>dmsetup suspend top		<nowiki>dmsetup suspend top
	echo 0 $(blockdev --getsize /dev/loop2) snapshot-merge /dev/loop2 /dev/loop3 p 8 \| dmsetup create mergeomatic && dmsetup status mergeomatic		echo 0 $(blockdev --getsize /dev/loop2) snapshot-merge /dev/loop2 /dev/loop3 p 8 \| dmsetup create mergeomatic && dmsetup status mergeomatic
	dmsetup status		dmsetup status
	dmsetup remove mergeomatic</nowiki>		dmsetup remove mergeomatic</nowiki>

	Step 4: Set the top device to no snapshot, and inspect the filesystem for results, if desired.		Step 4: Set the top device to no snapshot, and inspect the filesystem for results, if desired.
	<nowiki>echo 0 $(blockdev --getsize /dev/loop2) linear /dev/loop2 0 \| dmsetup load top		<nowiki>echo 0 $(blockdev --getsize /dev/loop2) linear /dev/loop2 0 \| dmsetup load top
	dmsetup resume top		dmsetup resume top
	mkdir root		mkdir root
	mount /dev/mapper/top root		mount /dev/mapper/top root
	cd root		cd root
	chroot .</nowiki>		chroot .</nowiki>

	Step 5: Clean up.		Step 5: Clean up.
	<nowiki>cd ..		<nowiki>cd ..
	umount root		umount root
	dmsetup remove top		dmsetup remove top
	dmsetup remove orig		dmsetup remove orig
	losetup -d /dev/loop2		losetup -d /dev/loop2
	losetup -d /dev/loop3		losetup -d /dev/loop3
	umount squashfs/</nowiki>		umount squashfs/</nowiki>

	Step 6: Copy the root filesystem image back into the squashfs image, you may need -noappend		Step 6: Copy the root filesystem image back into the squashfs image, you may need -noappend
	<nowiki>mkdir LiveOS		<nowiki>mkdir LiveOS
	mv ext3fs.img LiveOS		mv ext3fs.img LiveOS
	~~mksquashfs~~ LiveOS/~~ext3fs~~.img /run/media/*/LIVE/LiveOS/squashfs.img -~~noappend~~</nowiki>		rm /run/media/*/LIVE/LiveOS/squashfs.img
			mksquashfs LiveOS /run/media/*/LIVE/LiveOS/squashfs.img -keep-as-directory</nowiki>

Andrew Gilmore: Fixed mksquashfs call syntax

2012-08-16T23:35:29Z

Fixed mksquashfs call syntax

← Older revision		Revision as of 19:35, 16 August 2012
Line 39:		Line 39:

	Step 6: Copy the root filesystem image back into the squashfs image, you may need -noappend		Step 6: Copy the root filesystem image back into the squashfs image, you may need -noappend
	<nowiki>mksquashfs ext3fs.img /run/media/*/LIVE/LiveOS/squashfs.img</nowiki>		<nowiki>mkdir LiveOS
			mv ext3fs.img LiveOS
			mksquashfs LiveOS/ext3fs.img /run/media/*/LIVE/LiveOS/squashfs.img -noappend</nowiki>

Andrew Gilmore: Fixed formatting

2012-08-16T23:31:20Z

Fixed formatting

← Older revision		Revision as of 19:31, 16 August 2012
Line 5:		Line 5:

	Step 1: Get access to read-write base image, note that I got loop2 and loop3 here, YMMV.		Step 1: Get access to read-write base image, note that I got loop2 and loop3 here, YMMV.
	<nowiki>mkdir squashfs		<nowiki>mkdir squashfs
	mount -o loop /run/media/*/LIVE/LiveOS/squashfs.img squashfs/		mount -o loop /run/media/*/LIVE/LiveOS/squashfs.img squashfs/
	cp squashfs/LiveOS/ext3fs.img .</nowiki>		cp squashfs/LiveOS/ext3fs.img .</nowiki>

	Step 2: Set up loopback and device mapper devices for persistent overlay, base device mapper and snapshot.		Step 2: Set up loopback and device mapper devices for persistent overlay, base device mapper and snapshot.
	<nowiki>losetup -f ext3fs.img		<nowiki>losetup -f ext3fs.img
	losetup -f /run/media//LIVE/LiveOS/overlay-		losetup -f /run/media//LIVE/LiveOS/overlay-
	echo 0 $(blockdev --getsize /dev/loop2) linear /dev/loop2 0 \|dmsetup create orig		echo 0 $(blockdev --getsize /dev/loop2) linear /dev/loop2 0 \|dmsetup create orig
	echo 0 $(blockdev --getsize /dev/mapper/orig) snapshot /dev/mapper/orig /dev/loop3 p 8 \| dmsetup create top</nowiki>		echo 0 $(blockdev --getsize /dev/mapper/orig) snapshot /dev/mapper/orig /dev/loop3 p 8 \| dmsetup create top</nowiki>

	Step 3: Stop the snapshot device and merge the snapshot with the base		Step 3: Stop the snapshot device and merge the snapshot with the base
	<nowiki>dmsetup suspend top		<nowiki>dmsetup suspend top
	echo 0 $(blockdev --getsize /dev/loop2) snapshot-merge /dev/loop2 /dev/loop3 p 8 \| dmsetup create mergeomatic && dmsetup status mergeomatic		echo 0 $(blockdev --getsize /dev/loop2) snapshot-merge /dev/loop2 /dev/loop3 p 8 \| dmsetup create mergeomatic && dmsetup status mergeomatic
	dmsetup status		dmsetup status
	dmsetup remove mergeomatic</nowiki>		dmsetup remove mergeomatic</nowiki>

	Step 4: Set the top device to no snapshot, and inspect the filesystem for results, if desired.		Step 4: Set the top device to no snapshot, and inspect the filesystem for results, if desired.
	<nowiki>echo 0 $(blockdev --getsize /dev/loop2) linear /dev/loop2 0 \| dmsetup load top		<nowiki>echo 0 $(blockdev --getsize /dev/loop2) linear /dev/loop2 0 \| dmsetup load top
	dmsetup resume top		dmsetup resume top
	mkdir root		mkdir root
	mount /dev/mapper/top root		mount /dev/mapper/top root
	cd root		cd root
	chroot .</nowiki>		chroot .</nowiki>

	Step 5: Clean up.		Step 5: Clean up.
	<nowiki>cd ..		<nowiki>cd ..
	umount root		umount root
	dmsetup remove top		dmsetup remove top
	dmsetup remove orig		dmsetup remove orig
	losetup -d /dev/loop2		losetup -d /dev/loop2
	losetup -d /dev/loop3		losetup -d /dev/loop3
	umount squashfs/</nowiki>		umount squashfs/</nowiki>

	Step 6: Copy the root filesystem image back into the squashfs image, you may need -noappend		Step 6: Copy the root filesystem image back into the squashfs image, you may need -noappend
	<nowiki>mksquashfs ext3fs.img /run/media/*/LIVE/LiveOS/squashfs.img</nowiki>		<nowiki>mksquashfs ext3fs.img /run/media/*/LIVE/LiveOS/squashfs.img</nowiki>

Andrew Gilmore: Merge in that persistent overlay, don't expand it! Version 0.1, having formatting issues

2012-08-16T23:28:58Z

Merge in that persistent overlay, don't expand it! Version 0.1, having formatting issues

New page

It turns out that it is possible to merge down the persistent overlay into the base image, if you have access to another OS installation and sufficient disk space.
I like that result better than just having to increase the overlay size without bounds.

Tested and working on Fedora 17, all commands as root. You will need disk space sufficient for the uncompressed size of the root filesystem, 4 GB in the case of Fedora 17 LiveCD/USB. I assume only one image and one user on the machine.

Step 1: Get access to read-write base image, note that I got loop2 and loop3 here, YMMV.
<nowiki>mkdir squashfs
mount -o loop /run/media/*/LIVE/LiveOS/squashfs.img squashfs/
cp squashfs/LiveOS/ext3fs.img .</nowiki>

Step 2: Set up loopback and device mapper devices for persistent overlay, base device mapper and snapshot.
<nowiki>losetup -f ext3fs.img
losetup -f /run/media/*/LIVE/LiveOS/overlay-*
echo 0 $(blockdev --getsize /dev/loop2) linear /dev/loop2 0 |dmsetup create orig
echo 0 $(blockdev --getsize /dev/mapper/orig) snapshot /dev/mapper/orig /dev/loop3 p 8 | dmsetup create top</nowiki>

Step 3: Stop the snapshot device and merge the snapshot with the base
<nowiki>dmsetup suspend top
echo 0 $(blockdev --getsize /dev/loop2) snapshot-merge /dev/loop2 /dev/loop3 p 8 | dmsetup create mergeomatic && dmsetup status mergeomatic
dmsetup status
dmsetup remove mergeomatic</nowiki>

Step 4: Set the top device to no snapshot, and inspect the filesystem for results, if desired.
<nowiki>echo 0 $(blockdev --getsize /dev/loop2) linear /dev/loop2 0 | dmsetup load top
dmsetup resume top
mkdir root
mount /dev/mapper/top root
cd root
chroot .</nowiki>

Step 5: Clean up.
<nowiki>cd ..
umount root
dmsetup remove top
dmsetup remove orig
losetup -d /dev/loop2
losetup -d /dev/loop3
umount squashfs/</nowiki>

Step 6: Copy the root filesystem image back into the squashfs image, you may need -noappend
<nowiki>mksquashfs ext3fs.img /run/media/*/LIVE/LiveOS/squashfs.img</nowiki>