And delete the lvm cache before the scan, if you haven't already.
--
Dave
On May 3, 8:33 pm, dave wrote:
> IIRC, LVM was wonky when I tried to fix something similar to this.
> Assuming you only want the partitions on sda, sdb, sdc and the
> multipath devices, try:
>
> filter = [ "a|/dev/dm-*|",
IIRC, LVM was wonky when I tried to fix something similar to this.
Assuming you only want the partitions on sda, sdb, sdc and the
multipath devices, try:
filter = [ "a|/dev/dm-*|", "a|/dev/sda[0-9]|", "a|/dev/sdb[0-9]|", "a|/
dev/sdc[0-9]|", "r|.*|" ]
--
Dave
On May 3, 2:45 pm, James Hammer wro
On 05/03/10 15:30, James Hammer wrote:
On 05/03/10 13:39, Romeo Theriault wrote:
How can I resolve the "Found duplicate PV" warning/error?
It looks like this link should be able to help you.
http://kbase.redhat.com/faq/docs/DOC-2991
Essentially you'll want to create a filter in your lv
On 05/03/10 13:39, Romeo Theriault wrote:
How can I resolve the "Found duplicate PV" warning/error?
It looks like this link should be able to help you.
http://kbase.redhat.com/faq/docs/DOC-2991
Essentially you'll want to create a filter in your lvm.conf file so it
only scans your multi
By offline, did you mean the disk was offline on the target side? if
so, do you know what type of target you're using open-iscsi against?
If that is iscsi enterprise target, you can edit the configure file /
etc/ietd.conf on the target side properly and restart the target
service by "/etc/init.d/is
>
> How can I resolve the "Found duplicate PV" warning/error?
>
>
It looks like this link should be able to help you.
http://kbase.redhat.com/faq/docs/DOC-2991
Essentially you'll want to create a filter in your lvm.conf file so it only
scans your multipathed disks. From your error you see it is a
On a linux server I connect to 5 iscsi disks hosted by a SAN. I have
multipathing setup. On each multipath device I used pvcreate to create
a physical volume with no problems. When I create the 6th disk I get
the following from pvdisplay:
# pvcreate /dev/dm-18
Physical volume "/dev/dm-18"
Hi group,
I have been tracing the code related to sending PDUs from iscsi
initiator (ver 2.0-871).
And through some printk()s i realize that starting from
iscsi_sw_tcp_pdu_init(), all the functions using scatterlist (struct
scatterlist *sg) seem to use 4096 as the length (sg->length).
But I was
