Linux LVM users
 help / color / mirror / Atom feed
From: Michael Tokarev <mjt@tls.msk.ru>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] Using Oracle with lvm AND rawio: read(512) from
Date: Mon, 04 Dec 2000 18:16:36 +0300	[thread overview]
Message-ID: <3A2BB554.2D83919E@tls.msk.ru> (raw)
In-Reply-To: 3A2BADF1.A12C700A@tls.msk.ru

Michael Tokarev wrote:
> 
[]
> 
> Changed BLOCK_SIZE to 512 (from 1024) and recompiled.
> Lvm won't work anymore at all, any i/o (read/write) on
> any lv gives "no such device or address" error...
> 
> Any ideas? :(((

Oh, my bad, I'm sorry!..  It worked with BLOCK_SIZE=512, I forgot to
vgchange -ay !

So, with BLOCK_SIZE=512, it is ok, and dd ... bs=512 is also ok.
With 1024, it won't work with invalid argument.

What I noticied also is that regardless of actual block size
used in lvm, stat() on raw device on top of it reports
st_blksize=4096 (not 512 nor 1024) -- is this Ok?

And -- Jorg de Jong, can you please strace the ts creation
process?  I'm very interested on i/o buffer sizes used there.

If e.g. your ORACLE_SID=orcl, do the following:

  oracle> sqlplus internal/
  SQL>

then in other window/terminal, find pid of "oracleorcl"
(oracle$ORACLE_SID) process started by sqlplus:
  # ps -fu oracle
  ...
  oracle   14343 13857  0 18:02 pts/3    00:00:00 sqlplus
  oracle   14344 14343  0 18:02 ?        00:00:00 oracleorcl (DESCRIPTION=(LOCAL=...
           ^^^^^ ^^^^^                            ^^^^^^^^^^
and do the following:
  [ other window ]
  # strace -o trc -v -p 14344 ($PID of that process)

  [ sqlplus window ]
  SQL> create tablespace ... ;

  [ other window ]
  ^C
  # _  

Then examine `trc' file made by strace.  I'm interested in:
 1) st_blksize of /dev/raw/rawNN device
 2) read/write sizes requested by oracle on that device.

And also try:
  dd of=/dev/null if=/dev/raw/raw100 bs=512
   and the same with bs=1024
  (this will not destroy data)
 (/dev/raw/raw100 bound to one of LVs).

If you successefully created the tablespace, then
either oracle uses only 1024*n i/o (my 8.1.6 uses 512
sometimes) or your kernel allows to use 512 bytes...

Thank you!

Regards,
 Michael.

  reply	other threads:[~2000-12-04 15:16 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-12-01 21:28 [linux-lvm] Using Oracle with lvm AND rawio: read(512) from /dev/raw/ Michael Tokarev
2000-12-01 23:22 ` Andreas Dilger
2000-12-02  0:35   ` Michael Ju. Tokarev
2000-12-02  5:29     ` [linux-lvm] Using Oracle with lvm AND rawio: read(512) from Andreas Dilger
2000-12-02 23:24       ` Michael Ju. Tokarev
2000-12-03  1:34         ` Michael Ju. Tokarev
2000-12-04  8:42           ` Michael Ju. Tokarev
2000-12-04 14:14             ` Jorg de Jong
2000-12-04 14:42               ` Michael Tokarev
2000-12-04 14:45             ` Michael Tokarev
2000-12-04 15:16               ` Michael Tokarev [this message]
2000-12-04 19:35                 ` Jorg de Jong
2000-12-04 20:01                   ` [linux-lvm] Final Q: i/o with 512 bytes: lvm+raw... [was: Oracle, lvm, rawio, ...] Michael Tokarev
2000-12-02 10:45     ` [linux-lvm] Using Oracle with lvm AND rawio: read(512) from /dev/raw/ Christoph Hellwig
2000-12-02 20:46 ` Jorg de Jong

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=3A2BB554.2D83919E@tls.msk.ru \
    --to=mjt@tls.msk.ru \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox