From: "Thorsten Schöning" <tschoening@am-soft.de>
To: <linux-btrfs@vger.kernel.org>
Subject: Re: How does BTRFS compression influence existing and new snapshots?
Date: Sat, 29 May 2021 11:53:30 +0200 [thread overview]
Message-ID: <1806742121.20210529115330@am-soft.de> (raw)
In-Reply-To: <20210528193612.GE11733@hungrycats.org>
Guten Tag Zygo Blaxell,
am Freitag, 28. Mai 2021 um 21:36 schrieben Sie:
> Nothing happens to the snapshots. 'fi defrag' will make new, possibly
> compressed (but possibly not compressed) duplicate copies of the data
> in the listed files. These copies will use separate storage space from
> the snapshots.
Thanks for clearing things up, that what's I expected already.
> Each individual extent written on the filesystem contains its own
> independent copy of compression parameters[...]
This brings me to the following in the wiki, not sure if it's worth an
additional thread:
> There is a simple decision logic: if the first portion of data being
> compressed is not smaller than the original, the compression of the
> file is disabled[...]
https://btrfs.wiki.kernel.org/index.php/Compression#What_happens_to_incompressible_files.3F
If (de)compression methods are managed by extents always anway, is the
statement in the wiki really true that compression of a whole FILE is
disabled if the first portion can't be compressed? Or does the quoted
sentence refer to EXTENTS instead of whole FILES instead?
"btrfs-compsize" prints the following for one of my directories, which
means that at least some parts of the file are compressed, others are
not.
> Processed 230 files, 754137 regular extents (754137 refs), 3 inline.
> Type Perc Disk Usage Uncompressed Referenced
> TOTAL 87% 163G 187G 187G
> none 100% 130G 130G 130G
> lzo 57% 32G 56G 56G
So does this really mean that I was simply lucky because "the first
portion" of the file could be compressed? If that wouldn't the case,
the whole file would be uncompressed even though other parts of the
file might be compressed pretty well?
Referrring to the FILE in the wiki instead of EXTENTS doesn't make too
much sense to me currently.
Mit freundlichen Grüßen
Thorsten Schöning
--
AM-SoFT IT-Service - Bitstore Hameln GmbH i.G.
Mitglied der Bitstore Gruppe - Ihr Full-Service-Dienstleister für IT und TK
E-Mail: Thorsten.Schoening@AM-SoFT.de
Web: http://www.AM-SoFT.de/
Tel: 05151- 9468- 0
Tel: 05151- 9468-55
Fax: 05151- 9468-88
Mobil: 0178-8 9468-04
AM-SoFT IT-Service - Bitstore Hameln GmbH i.G., Brandenburger Str. 7c, 31789 Hameln
AG Hannover HRB neu - Geschäftsführer: Janine Galonska
Für Rückfragen stehe ich Ihnen sehr gerne zur Verfügung.
Mit freundlichen Grüßen
Thorsten Schöning
Tel: 05151 9468 0
Fax: 05151 9468 88
Mobil:
Webseite: https://www.am-soft.de
AM-Soft IT-Service - Bitstore Hameln GmbH i.G. ist ein Mitglied der Bitstore Gruppe - Ihr Full-Service-Dienstleister für IT und TK
AM-Soft IT-Service - Bitstore Hameln GmbH i.G.
Brandenburger Str. 7c
31789 Hameln
Tel: 05151 9468 0
Bitstore IT-Consulting GmbH
Zentrale - Berlin Lichtenberg
Frankfurter Allee 285
10317 Berlin
Tel: 030 453 087 80
CBS IT-Service - Bitstore Kaulsdorf UG
Tel: 030 453 087 880 1
Büro Dallgow-Döberitz
Tel: 03322 507 020
Büro Kloster Lehnin
Tel: 033207 566 530
PCE IT-Service - Bitstore Darmstadt UG
Darmstadt
Tel: 06151 392 973 0
Büro Neuruppin
Tel: 033932 606 090
ACI EDV Systemhaus - Bitstore Dresden GmbH
Dresden
Tel: 0351 254 410
Das Systemhaus - Bitstore Magdeburg GmbH
Magdeburg
Tel: 0391 636 651 0
Allerdata.IT - Bitstore Wittenberg GmbH
Wittenberg
Tel: 03491 876 735 7
Büro Liebenwalde
Tel: 033054 810 00
HSA - das Büro - Bitstore Altenburg UG
Altenburg
Tel: 0344 784 390 97
Bitstore IT – Consulting GmbH
NL Piesteritz
Piesteritz
Tel: 03491 644 868 6
Solltec IT-Services - Bitstore Braunschweig UG
Braunschweig
Tel: 0531 206 068 0
MF Computer Service - Bitstore Gütersloh GmbH
Gütersloh
Tel: 05245 920 809 3
Firmensitz: AM-Soft IT-Service - Bitstore Hameln GmbH i.G. , Brandenburger Str. 7c , 31789 Hameln
Geschäftsführer Janine Galonska
next prev parent reply other threads:[~2021-05-29 9:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-28 16:02 How does BTRFS compression influence existing and new snapshots? Thorsten Schöning
2021-05-28 19:36 ` Zygo Blaxell
2021-05-29 9:53 ` Thorsten Schöning [this message]
2021-05-29 22:16 ` Zygo Blaxell
2021-05-31 10:03 ` Thorsten Schöning
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=1806742121.20210529115330@am-soft.de \
--to=tschoening@am-soft.de \
--cc=linux-btrfs@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.