All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Bryn M. Reeves" <bmr@redhat.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Cc: Jewsco Pius Jacquez <JewscoPius.Jacquez@Amdocs.com>
Subject: Re: [linux-lvm] Question, what is the first 384 cyclinder in the PV?
Date: Mon, 01 Aug 2011 10:24:16 +0100	[thread overview]
Message-ID: <4E3670C0.1070503@redhat.com> (raw)
In-Reply-To: <883D98939E388E429EE8D771168A6560027ED144AF@USCMIMAIL1.corp.amdocs.com>

On 07/29/2011 06:35 PM, Jewsco Pius Jacquez wrote:
> I’m sorry, I mean the first 384 sector.

It's space reserved for lvm2 data used to manage the volume; This part of the
device contains the LVM2 label and metadata area. (it's before the first
physical extent in the volume).

> I am using RHEL5.6 kernel 2.6.18-238.12.1.el5 and have lvm2-2.02.74-5.el5. Here 
> is my lvm.conf.
> 
> Can an application data exist here? Like oracle data..

Not generally but lvm2 does not necessarily write to every location in this
region when initialising a new device so if there was existing data on the
device when pvcreate/vgcreate ran it will not have been overwritten.

> For instance, if I dd out from a PV with bs=512 and count=384 and I saw oracle 
> data on it, is this ok?

It's not possible to say with this information - has oracle been configured to
use the whole disk?

If so then that's an error but if the data you are seeing is just "stale" data
from a previous use of the device it's not going to cause any problems.

Regards,
Bryn.

  reply	other threads:[~2011-08-01  9:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-29 17:35 [linux-lvm] Question, what is the first 384 cyclinder in the PV? Jewsco Pius Jacquez
2011-08-01  9:24 ` Bryn M. Reeves [this message]
  -- strict thread matches above, loose matches on Subject: below --
2011-07-29 17:38 Jewsco Pius Jacquez
2011-07-29 16:12 Jewsco Pius Jacquez

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=4E3670C0.1070503@redhat.com \
    --to=bmr@redhat.com \
    --cc=JewscoPius.Jacquez@Amdocs.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 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.