From: raoul bhatia <r.bhatia@ipax.tk>
To: linux-lvm@redhat.com
Subject: Re: [linux-lvm] mdraid, pvcreate and vgcreate problem
Date: Mon Mar 1 05:16:00 2004 [thread overview]
Message-ID: <40430DBE.5020105@ipax.tk> (raw)
In-Reply-To: <40427F2B.7000507@ipax.tk>
ok, i found the problem. i'm mixed using devfsd, and somehow, i forgot
that you have to use /dev/md/1 instead of /dev/md1 when working with
lvm. so i have to say sorry for my last email!
best regards,
raoul bhatia
raoul bhatia wrote:
> hi!
>
> i've ran into some problems with mdraid and lvm. as i guess that log
> messages will give you more information than i might do, i will begin:
>
> i've got an identical setup on another server, which works flawlessly.
> as i don't know, where these problems might originate from, i hope that
> you can help me!
>
> best regards,
> raoul bhatia
>
> yellow:~# cat /proc/mdstat
> Personalities : [linear] [raid0] [raid1] [raid5]
> read_ahead 1024 sectors
> md3 : active raid1 ide/host0/bus1/target0/lun0/part3[1]
> ide/host0/bus0/target0/lun0/part3[0]
> 489856 blocks [2/2] [UU]
>
> md0 : active raid1 ide/host0/bus1/target0/lun0/part5[1]
> ide/host0/bus0/target0/lun0/part5[0]
> 979840 blocks [2/2] [UU]
>
> md1 : active raid1 ide/host0/bus1/target0/lun0/part6[1]
> ide/host0/bus0/target0/lun0/part6[0]
> 37069888 blocks [2/2] [UU]
>
> unused devices: <none>
>
> yellow:~# pvcreate -v /dev/md1
> pvcreate -- locking logical volume manager
> pvcreate -- checking physical volume name "/dev/md1"
> pvcreate -- getting physical volume size
> pvcreate -- checking maximum physical volume size
> pvcreate -- checking partition type
> pvcreate -- creating new physical volume
> pvcreate -- setting up physical volume for /dev/md1 with 74139776 sectors
> pvcreate -- writing physical volume data to disk "/dev/md1"
> pvcreate -- physical volume "/dev/md1" successfully created
> pvcreate -- unlocking logical volume manager
>
> yellow:~# pvdisplay /dev/md1
> pvdisplay -- "/dev/md1" is a new physical volume of 35.35 GB
>
> yellow:~# pvdata -v /dev/md1
> --- NEW Physical volume ---
> PV Name /dev/md1
> VG Name
> PV Size 35.35 GB [74139776 secs]
> PV# 0
> PV Status NOT available
> Allocatable NO
> Cur LV 0
> PE Size (KByte) 0
> Total PE 0
> Free PE 0
> Allocated PE 0
> PV UUID FzRQMD-gyz0-xB06-iP2s-Pog2-4MtC-lYSuab
>
> yellow:~# vgcreate -v vg0 /dev/md1
> vgcreate -- checking volume group name
> vgcreate -- checking volume group directory existence
> vgcreate -- locking logical volume manager
> vgcreate -- checking volume group "vg0" existence
> vgcreate -- counting all existing volume groups
> vgcreate -- reading all physical volume data from disks
> vgcreate -- checking if all given physical volumes in command line are new
> vgcreate -- checking physical volumes name "/dev/md1"
> vgcreate -- no valid physical volumes in command line
--
____________________________________________________________________
raoul bhatia email. r.bhatia@ipax.tk
- ipax.tk - web. http://www.ipax.tk
chief technician, support irc. #ipax (quakenet)
____________________________________________________________________
prev parent reply other threads:[~2004-03-01 10:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-29 23:24 [linux-lvm] mdraid, pvcreate and vgcreate problem raoul bhatia
2004-03-01 5:16 ` raoul bhatia [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=40430DBE.5020105@ipax.tk \
--to=r.bhatia@ipax.tk \
--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