Axigen Community Forum

  • If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

Announcement

Collapse
No announcement yet.

Mmessage storage size.

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

    Mmessage storage size.

    Hi all,

    What could be the reason for the sudden increase in total message storage size.
    During the last 6 weeks total sum has increased from 21GB to 47GB, while the size of all accounts increased by only 3,2GB.
    Unfortunately, the Compact_all routine (COMPACT All forced for domain) does not produce the expected result.
    After each time Compact_all is used, the storage size in blocks grows and aligns with Sum all message storage.
    I thought that this procedure would reduce the sum of all allocated space

    Our Axigen Mail-Server version is 8.0.2 (linux/x86),

    Best regards,
    bcteam

    #2
    Hello,

    As you may noticed we have just released the latest update for Axigen X1 (10.1.5) which includes many fixes and improvements over your current version (8.0.2).

    Without having the output of what was the situation before and after compacting the message storage, as well as the output of the compact command I could not give you any explanations.

    Nevertheless I strongly suggest is to install a fresh new Axigen machine (on an x64 supported OS) and migrate your 8.0.2 data to the new server.

    HTH,
    Ioan

    Comment


      #3
      Hi Loan,
      Thank you for your answer,
      I know that upgrade to the latest version of Axigen would be a good option.
      Unfortunately, at the moment we have to work on the current version of the software and try to solve this problem.
      In my opinion, memory management is out of control, details:
      Date Message Storage [MB] Accounts Size [MB]
      13.10.2017 21 282 19 412
      16.10.2017 23 243 19 462
      18.10.2017 24 246 19 736
      20.10.2017 24 305 19 874
      23.10.2017 25 097 19 950
      25.10.2017 26 110 20 036
      27.10.2017 27 200 20 473
      30.10.2017 28 325 20 523
      01.11.2017 28 733 20 571
      03.11.2017 30 773 20 784
      06.11.2017 31 621 20 839
      08.11.2017 32 390 21 131
      10.11.2017 32 715 21 254
      06.11.2017 32 800 21 325
      15.11.2017 35 592 21 615
      17.11.2017 36 575 21 977
      20.11.2017 36 738 22 030
      22.11.2017 38 107 22 133
      24.11.2017 38 372 22 384
      27.11.2017 40 725 22 420
      29.11.2017 47 286 22 634
      01.12.2017 53 229 22 700
      04.12.2017 57 842 22 852

      Delta
      13.10-04.12 36 560 3 287
      last week 17 117 432

      I can give you the output of the compact command, or additional information about the situations before and after the compact command,
      Unfortunately the output of the compact command file is a bit large, it would be best to send it via email,
      I am waiting for your answer at this address: bcteam.pub(@at)gmail.com

      Best regards,
      bcteam

      Comment


        #4
        Hello,
        Unfortunately, I do not have any information as to why our storage is behaving so strangely (it allocates a new place, much faster than it results from the size of accounts/emails).
        In the last 2 months storage space has increased by 41GB (!!!) when the accounts size is only 3.5GB.
        I have carefully analyzed the message container allocation process, and it looks like this:
        1. I changes the maxFiles parameter (I increase from e.g. from 107 to 108)
        12-07 11:46:32 WEBADMIN:00001C35: URI for message storage unit changed to 'file:///var/opt/axigen/domains/domain.nn/messages.1?maxFiles=108&maxFileSize=262144&readOnl y=no
        2. In the directory: ///var/opt/axigen/domains/domain.nn/messages.1 a new 6B.hsf file is created.
        3. After about 5 minutes the file size reaches the maximum value (256M!!!) but size in blocks only 1.3M
        Command result: date; ls -lhs /var/opt/axigen/domains/domain.nn/messages.1/6B.hsf
        Thu Dec 7 11:47:01 CET 2017
        1.3M -rw-r----- 1 axigen axigen 1.6M Dec 7 11:46 /var/opt/axigen/domains/domain.nn/messages.1/6B.hsf
        Thu Dec 7 11:48:01 CET 2017
        1.3M -rw-r----- 1 axigen axigen 1.6M Dec 7 11:47 /var/opt/axigen/domains/domain.nn/messages.1/6B.hsf
        Thu Dec 7 11:49:01 CET 2017
        1.3M -rw-r----- 1 axigen axigen 1.6M Dec 7 11:47 /var/opt/axigen/domains/domain.nn/messages.1/6B.hsf
        Thu Dec 7 11:50:01 CET 2017
        1.3M -rw-r----- 1 axigen axigen 256M Dec 7 11:49 /var/opt/axigen/domains/domain.nn/messages.1/6B.hsf
        Thu Dec 7 11:51:01 CET 2017
        1.3M -rw-r----- 1 axigen axigen 256M Dec 7 11:49 /var/opt/axigen/domains/domain.nn/messages.1/6B.hsf
        Thu Dec 7 11:52:01 CET 2017
        1.3M -rw-r----- 1 axigen axigen 256M Dec 7 11:51 /var/opt/axigen/domains/domain.nn/messages.1/6B.hsf

        4. In the next few hours only size in blocks increases. Changing the size in blocks is comparable with the increase of accounts size. File size remains unchanged (256M).
        Thu Dec 7 11:47:01 CET 2017
        1.3M -rw-r----- 1 axigen axigen 1.6M Dec 7 11:46 /var/opt/axigen/domains/domain.nn/messages.1/6B.hsf
        Thu Dec 7 11:48:01 CET 2017
        1.3M -rw-r----- 1 axigen axigen 1.6M Dec 7 11:47 /var/opt/axigen/domains/domain.nn/messages.1/6B.hsf
        Thu Dec 7 11:49:01 CET 2017
        1.3M -rw-r----- 1 axigen axigen 1.6M Dec 7 11:47 /var/opt/axigen/domains/domain.nn/messages.1/6B.hsf
        Thu Dec 7 11:50:01 CET 2017
        1.3M -rw-r----- 1 axigen axigen 256M Dec 7 11:49 /var/opt/axigen/domains/domain.nn/messages.1/6B.hsf
        Thu Dec 7 11:51:01 CET 2017
        1.3M -rw-r----- 1 axigen axigen 256M Dec 7 11:49 /var/opt/axigen/domains/domain.nn/messages.1/6B.hsf
        Thu Dec 7 11:52:01 CET 2017
        1.3M -rw-r----- 1 axigen axigen 256M Dec 7 11:51 /var/opt/axigen/domains/domain.nn/messages.1/6B.hsf
        Thu Dec 7 11:53:01 CET 2017
        1.3M -rw-r----- 1 axigen axigen 256M Dec 7 11:51 /var/opt/axigen/domains/domain.nn/messages.1/6B.hsf
        Thu Dec 7 11:54:01 CET 2017
        1.3M -rw-r----- 1 axigen axigen 256M Dec 7 11:51 /var/opt/axigen/domains/domain.nn/messages.1/6B.hsf
        Thu Dec 7 11:55:01 CET 2017
        1.3M -rw-r----- 1 axigen axigen 256M Dec 7 11:51 /var/opt/axigen/domains/domain.nn/messages.1/6B.hsf
        Thu Dec 7 12:00:01 CET 2017
        1.3M -rw-r----- 1 axigen axigen 256M Dec 7 11:57 /var/opt/axigen/domains/domain.nn/messages.1/6B.hsf
        Thu Dec 7 12:05:01 CET 2017
        1.3M -rw-r----- 1 axigen axigen 256M Dec 7 11:57 /var/opt/axigen/domains/domain.nn/messages.1/6B.hsf
        Thu Dec 7 12:10:01 CET 2017
        1.3M -rw-r----- 1 axigen axigen 256M Dec 7 12:06 /var/opt/axigen/domains/domain.nn/messages.1/6B.hsf
        Thu Dec 7 12:15:01 CET 2017
        1.5M -rw-r----- 1 axigen axigen 256M Dec 7 12:13 /var/opt/axigen/domains/domain.nn/messages.1/6B.hsf
        Thu Dec 7 12:20:01 CET 2017
        1.6M -rw-r----- 1 axigen axigen 256M Dec 7 12:19 /var/opt/axigen/domains/domain.nn/messages.1/6B.hsf
        Thu Dec 7 12:25:01 CET 2017
        1.7M -rw-r----- 1 axigen axigen 256M Dec 7 12:20 /var/opt/axigen/domains/domain.nn/messages.1/6B.hsf
        Thu Dec 7 12:30:02 CET 2017
        1.7M -rw-r----- 1 axigen axigen 256M Dec 7 12:26 /var/opt/axigen/domains/domain.nn/messages.1/6B.hsf
        Thu Dec 7 12:35:01 CET 2017
        2.1M -rw-r----- 1 axigen axigen 256M Dec 7 12:34 /var/opt/axigen/domains/domain.nn/messages.1/6B.hsf
        Thu Dec 7 12:40:01 CET 2017
        2.1M -rw-r----- 1 axigen axigen 256M Dec 7 12:38 /var/opt/axigen/domains/domain.nn/messages.1/6B.hsf
        Thu Dec 7 12:45:01 CET 2017
        2.1M -rw-r----- 1 axigen axigen 256M Dec 7 12:43 /var/opt/axigen/domains/domain.nn/messages.1/6B.hsf
        Thu Dec 7 12:50:01 CET 2017
        2.1M -rw-r----- 1 axigen axigen 256M Dec 7 12:48 /var/opt/axigen/domains/domain.nn/messages.1/6B.hsf
        Thu Dec 7 12:55:02 CET 2017
        2.1M -rw-r----- 1 axigen axigen 256M Dec 7 12:52 /var/opt/axigen/domains/domain.nn/messages.1/6B.hsf
        Thu Dec 7 13:00:01 CET 2017
        2.2M -rw-r----- 1 axigen axigen 256M Dec 7 12:58 /var/opt/axigen/domains/domain.nn/messages.1/6B.hsf
        Thu Dec 7 13:05:01 CET 2017
        2.2M -rw-r----- 1 axigen axigen 256M Dec 7 13:02 /var/opt/axigen/domains/domain.nn/messages.1/6B.hsf
        Thu Dec 7 13:10:01 CET 2017
        2.2M -rw-r----- 1 axigen axigen 256M Dec 7 13:02 /var/opt/axigen/domains/domain.nn/messages.1/6B.hsf
        Thu Dec 7 13:15:01 CET 2017
        2.5M -rw-r----- 1 axigen axigen 256M Dec 7 13:13 /var/opt/axigen/domains/domain.nn/messages.1/6B.hsf
        Thu Dec 7 13:20:01 CET 2017
        2.5M -rw-r----- 1 axigen axigen 256M Dec 7 13:17 /var/opt/axigen/domains/domain.nn/messages.1/6B.hsf
        Thu Dec 7 13:25:01 CET 2017
        2.5M -rw-r----- 1 axigen axigen 256M Dec 7 13:17 /var/opt/axigen/domains/domain.nn/messages.1/6B.hsf
        Thu Dec 7 13:30:01 CET 2017
        2.5M -rw-r----- 1 axigen axigen 256M Dec 7 13:29 /var/opt/axigen/domains/domain.nn/messages.1/6B.hsf
        Thu Dec 7 13:35:01 CET 2017
        2.5M -rw-r----- 1 axigen axigen 256M Dec 7 13:34 /var/opt/axigen/domains/domain.nn/messages.1/6B.hsf
        Thu Dec 7 13:40:01 CET 2017
        3.0M -rw-r----- 1 axigen axigen 256M Dec 7 13:37 /var/opt/axigen/domains/domain.nn/messages.1/6B.hsf
        Thu Dec 7 13:45:02 CET 2017
        3.8M -rw-r----- 1 axigen axigen 256M Dec 7 13:43 /var/opt/axigen/domains/domain.nn/messages.1/6B.hsf
        Thu Dec 7 13:50:01 CET 2017
        4.2M -rw-r----- 1 axigen axigen 256M Dec 7 13:48 /var/opt/axigen/domains/domain.nn/messages.1/6B.hsf
        Thu Dec 7 13:55:01 CET 2017
        6.2M -rw-r----- 1 axigen axigen 256M Dec 7 13:53 /var/opt/axigen/domains/domain.nn/messages.1/6B.hsf
        Thu Dec 7 14:00:01 CET 2017
        7.2M -rw-r----- 1 axigen axigen 256M Dec 7 13:56 /var/opt/axigen/domains/domain.nn/messages.1/6B.hsf
        Thu Dec 7 14:05:01 CET 2017
        7.2M -rw-r----- 1 axigen axigen 256M Dec 7 14:02 /var/opt/axigen/domains/domain.nn/messages.1/6B.hsf
        Thu Dec 7 14:10:01 CET 2017
        7.8M -rw-r----- 1 axigen axigen 256M Dec 7 14:10 /var/opt/axigen/domains/domain.nn/messages.1/6B.hsf
        Thu Dec 7 14:15:01 CET 2017
        9.6M -rw-r----- 1 axigen axigen 256M Dec 7 14:12 /var/opt/axigen/domains/domain.nn/messages.1/6B.hsf
        Thu Dec 7 14:20:01 CET 2017
        9.6M -rw-r----- 1 axigen axigen 256M Dec 7 14:18 /var/opt/axigen/domains/domain.nn/messages.1/6B.hsf
        Thu Dec 7 14:25:01 CET 2017
        9.6M -rw-r----- 1 axigen axigen 256M Dec 7 14:22 /var/opt/axigen/domains/domain.nn/messages.1/6B.hsf
        Thu Dec 7 14:30:01 CET 2017
        9.6M -rw-r----- 1 axigen axigen 256M Dec 7 14:26 /var/opt/axigen/domains/domain.nn/messages.1/6B.hsf
        Thu Dec 7 14:35:01 CET 2017
        9.6M -rw-r----- 1 axigen axigen 256M Dec 7 14:31 /var/opt/axigen/domains/domain.nn/messages.1/6B.hsf
        Thu Dec 7 14:40:01 CET 2017
        9.6M -rw-r----- 1 axigen axigen 256M Dec 7 14:37 /var/opt/axigen/domains/domain.nn/messages.1/6B.hsf
        Thu Dec 7 14:45:01 CET 2017
        9.6M -rw-r----- 1 axigen axigen 256M Dec 7 14:37 /var/opt/axigen/domains/domain.nn/messages.1/6B.hsf
        Thu Dec 7 14:50:02 CET 2017
        18M -rw-r----- 1 axigen axigen 256M Dec 7 14:46 /var/opt/axigen/domains/domain.nn/messages.1/6B.hsf
        Thu Dec 7 14:55:01 CET 2017
        18M -rw-r----- 1 axigen axigen 256M Dec 7 14:46 /var/opt/axigen/domains/domain.nn/messages.1/6B.hsf
        Thu Dec 7 15:00:01 CET 2017
        20M -rw-r----- 1 axigen axigen 256M Dec 7 14:59 /var/opt/axigen/domains/domain.nn/messages.1/6B.hsf
        Thu Dec 7 15:05:01 CET 2017
        20M -rw-r----- 1 axigen axigen 256M Dec 7 15:04 /var/opt/axigen/domains/domain.nn/messages.1/6B.hsf
        Thu Dec 7 15:10:01 CET 2017
        20M -rw-r----- 1 axigen axigen 256M Dec 7 15:09 /var/opt/axigen/domains/domain.nn/messages.1/6B.hsf
        Thu Dec 7 15:15:01 CET 2017
        20M -rw-r----- 1 axigen axigen 256M Dec 7 15:14 /var/opt/axigen/domains/domain.nn/messages.1/6B.hsf
        Thu Dec 7 15:20:02 CET 2017
        20M -rw-r----- 1 axigen axigen 256M Dec 7 15:19 /var/opt/axigen/domains/domain.nn/messages.1/6B.hsf
        Thu Dec 7 15:25:01 CET 2017
        20M -rw-r----- 1 axigen axigen 256M Dec 7 15:23 /var/opt/axigen/domains/domain.nn/messages.1/6B.hsf
        Thu Dec 7 15:30:02 CET 2017
        21M -rw-r----- 1 axigen axigen 256M Dec 7 15:29 /var/opt/axigen/domains/domain.nn/messages.1/6B.hsf
        Thu Dec 7 15:35:01 CET 2017
        22M -rw-r----- 1 axigen axigen 256M Dec 7 15:32 /var/opt/axigen/domains/domain.nn/messages.1/6B.hsf
        Thu Dec 7 15:40:01 CET 2017
        22M -rw-r----- 1 axigen axigen 256M Dec 7 15:37 /var/opt/axigen/domains/domain.nn/messages.1/6B.hsf
        Thu Dec 7 15:42:01 CET 2017
        22M -rw-r----- 1 axigen axigen 256M Dec 7 15:37 /var/opt/axigen/domains/domain.nn/messages.1/6B.hsf
        Thu Dec 7 15:43:01 CET 2017
        22M -rw-r----- 1 axigen axigen 256M Dec 7 15:37 /var/opt/axigen/domains/domain.nn/messages.1/6B.hsf
        Thu Dec 7 15:44:01 CET 2017
        22M -rw-r----- 1 axigen axigen 256M Dec 7 15:37 /var/opt/axigen/domains/domain.nn/messages.1/6B.hsf
        Thu Dec 7 15:45:02 CET 2017
        22M -rw-r----- 1 axigen axigen 256M Dec 7 15:37 /var/opt/axigen/domains/domain.nn/messages.1/6B.hsf
        Thu Dec 7 15:46:01 CET 2017
        22M -rw-r----- 1 axigen axigen 256M Dec 7 15:37 /var/opt/axigen/domains/domain.nn/messages.1/6B.hsf
        Thu Dec 7 15:47:01 CET 2017
        22M -rw-r----- 1 axigen axigen 256M Dec 7 15:37 /var/opt/axigen/domains/domain.nn/messages.1/6B.hsf
        Thu Dec 7 15:48:01 CET 2017
        22M -rw-r----- 1 axigen axigen 256M Dec 7 15:37 /var/opt/axigen/domains/domain.nn/messages.1/6B.hsf
        Thu Dec 7 15:49:01 CET 2017
        22M -rw-r----- 1 axigen axigen 256M Dec 7 15:37 /var/opt/axigen/domains/domain.nn/messages.1/6B.hsf
        Thu Dec 7 15:50:01 CET 2017
        22M -rw-r----- 1 axigen axigen 256M Dec 7 15:49 /var/opt/axigen/domains/domain.nn/messages.1/6B.hsf
        Thu Dec 7 15:51:01 CET 2017
        22M -rw-r----- 1 axigen axigen 256M Dec 7 15:49 /var/opt/axigen/domains/domain.nn/messages.1/6B.hsf
        Thu Dec 7 15:52:01 CET 2017
        22M -rw-r----- 1 axigen axigen 256M Dec 7 15:51 /var/opt/axigen/domains/domain.nn/messages.1/6B.hsf
        Thu Dec 7 15:53:01 CET 2017
        22M -rw-r----- 1 axigen axigen 256M Dec 7 15:51 /var/opt/axigen/domains/domain.nn/messages.1/6B.hsf
        Thu Dec 7 15:54:01 CET 2017
        22M -rw-r----- 1 axigen axigen 256M Dec 7 15:51 /var/opt/axigen/domains/domain.nn/messages.1/6B.hsf
        (?)
        Tue Dec 12 17:33:13 CET 2017
        23M -rw-r----- 1 axigen axigen 256M Dec 12 17:31 /var/opt/axigen/domains/domain.nn/messages.1/6B.hsf

        5. Unfortunately, when size in block reaches about 22M (2017.12.07 15:41), we receive a message (Not enough space in storage; check storage configuration for domain domain.nn), and STOP receiving new email in this domain. The only effective way to resume work is to add a new message container.
        At the beginning I added 16 files in one step (I changed the maxFiles parameter from 80 to 96), but the effect was even worse because the size in block is smaller than 1M. the next changes were made only by 1.
        The result for today is this:date; ls -lhs /var/opt/axigen/domains/domain.nn/messages.1/[5-7]?.hsf
        Tue Dec 12 17:47:07 CET 2017
        7.8M -rw-r----- 1 axigen axigen 256M Dec 12 17:46 /var/opt/axigen/domains/domain.nn/messages.1/50.hsf
        155M -rw-r----- 1 axigen axigen 256M Dec 12 17:47 /var/opt/axigen/domains/domain.nn/messages.1/51.hsf
        228K -rw-r----- 1 axigen axigen 256M Dec 6 01:00 /var/opt/axigen/domains/domain.nn/messages.1/52.hsf
        528K -rw-r----- 1 axigen axigen 256M Dec 12 17:45 /var/opt/axigen/domains/domain.nn/messages.1/53.hsf
        264K -rw-r----- 1 axigen axigen 256M Dec 6 01:00 /var/opt/axigen/domains/domain.nn/messages.1/54.hsf
        184K -rw-r----- 1 axigen axigen 256M Dec 6 01:00 /var/opt/axigen/domains/domain.nn/messages.1/55.hsf
        508K -rw-r----- 1 axigen axigen 256M Dec 12 16:08 /var/opt/axigen/domains/domain.nn/messages.1/56.hsf
        496K -rw-r----- 1 axigen axigen 256M Dec 12 14:37 /var/opt/axigen/domains/domain.nn/messages.1/57.hsf
        184K -rw-r----- 1 axigen axigen 256M Dec 6 01:00 /var/opt/axigen/domains/domain.nn/messages.1/58.hsf
        220K -rw-r----- 1 axigen axigen 256M Dec 6 01:00 /var/opt/axigen/domains/domain.nn/messages.1/59.hsf
        792K -rw-r----- 1 axigen axigen 256M Dec 12 17:42 /var/opt/axigen/domains/domain.nn/messages.1/5A.hsf
        900K -rw-r----- 1 axigen axigen 256M Dec 12 17:39 /var/opt/axigen/domains/domain.nn/messages.1/5B.hsf
        700K -rw-r----- 1 axigen axigen 256M Dec 12 17:44 /var/opt/axigen/domains/domain.nn/messages.1/5C.hsf
        292K -rw-r----- 1 axigen axigen 256M Dec 12 17:36 /var/opt/axigen/domains/domain.nn/messages.1/5D.hsf
        188K -rw-r----- 1 axigen axigen 256M Dec 5 10:30 /var/opt/axigen/domains/domain.nn/messages.1/5E.hsf
        268K -rw-r----- 1 axigen axigen 256M Dec 6 01:00 /var/opt/axigen/domains/domain.nn/messages.1/5F.hsf
        16M -rw-r----- 1 axigen axigen 256M Dec 12 17:45 /var/opt/axigen/domains/domain.nn/messages.1/60.hsf
        42M -rw-r----- 1 axigen axigen 256M Dec 12 17:45 /var/opt/axigen/domains/domain.nn/messages.1/61.hsf
        40M -rw-r----- 1 axigen axigen 256M Dec 12 17:45 /var/opt/axigen/domains/domain.nn/messages.1/62.hsf
        29M -rw-r----- 1 axigen axigen 256M Dec 12 17:45 /var/opt/axigen/domains/domain.nn/messages.1/63.hsf
        1.3M -rw-r----- 1 axigen axigen 256M Dec 12 17:45 /var/opt/axigen/domains/domain.nn/messages.1/64.hsf
        1.2M -rw-r----- 1 axigen axigen 256M Dec 12 17:45 /var/opt/axigen/domains/domain.nn/messages.1/65.hsf
        69M -rw-r----- 1 axigen axigen 256M Dec 12 17:45 /var/opt/axigen/domains/domain.nn/messages.1/66.hsf
        7.9M -rw-r----- 1 axigen axigen 256M Dec 12 17:46 /var/opt/axigen/domains/domain.nn/messages.1/67.hsf
        24M -rw-r----- 1 axigen axigen 256M Dec 12 17:45 /var/opt/axigen/domains/domain.nn/messages.1/68.hsf
        5.4M -rw-r----- 1 axigen axigen 256M Dec 12 17:45 /var/opt/axigen/domains/domain.nn/messages.1/69.hsf
        1.8M -rw-r----- 1 axigen axigen 256M Dec 12 17:45 /var/opt/axigen/domains/domain.nn/messages.1/6A.hsf
        23M -rw-r----- 1 axigen axigen 256M Dec 12 17:46 /var/opt/axigen/domains/domain.nn/messages.1/6B.hsf
        25M -rw-r----- 1 axigen axigen 256M Dec 12 17:45 /var/opt/axigen/domains/domain.nn/messages.1/6C.hsf
        7.6M -rw-r----- 1 axigen axigen 256M Dec 12 17:45 /var/opt/axigen/domains/domain.nn/messages.1/6D.hsf
        12M -rw-r----- 1 axigen axigen 256M Dec 12 17:45 /var/opt/axigen/domains/domain.nn/messages.1/6E.hsf
        1.2M -rw-r----- 1 axigen axigen 256M Dec 12 17:45 /var/opt/axigen/domains/domain.nn/messages.1/6F.hsf
        16M -rw-r----- 1 axigen axigen 256M Dec 12 17:45 /var/opt/axigen/domains/domain.nn/messages.1/70.hsf
        5.0M -rw-r----- 1 axigen axigen 256M Dec 12 17:46 /var/opt/axigen/domains/domain.nn/messages.1/71.hsf
        3.3M -rw-r----- 1 axigen axigen 256M Dec 12 17:46 /var/opt/axigen/domains/domain.nn/messages.1/72.hsf
        17M -rw-r----- 1 axigen axigen 256M Dec 12 17:42 /var/opt/axigen/domains/domain.nn/messages.1/73.hsf
        17M -rw-r----- 1 axigen axigen 256M Dec 12 17:46 /var/opt/axigen/domains/domain.nn/messages.1/74.hsf

        6. Unfortunately, the Compact_all routine (COMPACT All forced for domain) does not produce the expected result.
        After each time Compact_all is used, the storage size in blocks grows to 256M (???) and very quickly we have the same problem with email (Not enough space in storage; check storage configuration for domain domain.nn).

        My main questions is:
        a) why new files very quickly reach the maximum size (256M)
        b) why is there so much discrepancy between file size (256M) and size in blocks (e.g. 12M)
        c) why Axigen server can not use more recent message container but need to add new ones?

        What is the reason?
        Best regards,
        bcteam

        Comment


          #5
          Hello,

          For your problem my recommended procedure is the following one:
          * based on this KB run the following CLI command:
          Code:
          <domain#> FINDINVALIDMSG * purge
          * continue with the following CLI command:
          Code:
          <domain#> SCAN ALL purge
          Later Edit: well, based on this thread it seems you are using an older version and I have already recommended to migrate to a newer one. Than you just have to skip this step

          * run again the compact (forced) procedure

          * lastly, before considering to add a new message storage, try first to increase the current message storage maxFileSize parameter (when needed, using an increase step of 20%, till you reach the recommended max size of 1 GB).

          Returning to your questions, the main difference between the value displayed by -s and -l is the following one:
          Code:
          -l reports file size (in bytes)
          -s reports actual on-disk size (in blocks)
          Axigen storage files have the tendency to become sparse, especially the ones used for messages and objects.

          There are several ways to detect sparse files, one of them being already mentioned by you.

          One tool that could print the file's sparseness is find (using %S)

          Quoting from find manual:
          This is calculated as (BLOCKSIZE*st_blocks / st_size). The exact value you will get for an ordinary file of a certain length is system-dependent. However, normally sparse files will have values less than 1.0, and files which use indirect blocks may have a value which is greater than 1.0. The value used for BLOCKSIZE is system-dependent, but is usually 512 bytes. If the file size is zero, the value printed is undefined. On systems which lack support for st_blocks, a file?s sparseness is assumed to be 1.0.
          For example, on one of our test servers we have:
          Code:
          [root@axi-36 tmp]# ls -ls /var/opt/axigen/domains/be-33/messages.01
          total 2472
          1844 -rw-r-----. 1 axigen axigen 2723840 Dec 15 08:45 00.hsf
           556 -rw-r-----. 1 axigen axigen 1200128 Dec  7 15:03 01.hsf
             4 -rw-r-----. 1 axigen axigen      69 May 26  2015 hsf.dat
            68 -rw-r-----. 1 axigen axigen   65544 Dec  7 12:42 log.hst
          
          root@axi-36 tmp]# find /var/opt/axigen/domains/be-33/messages.01 -type f ! -size 0 -printf '%p\t%S\t%s bytes\n'
          /var/opt/axigen/domains/be-01/messages.01/log.hst       1.06237 65544 bytes
          /var/opt/axigen/domains/be-01/messages.01/hsf.dat       59.3623 69 bytes
          /var/opt/axigen/domains/be-01/messages.01/00.hsf        0.693233        2723840 bytes
          /var/opt/axigen/domains/be-01/messages.01/01.hsf        0.474403        1200128 bytes
          Now, running Axigen compact command will have an impact on its size because:
          • the additional storage metadata associated to non-compacted storage files will be discarded (not a huge impact on how much space is gained)
          • removed objects are finally deleted from the storage files
          • any storage leaks are deleted as well
          In other words, imediately after a compact operation the sparseness value for .hsf files will be as close as possible to 1.

          For more tools that could help on dealing with sparse files you also check this page, from which I quote below:
          Sparse files are basically just like any other file except that blocks that only contain zeros (i.e., nothing) are not actually stored on disk. This means you can have an apparently 16G file ? with 16G of ?data? ? only taking up 1G of space on disk.
          HTH,
          Ioan


          Comment

          Working...
          X