Bug 611250

Summary:	lvchange change of local availability does not work
Product:	[openSUSE] openSUSE 11.2	Reporter:	Claus Jeppesen <claus>
Component:	Basesystem	Assignee:	Dong Mao Zhang <dmzhang>
Status:	VERIFIED WONTFIX	QA Contact:	E-mail List <qa-bugs>
Severity:	Normal
Priority:	P5 - None
Version:	Final
Target Milestone:	---
Hardware:	x86-64
OS:	openSUSE 11.2
Whiteboard:
Found By:	---	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description Claus Jeppesen 2010-06-03 07:39:38 UTC

User-Agent:       Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.9) Gecko/20100317 SUSE/3.5.9-0.1.1 Firefox/3.5.9

Using 'lvchange -aln' does not change availability status:

xen11:~ # lvdisplay /dev/eonstor11/test11
  --- Logical volume ---
  LV Name                /dev/eonstor11/test11
  VG Name                eonstor11
  LV UUID                rWR1Xq-VkyN-F6uF-xukW-PpKj-1fCx-5DnAYZ
  LV Write Access        read/write
  LV Status              available
  # open                 0
  LV Size                250.00 GB
  Current LE             64000
  Segments               1
  Allocation             inherit
  Read ahead sectors     auto
  - currently set to     256
  Block device           253:3

xen11:~ # lvchange -aln /dev/eonstor11/test11
xen11:~ # lvdisplay /dev/eonstor11/test11
  --- Logical volume ---
  LV Name                /dev/eonstor11/test11
  VG Name                eonstor11
  LV UUID                rWR1Xq-VkyN-F6uF-xukW-PpKj-1fCx-5DnAYZ
  LV Write Access        read/write
  LV Status              available
  # open                 0
  LV Size                250.00 GB
  Current LE             64000
  Segments               1
  Allocation             inherit
  Read ahead sectors     auto
  - currently set to     256
  Block device           253:3

The underlying device is from a qlogic 2460 HBA.

Reproducible: Always





It seems that using 'dmsetup remove eonstor11-test11' one can change the availability status for the LV.

Comment 1 Xin Wei Hu 2010-06-17 03:29:31 UTC

Hi Claus,
  Yes. It's a known issue.

  lvchange causes a 'change' event, which triggers the udev rules to activate the whole VG again. I'm looking for a solution now.

Thanks.

Comment 2 Dong Mao Zhang 2012-06-29 06:31:53 UTC

close