If the tmpfs being used to hold the image filesystem is close to being
full then housing the raw disk image in the same place can be
problematic as it tends to grow faster then the filesystem shrinks when
data is being moved into it.
Putting them both into separate tmpfs's will allow there to be an
overlap where they jointly use more then the size limit for a singe tmpfs.
Reviewed: https:/ /review. openstack. org/91545 /git.openstack. org/cgit/ openstack/ diskimage- builder/ commit/ ?id=3fada2566a3 66c8bc1b668e91c 8412b8fb63fd7a
Committed: https:/
Submitter: Jenkins
Branch: master
commit 3fada2566a366c8 bc1b668e91c8412 b8fb63fd7a
Author: Derek Higgins <email address hidden>
Date: Thu May 1 10:22:15 2014 +0100
Build raw image in separate tmpfs
If the tmpfs being used to hold the image filesystem is close to being
full then housing the raw disk image in the same place can be
problematic as it tends to grow faster then the filesystem shrinks when
data is being moved into it.
Putting them both into separate tmpfs's will allow there to be an
overlap where they jointly use more then the size limit for a singe tmpfs.
Change-Id: Ia17ca357d3b865 d70a2d3e13e0479 d008ca5f924
Closes-Bug: #1289582