openstack/diskimage-builder
Code Issues Proposed changes

Ensure that the ext4 fs can be rebuilt up to 1PB in size.

Browse Source 
Change-Id: I16c5fe4eb0a9951d44745d6a46450f70d33b3481
This commit is contained in:
Robert Collins 2013-05-11 16:36:32 +12:00
parent 103bedacc7
commit fb246a02eb
2 changed files with 5 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
README.md
View File

@ -53,7 +53,9 @@ cloud: e.g. a nova-compute node. Images produce either a filesystem image with
a label of cloudimg-rootfs, or can be customised to produce whole disk images
(but will still contain a filesystem labelled cloudimg-rootfs). Once the file
system tree is assembled a loopback device with filesystem (or partition table
and file system) is created and the tree copied into it.
and file system) is created and the tree copied into it. The file system
created is an ext4 filesystem just large enough to hold the file system tree
and can be resized up to 1PB in size.
An element is a particular set of code that alters how the image is built, or
runs within the chroot to prepare the image. E.g. the local-config element

3
bin/disk-image-create
View File

@ -122,7 +122,8 @@ else
MKFS_OPTS="-i 4096"
fi
fi
# allow up to 1PB of 4KB blocks.
OPTS="$MKFS_OPTS -E resize=274877906944"
LOOPDEV=$(sudo losetup --show -f $TMP_IMAGE_PATH)
export EXTRA_UNMOUNT="detach_loopback $LOOPDEV"