> -Original Message-
> From: devel-boun...@lists.fedoraproject.org [mailto:devel-
> boun...@lists.fedoraproject.org] On Behalf Of Major Hayden
> My goal is to live boot our servers since the majority of our systems would be
> stateless. Being able to reboot into a known good, tested state
On Mon, 2014-07-28 at 21:26 -0500, Major Hayden wrote:
> On Jul 28, 2014, at 17:11, Will Woods wrote:
>
> > Since your systems have lots of RAM, why not just use a regular ext4
> > filesystem image as your root filesystem? Then you don't need to worry
> > about blowing up the overlay at all.
>
>
>> You're not quite right about how the overlay works.
>>
>> The default in-memory overlay is just 512MB. And the device-mapper docs
>> note that "if it fills up the snapshot will become useless and be
>> disabled, returning errors."[1].
>>
>> You should also note that the overlay is a block-level
On Jul 28, 2014, at 17:11, Will Woods wrote:
> You're not quite right about how the overlay works.
>
> The default in-memory overlay is just 512MB. And the device-mapper docs
> note that "if it fills up the snapshot will become useless and be
> disabled, returning errors."[1].
>
> You should al
On Mon, 2014-07-28 at 09:37 -0500, Major Hayden wrote:
> Hello there,
>
> I'm working with F20 and CentOS 7 to create some live booted images.
> I'm not looking to do live USB/CD media, but rather boot a server over
> the network with a kernel, initramfs, and squashfs. It's working well
> so far,
On Jul 28, 2014, at 10:55, Fabian Deutsch wrote:
>
> I am not completely if it is this issue you are seeing, but a squashfs image
> takes more memory then the image itself, becasue you first need to unsquash
> (in ram) and the load the fs pages into ram.
> Also take a look here:
> http://dumm
