From: Oleg Drokin <green@linuxhacker.ru>
To: Nikita Danilov <Nikita@Namesys.COM>
Cc: Dan Egli <dan@eglifamily.dnsalias.net>, linux-kernel@vger.kernel.org
Subject: Re: 2.6.x breaks some Berkeley/Sleepycat DB functionality
Date: Tue, 13 Jan 2004 12:10:29 +0200 [thread overview]
Message-ID: <20040113101029.GD2224@linuxhacker.ru> (raw)
In-Reply-To: <16387.49164.269996.500699@laputa.namesys.com>
Hello!
On Tue, Jan 13, 2004 at 12:53:16PM +0300, Nikita Danilov wrote:
> > I run a PGP Public key server on this machine and under 2.4.x it's
> > "smooth as silk". But if I boot under 2.6.x, it's gaurenteed failure. If
> > I try to build a database using the build command (this is an sks
> > server, so it's sks build or sks fastbuild) I IMMEDIATELY get Bdb
> > error. But the exact same command with the exact same libraries and
> > input files under 2.4.20 works without a hitch.
> > Anyone got any ideas? Anything else I can provide to assist in debugging?
> On top of what file system berkdb is created? I have a reminiscence that
> Sleepy Cat used to have a problem with reiserfs, due to large
> stat->st_blksize value. Oleg do you remember this?
No, that problem was different. And it was believed that BErkeley DB might just
be performing a bit slower on reiserfs, though I never was able to reproduce and
Sleepycat's code contains it own limit on maximal block size (it uses 16k
blocksize if on suggested by FS is bigger that 16k).
Definitely there were no crashes.
Bye,
Oleg
next prev parent reply other threads:[~2004-01-13 10:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-12 17:16 2.6.x breaks some Berkeley/Sleepycat DB functionality Dan Egli
2004-01-12 17:24 ` Arjan van de Ven
2004-01-12 17:25 ` Valdis.Kletnieks
2004-01-13 9:53 ` Nikita Danilov
2004-01-13 10:10 ` Oleg Drokin [this message]
2004-01-13 17:14 ` dan
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=20040113101029.GD2224@linuxhacker.ru \
--to=green@linuxhacker.ru \
--cc=Nikita@Namesys.COM \
--cc=dan@eglifamily.dnsalias.net \
--cc=linux-kernel@vger.kernel.org \
/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