Opened 13 years ago

Closed 13 years ago

#4 closed defect (fixed)

Search for VG's in analyse-my-lvm

Reported by: bbaumer@… Owned by: Bruno Cornec
Priority: normal Milestone: 2.2.0
Component: mindi Version: 2.0.8
Severity: normal Keywords:
Cc: andree@…

Description

The analyse-my-lvm Script find VG like system an oldsytem as one VG. Therefore it will create VG's with PV's of both.

Change History (6)

comment:1 Changed 13 years ago by bbaumer@…

Status: newassigned

I added 2 blanks to grep in the Function "ProcessVolumeGroup()". The search String is now "list_of_devices=lvm pvs | grep " $current_VG " | awk '{print $1}'`" in the Function "ProcessVolumeGroup?()".

comment:2 Changed 13 years ago by Bruno Cornec

Could you give me the result of the lvm pvs on your system so that I can check potential impacts of your modification ?

comment:3 Changed 13 years ago by Bruno Cornec

Could you please check that this bug is solved by the latest version of Mondo Rescue (2.0.9) available at ftp://ftp.mondorescue.org ?

comment:4 Changed 13 years ago by Bruno Cornec

Cc: andree@… added
Milestone: 2.2.0

Andree, if you stil have you test LVM environemnet, could you test if this is still valid with 2.2.0~834 and close if not. TIA, Bruno.

comment:5 Changed 13 years ago by bbaumer@…

Component: mondomindi

The Bug is not solved in Rev 840. The line submitted is still the same. I tried it anyway, but the failure is still there.


Output from analyze-my-lvm:

Create and activate the VG's (volume groups). # lvm vgcreate oldhome1 -l 0 -p 0 -s 4m /dev/hdb6 # lvm vgchange -a y oldhome1 # lvm vgcreate logs -l 0 -p 0 -s 4m /dev/hda7 # lvm vgchange -a y logs # lvm vgcreate store -l 0 -p 0 -s 4m /dev/sda6 # lvm vgchange -a y store # lvm vgcreate storage -l 0 -p 0 -s 4m /dev/hda6 # lvm vgchange -a y storage # lvm vgcreate system -l 0 -p 0 -s 4m /dev/sda5 # lvm vgchange -a y system # lvm vgcreate home1 -l 0 -p 0 -s 4m /dev/hda5 /dev/hdb6 <---- /dev/hdb6 belongs to oldhome1; see above # lvm vgchange -a y home1

comment:6 Changed 13 years ago by Bruno Cornec

Resolution: fixed
Status: assignedclosed

Thanks for your feedback. I applied your patch to rev [850]

Hope there is no collision with something else.

Note: See TracTickets for help on using tickets.