From: Hannes Dorbath <light@theendofthetunnel.de>
To: Peter Grandi <pg_xf2@xfs2.for.sabi.co.UK>
Cc: Linux XFS <xfs@oss.sgi.com>
Subject: Re: tuning, many small files, small blocksize
Date: Tue, 19 Feb 2008 12:44:57 +0100 [thread overview]
Message-ID: <47BAC139.3000109@theendofthetunnel.de> (raw)
In-Reply-To: <18362.37642.577718.529415@tree.ty.sabi.co.UK>
> That sounds like a good use for a LDAP database, but using
> Berkeley DB directly may be best. One could also do a FUSE module
> or a special purpose NFS server that presents a Berkeley DB as a
> filesystem, but then we would be getting rather close to ReiserFS.
During testing of HA clusters some time ago I found BDB to always be the
first thing to break. It seems to have very poor recovery and seems not
fine with neither file systems snapshots nor power failures.
Nevertheless it's claimed ACID conform. I don't know -- from my
experience I wouldn't even put my address book on it.
Personally I ended up doing this for OpenLDAP and never looked back:
http://www.samse.fr/GPL/ldap_pg/HOWTO/x12.html
--
Best regards,
Hannes Dorbath
next prev parent reply other threads:[~2008-02-19 11:44 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-16 5:01 tuning, many small files, small blocksize Jeff Breidenbach
2008-02-16 9:28 ` Hannes Dorbath
2008-02-16 10:24 ` Jeff Breidenbach
2008-02-16 20:30 ` Jeff Breidenbach
2008-02-19 0:48 ` Timothy Shimmin
2008-02-16 12:23 ` pg_xfs2
2008-02-18 22:53 ` David Chinner
2008-02-18 23:12 ` Linda Walsh
2008-02-18 23:51 ` David Chinner
2008-02-19 1:03 ` Linda Walsh
2008-02-19 2:49 ` David Chinner
2008-02-19 4:58 ` Jeff Breidenbach
2008-02-19 8:27 ` Peter Grandi
2008-02-19 11:44 ` Hannes Dorbath [this message]
2008-02-19 21:24 ` Peter Grandi
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=47BAC139.3000109@theendofthetunnel.de \
--to=light@theendofthetunnel.de \
--cc=pg_xf2@xfs2.for.sabi.co.UK \
--cc=xfs@oss.sgi.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