From: Milan Broz <mbroz@redhat.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] Re: Problems running my home-built LVM2
Date: Tue, 17 Feb 2009 08:31:04 +0100 [thread overview]
Message-ID: <499A67B8.8070507@redhat.com> (raw)
In-Reply-To: <jwv7i3p24qp.fsf-monnier+gmane.linux.lvm.general@gnu.org>
Stefan Monnier wrote:
>>> _io in dev-io.c) would often return garbage (tho not always). Not sure
>>> if it's a problem in LVM2, or in uClibc, or in the kernel, but I think
>>> I've already wasted more than enough time on this, so I'll just use
>>> the --disable-o_direct workaround.
>> We had a problem with O-direct several years ago which we blamed on a rogue
>> version of gcc.
>
> Based on my experience I'd say that it seems to still be around.
> At least on `mipsel'. I have since discovered that Debian's `lvm2'
> package disables O_DIRECT with the following lines:
>
> ifneq (,$(findstring $(DEB_HOST_ARCH), arm armeb hppa mips mipsel))
> CONFIGURE_FLAGS += --disable-o_direct
> endif
Ah, ok. That explains why my test on i686 arch & uClibc works:)
This really seems like problem unrelated to LVM2,
is possible that O_DIRECT is just buggy on ARM & similar archs
see http://lkml.org/lkml/2008/11/19/300 for example...
Milan
--
mbroz@redhat.com
next prev parent reply other threads:[~2009-02-17 7:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-06 15:36 [linux-lvm] Problems running my home-built LVM2 Stefan Monnier
2009-02-08 14:11 ` Milan Broz
2009-02-09 16:28 ` [linux-lvm] " Stefan Monnier
2009-02-09 16:32 ` Bryn M. Reeves
2009-02-16 23:20 ` Stefan Monnier
2009-02-17 0:06 ` Alasdair G Kergon
2009-02-17 2:16 ` Stefan Monnier
2009-02-17 7:31 ` Milan Broz [this message]
2009-02-17 13:46 ` Stefan Monnier
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=499A67B8.8070507@redhat.com \
--to=mbroz@redhat.com \
--cc=linux-lvm@redhat.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;
as well as URLs for NNTP newsgroup(s).