linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nikita Danilov <Nikita@Namesys.COM>
To: Dan Egli <dan@eglifamily.dnsalias.net>
Cc: linux-kernel@vger.kernel.org, ОлегДрокин <Green@LinuxHacker.RU>
Subject: Re: 2.6.x breaks some Berkeley/Sleepycat DB functionality
Date: Tue, 13 Jan 2004 12:53:16 +0300	[thread overview]
Message-ID: <16387.49164.269996.500699@laputa.namesys.com> (raw)
In-Reply-To: <4002D65C.1010505@eglifamily.dnsalias.net>

Dan Egli writes:
 > -----BEGIN PGP SIGNED MESSAGE-----
 > Hash: SHA1
 > 
 > I have encountered a strange issue in 2.6.0 and 2.6.1
 > 
 > 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?

 > 
 > - --- Dan

Nikita.


  parent reply	other threads:[~2004-01-13  9:53 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 [this message]
2004-01-13 10:10   ` Oleg Drokin
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=16387.49164.269996.500699@laputa.namesys.com \
    --to=nikita@namesys.com \
    --cc=Green@LinuxHacker.RU \
    --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;
as well as URLs for NNTP newsgroup(s).