From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: backup.pl - gzip not working as expected!?
Date: Mon, 27 Dec 2021 11:38:11 +0100 [thread overview]
Message-ID: <3D2CF659-5EEE-46CA-A6E3-99AECDD681AB@ipfire.org> (raw)
In-Reply-To: <b21362c2-ad3b-97e7-f383-722a1049871a@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 2206 bytes --]
Hello,
Thank you for double-checking.
-Michael
> On 27 Dec 2021, at 10:32, Matthias Fischer <matthias.fischer(a)ipfire.org> wrote:
>
> Hi,
>
> On 26.12.2021 21:48, Michael Tremer wrote:
>> 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
>
> Seems I was really busy in the last weeks, otherwise I would have seen
> that this problem was already reported. D'oh!
>
>> So this should be resolved in c163. Can you test and confirm?
>
> I first applied the changes from "[2/3] backup: Create tarball in one
> pass" and can confirm.
>
> The IPF file of the *ISO backup* is now identical to the one created
> *without logs* and correctly compressed as reported by Larsen in
> https://bugzilla.ipfire.org/show_bug.cgi?id=12737#c2 (see attachment).
>
> In a second run I also applied "[1/3] backup: Use filename as specified
> on console" and "[3/3] backup: Fork ISO job into the background in CGI
> script" from https://patchwork.ipfire.org/project/ipfire/list/?series=2450
>
> Looking good.
>
> Best,
> Matthias
>
>> -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>
>>
> <01_ipf_iso_and_without_logs.png><02_ipf_iso_and_without_logs.png>
next parent reply other threads:[~2021-12-27 10:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <b21362c2-ad3b-97e7-f383-722a1049871a@ipfire.org>
2021-12-27 10:38 ` Michael Tremer [this message]
[not found] <712b2fa2-2c72-0fa9-e9fb-b13fde945ab6@ipfire.org>
2021-12-26 20:48 ` 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=3D2CF659-5EEE-46CA-A6E3-99AECDD681AB@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