From: Hamish Moffatt <hamish-btrfs@moffatt.email>
To: Nikolay Borisov <nborisov@suse.com>,
Zygo Blaxell <ce3g8jdj@umail.furryterror.org>
Subject: Re: new database files not compressed
Date: Mon, 31 Aug 2020 22:56:23 +1000 [thread overview]
Message-ID: <2eb111da-204d-e723-2245-38c3d9256cfe@moffatt.email> (raw)
In-Reply-To: <68468502-c0e4-d126-3e09-4b5afa0a1f29@suse.com>
On 31/8/20 8:47 pm, Nikolay Borisov wrote:
> <SNIP>
>
>> I created a new file system, ran dd bs=32k count=1024, then the dump
>> shows me items all the way up to item 161. https://pastebin.com/0MPPdqqM
>>
>> item 160 key (258 EXTENT_DATA 33292288) itemoff 7750 itemsize 53
>> generation 7 type 1 (regular)
>> extent data disk byte 14671872 nr 4096
>> extent data offset 0 nr 131072 ram 131072
>> extent compression 3 (zstd)
>> item 161 key (258 EXTENT_DATA 33423360) itemoff 7697 itemsize 53
>> generation 7 type 1 (regular)
>> extent data disk byte 14675968 nr 4096
>> extent data offset 0 nr 131072 ram 131072
>> extent compression 3 (zstd)
>> total bytes 32196018176
>> bytes used 1245184
>> uuid 53eaed91-1060-445b-bf7c-5efe9917adbc
> This output indicates that extents are compressed, what does compsize
> report on this file?
Yes it is right actually, I had wrong mount options before as Roman
observed.
$ sudo compsize zeroes
Type Perc Disk Usage Uncompressed Referenced
TOTAL 3% 1.0M 32M 32M
zstd 3% 1.0M 32M 32M
But it is not working for Firebird still.
$ isql-fb
Use CONNECT or CREATE DATABASE to specify a database
SQL> create database 'test3.fdb' page_size 16384;
SQL> ^D
$ sudo compsize test3.fdb
Type Perc Disk Usage Uncompressed Referenced
TOTAL 100% 2.2M 2.2M 2.2M
none 100% 2.2M 2.2M 2.2M
Hamish
next prev parent reply other threads:[~2020-08-31 12:56 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-30 9:35 new database files not compressed Hamish Moffatt
2020-08-31 2:20 ` Eric Wong
2020-08-31 2:44 ` Hamish Moffatt
2020-08-31 3:15 ` A L
2020-08-31 3:47 ` Zygo Blaxell
2020-08-31 8:53 ` Hamish Moffatt
2020-08-31 9:25 ` Nikolay Borisov
2020-08-31 10:40 ` Hamish Moffatt
2020-08-31 10:47 ` Nikolay Borisov
2020-08-31 12:56 ` Hamish Moffatt [this message]
2020-08-31 11:15 ` Roman Mamedov
2020-08-31 12:54 ` Hamish Moffatt
2020-08-31 12:57 ` Nikolay Borisov
2020-08-31 23:50 ` Hamish Moffatt
2020-09-01 5:15 ` Nikolay Borisov
2020-09-01 8:55 ` Hamish Moffatt
2020-09-02 0:32 ` Hamish Moffatt
2020-09-02 5:57 ` Nikolay Borisov
2020-09-02 6:05 ` Hamish Moffatt
2020-09-02 6:10 ` Nikolay Borisov
2020-09-02 9:57 ` A L
2020-09-02 10:09 ` Nikolay Borisov
2020-09-03 15:04 ` A L
2020-09-02 16:16 ` Zygo Blaxell
2020-09-03 12:53 ` Hamish Moffatt
2020-09-03 19:44 ` Zygo Blaxell
2020-09-04 8:07 ` Hamish Moffatt
2020-09-05 4:07 ` Zygo Blaxell
2020-09-03 15:03 ` A L
2020-09-03 21:52 ` Zygo Blaxell
2020-09-01 1:43 ` Chris Murphy
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=2eb111da-204d-e723-2245-38c3d9256cfe@moffatt.email \
--to=hamish-btrfs@moffatt.email \
--cc=ce3g8jdj@umail.furryterror.org \
--cc=nborisov@suse.com \
/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