Results 1 to 1 of 1

Thread: 80GB sparse mdb file to back ldap

  1. #1
    Join Date
    Aug 2009
    Rep Power

    Default 80GB sparse mdb file to back ldap

    Since this thread is closed, I thought I'd post an update to clarify in hopes I'd help folks that rather not slog through many threads and posts.

    Thank you to winepress and quanah for there help in understanding the situation. I'd like to summerize here their
    updated procedure (8.0.2 and later) to shrink /opt/zimbra/data/ldap/mdb/db

    Quote Originally Posted by winepress
    This is for a 64MB datasize. Please change ldap_db_maxsize and ldap_accesslog_maxsize as necessary to suit your environment.
    # update database size
    zmlocalconfig -e ldap_db_maxsize=67108864
    # update log size
    zmlocalconfig -e ldap_accesslog_maxsize=536870912
    That's it, the commands winepress originally had after those two commands were to get around odd behavior in ldap/mdb in early Zimbra 8 (prior to 8.0.2).

    You might do such a crazy thing as shrink this file if you are in my situation:
    (if you are totally small time like me)
    1. You have very few users (I have less than 30).
    2. You and your users make very little use of LDAP.
    3. The size of the real data in the sparse file is very small. "du -ch" reports 1.5MB after several months of running.
    4. You are migrating to a new filesystem... right sized in a VM, /opt is 60GB.

    I understand an 80GB sparse file was "by design." I hope mdb gives HUGE performance increases because the amount of confusion and pain by small timers (that aren't throwing 1TB+ at this) is considerable. Not knowing that there were any sparse files, my rsync command (on a cold zimbra) filled up my destination FS. It took quite a bit of time to track down what was going on. (My first thoughts were large/odd block sizes of destination FS with many files... and then rsync getting confused and some how recursing following symlinks.)

    I hope this helps someone not waste as much time as I have.
    Last edited by scott.serr; 04-17-2014 at 01:01 PM. Reason: typo and wordsmithing

Similar Threads

  1. LDAP MDB back end file huge
    By halfgaar in forum Administrators
    Replies: 11
    Last Post: 12-01-2013, 02:59 AM
  2. 80GB ldap database
    By Fava in forum Administrators
    Replies: 2
    Last Post: 05-22-2013, 10:03 AM
  3. Replies: 3
    Last Post: 01-28-2013, 08:28 PM
  4. Importing tgz file back into Zimbra
    By mrballz in forum General Questions
    Replies: 8
    Last Post: 02-11-2009, 09:37 AM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts