From: Shawn <core@enodev.com>
To: William Lee Irwin III <wli@holomorphy.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@digeo.com>
Subject: Re: odd db4 error with 2.5.69-mm4 [was Re: Huraaa for 2.5]
Date: 13 May 2003 21:24:23 -0500 [thread overview]
Message-ID: <1052879063.3569.31.camel@www.enodev.com> (raw)
In-Reply-To: <20030514021826.GI8978@holomorphy.com>
Thanks for all the help! So, is it that there is likely misuse of
O_DIRECT somewhere (db4, rpm, etc)?
Wonder if I should bother filing a bug if rpm has a bugzilla...
On Tue, 2003-05-13 at 21:18, William Lee Irwin III wrote:
> They appear to either not be running in equivalent environments or
> something has gone horribly wrong. The diff is incredibly noisy and not
> useful for debugging, could you strace the working kernel's bit as root?
>
> Also, things start getting wildly different after both examine DB_CONFIG,
> where 2.4 and 2.5 open different files with different options, i.e. 2.5
> does O_DIRECT on /var/lib/rpm/__db.001 and 2.4 never touches that file,
> and 2.4 never does O_DIRECT either.
>
> This may very well have something to do with the difference in
> privileges.
next prev parent reply other threads:[~2003-05-14 2:13 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-13 22:54 Huraaa for 2.5 Shawn
2003-05-14 1:27 ` William Lee Irwin III
2003-05-14 1:52 ` odd db4 error with 2.5.69-mm4 [was Re: Huraaa for 2.5] Shawn
2003-05-14 2:01 ` William Lee Irwin III
2003-05-14 2:06 ` Andrew Morton
2003-05-14 2:05 ` Shawn
2003-05-14 2:18 ` William Lee Irwin III
2003-05-14 2:24 ` Shawn [this message]
2003-05-14 2:27 ` William Lee Irwin III
2003-05-14 2:32 ` J Sloan
2003-05-14 2:47 ` Shawn
2003-05-14 2:51 ` Shawn
2003-05-14 3:24 ` J Sloan
2003-05-14 7:38 ` Matti Aarnio
2003-05-14 12:49 ` Tom Sightler
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=1052879063.3569.31.camel@www.enodev.com \
--to=core@enodev.com \
--cc=akpm@digeo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=wli@holomorphy.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