Re: new database files not compressed

Hamish Moffatt
2020-08-31T12:56:38Z

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