On Thu, Aug 13, 2015 at 2:54 PM, Matthew Miller
mat...@fedoraproject.org wrote:
On Thu, Aug 13, 2015 at 02:00:11PM -0400, Michael DePaulo wrote:
Yeah, we tried it before, and it was failing in the image build
process. I don't remember the current state.
I am at Flock and I am very interested
On Wed, Jun 17, 2015 at 6:45 PM, Matthew Miller
mat...@fedoraproject.org wrote:
On Wed, Jun 17, 2015 at 06:12:00PM -0400, Dusty Mabe wrote:
Have we considered running fstrim against our cloud image filesystems
before we package it up? I wrote a small script to do it (inside a
container) at
On Thu, Aug 13, 2015 at 02:00:11PM -0400, Michael DePaulo wrote:
Yeah, we tried it before, and it was failing in the image build
process. I don't remember the current state.
I am at Flock and I am very interested in helping with this.
Cool -- thanks for not forgetting about this thread. :)
Hey all,
Have we considered running fstrim against our cloud image filesystems
before we package it up? I wrote a small script to do it (inside a
container) at [1]. Looks like we can save ~28M:
It would need to be incorporated into the image build process because
it would affect checksums
On Wed, Jun 17, 2015 at 06:12:00PM -0400, Dusty Mabe wrote:
Have we considered running fstrim against our cloud image filesystems
before we package it up? I wrote a small script to do it (inside a
container) at [1]. Looks like we can save ~28M:
Yeah, we tried it before, and it was failing in
Hey all,
Have we considered running fstrim against our cloud image filesystems
before we package it up? I wrote a small script to do it (inside a
container) at [1]. Looks like we can save ~28M:
[root@f22 xzimg]# ls -lh ./
total 1.3G
-rw-r--r--. 1 root root 3.0G May 22 00:13 orig.raw
-rw-r--r--.
