All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gary Eheman <eheman@funsoft.com>
To: linux-lvm@sistina.com
Subject: Re: dd and raw devices with lvm  [was:  Re: [linux-lvm] LVM hang with  some uses of raw i/o]
Date: Wed Jul  3 12:16:02 2002	[thread overview]
Message-ID: <3D2330BF.AB9221B8@funsoft.com> (raw)
In-Reply-To: 20020703193224.D999@portatile.milano.dt

Eike:
  The "bug" with dd and raw devices is in the man page for the raw command. That
is "man raw".  I am pasting what it says on a RedHat 7.2 distribution:
BUGS
       The  Linux  dd  (1)  command  does not currently align its
       buffers correctly, and so cannot be used on raw devices.

       Raw I/O devices do not maintain cache coherency  with  the
       Linux  block  device  buffer cache.  If you use raw I/O to
       overwrite data already in the  buffer  cache,  the  buffer
       cache  will  no  longer  correspond to the contents of the
       actual storage device underneath.  This is deliberate, but
       is regarded either a bug or a feature depending on who you
       ask!

I am still having the same problem.  One of my colleagues managed to reproduce
the problem on a system that he has direct access to. The system that is failing
for me is remote and it is difficult to find someone to go reset the server once
linux hangs. I am hoping my colleague can get a handle on it soon so that we can
confirm whether or not it is a problem with raw i/o in general, LVM and raw, or
our own code.

Eike Kowallik wrote:
> 
> Hello!
> 
> On Wed, Jun 26, 2002 at 01:28:00PM -0400, Gary Eheman wrote:
> 
> > utilities (I think), though I also see that dd is not supposed to be used
> > against raw devices in the man pages.  The author of our utility is well aware
> > of the need to align the buffers, and the same code does work on other raw
> > devices on other LVM linux systems I have put together.
> 
> I waited some days, but nobody wrote something about dd and raw
> devices...
> 
> I read the dd man pages on two Linux Systems - and the newest
> one from the fileutils Version 4.1:
> http://www.gnu.org/directory/All_GNU_Packages/fileutils.html
> But I couldn't find any note about (problems with) raw devices.
> 
> Grey, would you give me a hint? Anybody else? I'm asking here
> because I used dd to find out more about my problems with
> lvm and raw devices (for Oracle RAC):
> http://lists.sistina.com/pipermail/linux-lvm/2002-June/011737.html
> 
> Thanks in advance, Eike
> 
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@sistina.com
> http://lists.sistina.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://www.sistina.com/lvm/Pages/howto.html

-- 
Gary Eheman
Fundamental Software, Inc.
http://www.funsoft.com

      reply	other threads:[~2002-07-03 12:16 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-26 12:30 [linux-lvm] LVM hang with some uses of raw i/o Gary Eheman
2002-06-26 12:37 ` Gary Eheman
2002-06-27  4:52 ` Heinz J . Mauelshagen
2002-06-27  7:42   ` bscott
2002-06-27  8:43     ` Heinz J . Mauelshagen
2002-07-03 11:52 ` dd and raw devices with lvm [was: Re: [linux-lvm] LVM hang with some uses of raw i/o] Eike Kowallik
2002-07-03 12:16   ` Gary Eheman [this message]

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=3D2330BF.AB9221B8@funsoft.com \
    --to=eheman@funsoft.com \
    --cc=linux-lvm@sistina.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.