From: Sebastian Witt <se.witt@gmx.net>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] Endless loop running vgscan
Date: Mon Dec 29 07:51:28 2003 [thread overview]
Message-ID: <3FE7483D.90107@hasw.net> (raw)
In-Reply-To: <20031221233848.M21022@uk.sistina.com>
[-- Attachment #1: Type: text/plain, Size: 800 bytes --]
Alasdair G Kergon wrote:
> On Sun, Dec 21, 2003 at 12:41:34AM +0100, Sebastian Witt wrote:
>
>>Ignoring duplicate PV on /dev/hdg1
>>Found /dev/hdf1 in VG raid_vg
>>Ignoring duplicate PV on /dev/hdf1
>>Found /dev/hdh1 in VG raid_vg
>
>
> Set up a filter in lvm.conf so that LVM2 only sees the RAID devices
> and ignores the constituent devices that make up the RAID devices.
>
> The LVM2 logic isn't clever enough yet always to work out the correct
> device to use. This will get fixed.
Sorry, RAID is a little bit wrong in my case. The harddiscs running on
a Promise RAID-Controller but the RAID-function is disabled and it's
used as a normal IDE controller.
I appended my configuration.
I've also this problem if I use this filter:
filter = [ "a/hd[e-h]1$/", "r/.*/" ]
Regards,
Sebastian
[-- Attachment #2: LVM-VGs-server3 --]
[-- Type: text/plain, Size: 1881 bytes --]
--- Volume group ---
VG Name raid_vg
VG Access read/write
VG Status available/resizable
VG # 0
MAX LV 256
Cur LV 2
Open LV 2
MAX LV Size 255.99 GB
Max PV 256
Cur PV 4
Act PV 4
VG Size 38.15 GB
PE Size 4 MB
Total PE 9766
Alloc PE / Size 9760 / 38.12 GB
Free PE / Size 6 / 24 MB
VG UUID none
--- Logical volume ---
LV Name /dev/raid_vg/ftp_lv
VG Name raid_vg
LV Write Access read/write
LV Status available
LV # 1
# open 1
LV Size 25 GB
Current LE 6400
Allocated LE 6400
Stripes 4
Stripe size (KByte) 64
Allocation next free
Read ahead sectors 1024
Block device 58:0
--- Logical volume ---
LV Name /dev/raid_vg/raid_lv
VG Name raid_vg
LV Write Access read/write
LV Status available
LV # 2
# open 1
LV Size 13.12 GB
Current LE 3360
Allocated LE 3360
Stripes 4
Stripe size (KByte) 64
Allocation next free
Read ahead sectors 1024
Block device 58:1
--- Physical volumes ---
PV Name (#) /dev/hde1 (1)
PV Status available / allocatable
Total PE / Free PE 2440 / 0
PV Name (#) /dev/hdf1 (2)
PV Status available / allocatable
Total PE / Free PE 2442 / 2
PV Name (#) /dev/hdg1 (3)
PV Status available / allocatable
Total PE / Free PE 2442 / 2
PV Name (#) /dev/hdh1 (4)
PV Status available / allocatable
Total PE / Free PE 2442 / 2
next prev parent reply other threads:[~2003-12-29 7:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-20 17:42 [linux-lvm] Endless loop running vgscan Sebastian Witt
2003-12-21 17:40 ` Alasdair G Kergon
2003-12-29 7:51 ` Sebastian Witt [this message]
2003-12-29 8:42 ` Alasdair G Kergon
2003-12-29 10:57 ` Sebastian Witt
2003-12-29 15:10 ` Alasdair G Kergon
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=3FE7483D.90107@hasw.net \
--to=se.witt@gmx.net \
--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.