public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: backup.pl - gzip not working as expected!?
Date: Sun, 26 Dec 2021 21:48:09 +0100	[thread overview]
Message-ID: <5D2BF87D-DA56-4822-8959-85AE4E9CF422@ipfire.org> (raw)
In-Reply-To: <712b2fa2-2c72-0fa9-e9fb-b13fde945ab6@ipfire.org>

[-- Attachment #1: Type: text/plain, Size: 1113 bytes --]

Hello,

> On 25 Dec 2021, at 20:53, Matthias Fischer <matthias.fischer(a)ipfire.org> wrote:
> 
> Hi,
> 
> I wondered for some time - since Friday 21.5.2021 ( ;-) ) - that the IPF
> files of the ISO backups turned out much larger than before.

Yes, they were indeed not compressed at all:

https://bugzilla.ipfire.org/show_bug.cgi?id=12737

So this should be resolved in c163. Can you test and confirm?

-Michael

> Today I tested: when I make a backup *without* logs, the resulting IPF
> is about *26MB* in size.
> 
> The same file is about *108MB* in size when I make an *ISO backup*.
> 
> So I ran ' /var/ipfire/backup/bin/backup.pl iso' from console and
> watched the output.
> 
> After some time, 'gzip' told me:
> 
> ...
> gzip: /var/ipfire/backup/2021-12-25-20:34.ipf already has .ipf suffix --
> unchanged
> ...
> 
> For results, please see attached screenshot (and yes: I use tables... ;-) ).
> 
> The first IPF was created using 'Generate ISO', the second using
> 'Exclude logfiles'.
> 
> Can anyone confirm?
> 
> Best,
> Matthias<ipf_files_differ_in_size.png>


       reply	other threads:[~2021-12-26 20:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <712b2fa2-2c72-0fa9-e9fb-b13fde945ab6@ipfire.org>
2021-12-26 20:48 ` Michael Tremer [this message]
     [not found] <b21362c2-ad3b-97e7-f383-722a1049871a@ipfire.org>
2021-12-27 10:38 ` Michael Tremer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5D2BF87D-DA56-4822-8959-85AE4E9CF422@ipfire.org \
    --to=michael.tremer@ipfire.org \
    --cc=development@lists.ipfire.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox