7
edits
Changes
Merge in that persistent overlay, don't expand it! Version 0.1, having formatting issues
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>
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>