From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mx3.redhat.com (mx3.redhat.com [172.16.48.32]) by int-mx1.corp.redhat.com (8.13.1/8.13.1) with ESMTP id n4SE7vGh016723 for ; Thu, 28 May 2009 10:07:57 -0400 Received: from fela.liber4e.com (fela.liber4e.com [208.77.96.130]) by mx3.redhat.com (8.13.8/8.13.8) with ESMTP id n4SE7dbu022167 for ; Thu, 28 May 2009 10:07:39 -0400 Received: from libermobile.liber4e.home (fela.liber4e.com [127.0.0.1]) (authenticated bits=0) by fela.liber4e.com (8.14.2/8.14.2) with ESMTP id n4SE5ARA009546 for ; Thu, 28 May 2009 15:05:21 +0100 From: jose nuno neto Subject: Re: [linux-lvm] Failed to activate snapshot exception store. Date: Thu, 28 May 2009 14:40:52 +0100 References: <200905261801.49236.jose.neto@liber4e.com> In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="Boundary-00=_lRpHK6VP3LwS8o+" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200905281440.53176.jose.neto@liber4e.com> Reply-To: LVM general discussion and development List-Id: LVM general discussion and development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , List-Id: To: LVM general discussion and development --Boundary-00=_lRpHK6VP3LwS8o+ Content-Type: text/plain; charset="iso-8859-6" Content-Transfer-Encoding: 7bit Hi, Thanks for the reply :-) If I take the --test, yes the snapshot gets created But if I try to create a new VG and after a new LV I get the same error. I can the work I was supposed to do, but would like to understand what's going on...... lvcreate -L 1G -n TEST vg_mysql_bk Aborting. Failed to activate new LV to wipe the start of it. vgdisplay -v vg_mysql_bk Using volume group(s) on command line Finding volume group "vg_mysql_bk" --- Volume group --- VG Name vg_mysql_bk System ID Format lvm2 Metadata Areas 1 Metadata Sequence No 3 VG Access read/write VG Status resizable MAX LV 0 Cur LV 0 Open LV 0 Max PV 0 Cur PV 1 Act PV 1 VG Size 250.00 GB PE Size 4.00 MB Total PE 63999 Alloc PE / Size 0 / 0 Free PE / Size 63999 / 250.00 GB VG UUID orekvq-dWqZ-uXs8-gETe-WkyG-adTO-YHdHPh --- Physical volumes --- PV Name /dev/sdl1 PV UUID pw80TN-xYP2-FY4T-ASWF-PpIe-j6vo-WNQTtG PV Status allocatable Total PE / Free PE 63999 / 63999 On Tuesday 26 May 2009 21:30:40 Jonathan Brassow wrote: > what happens if you remove the '--test' from your command? > > brassow > > On May 26, 2009, at 12:01 PM, jose nuno neto wrote: > > HI > > > > I'm running into some problems with lvm on redhat. > > I'm trying to create a snapshot but gives always a error > > " Aborting. Failed to activate snapshot exception store." > > > > Also when I try to create a new volume and create new logical > > volumes I get the same error > > > > This is the output of the lvcreate -s and vgdisplay > > Any ideas/hints are apreciated > > > > Thanks > > Jose Nuno Neto > > > > > > > > lvcreate --test -L 504M -n SnapTest -i2 -s /dev/vgdb/lvdb02 > > Test mode: Metadata will NOT be updated. > > Using default stripesize 64.00 KB > > Rounding size (63 extents) up to stripe boundary size (64 extents) > > Aborting. Failed to activate snapshot exception store. > > > > > > > > --- Volume group --- > > VG Name vgdb > > System ID > > Format lvm2 > > Metadata Areas 5 > > Metadata Sequence No 126 > > VG Access read/write > > VG Status resizable > > MAX LV 0 > > Cur LV 2 > > Open LV 2 > > Max PV 0 > > Cur PV 5 > > Act PV 5 > > VG Size 249.96 GB > > PE Size 8.00 MB > > Total PE 31995 > > Alloc PE / Size 30976 / 242.00 GB > > Free PE / Size 1019 / 7.96 GB > > VG UUID FqqBnv-EKiI-TXA2-GR3C-b4i0-XTeq-xPxpVa > > > > --- Logical volume --- > > LV Name /dev/vgdb/lvdb01 > > VG Name vgdb > > LV UUID 0F2fNt-m2n5-MpJ8-dMNS-Xwzb-QsvS-LyHefm > > LV Write Access read/write > > LV Status available > > # open 1 > > LV Size 2.00 GB > > Current LE 256 > > Segments 1 > > Allocation inherit > > Read ahead sectors auto > > - currently set to 256 > > Block device 253:4 > > > > --- Logical volume --- > > LV Name /dev/vgdb/lvdb02 > > VG Name vgdb > > LV UUID 7Q038a-7FfX-AhBo-djfL-chFO-MI3N-vzdcbo > > LV Write Access read/write > > LV Status available > > # open 1 > > LV Size 240.00 GB > > Current LE 30720 > > Segments 3 > > Allocation inherit > > Read ahead sectors auto > > - currently set to 256 > > Block device 253:5 > > > > > > > > --- Physical volumes --- > > PV Name /dev/sdh1 > > PV UUID 13EWPc-BeSd-w1ub-wbhM-c3Ff-pi7U-KWDkxr > > PV Status allocatable > > Total PE / Free PE 6399 / 0 > > > > > > > > PV Name /dev/sdi1 > > PV UUID 14OQ42-xq0w-xln5-z9ts-PHKF-goXA-X9qzTE > > PV Status allocatable > > Total PE / Free PE 6399 / 255 > > > > > > > > PV Name /dev/sdj1 > > PV UUID U3h5F6-g6Wt-MNMb-AHyy-BP2R-BWf1-6LNm55 > > PV Status allocatable > > Total PE / Free PE 6399 / 255 > > > > > > > > PV Name /dev/sdk1 > > PV UUID qkpbY5-dvGg-Z1Xb-3cEM-sidS-frbr-pCe8Bk > > PV Status allocatable > > Total PE / Free PE 6399 / 255 > > > > > > > > PV Name /dev/sdb1 > > PV UUID WtDVja-1Q9u-Tgr8-bCU3-qlqS-lahj-m1p2cU > > PV Status allocatable > > Total PE / Free PE 6399 / 254 > > > > > > > > > > -- > > This message has been scanned for viruses and > > dangerous content by MailScanner, and is > > believed to be clean. _______________________________________________ > > linux-lvm mailing list > > linux-lvm@redhat.com > > https://www.redhat.com/mailman/listinfo/linux-lvm > > read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/ -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. --Boundary-00=_lRpHK6VP3LwS8o+ Content-Type: text/html; charset="iso-8859-6" Content-Transfer-Encoding: 7bit Hi,


Thanks for the reply :-)


If I take the --test, yes the snapshot gets created
But if I try to create a new VG and after a new LV I get the same error. I can the work I was supposed to do, but would like to understand what's going on......


lvcreate -L 1G -n TEST vg_mysql_bk
Aborting. Failed to activate new LV to wipe the start of it.


vgdisplay -v vg_mysql_bk
Using volume group(s) on command line
Finding volume group "vg_mysql_bk"
--- Volume group ---
VG Name vg_mysql_bk
System ID
Format lvm2
Metadata Areas 1
Metadata Sequence No 3
VG Access read/write
VG Status resizable
MAX LV 0
Cur LV 0
Open LV 0
Max PV 0
Cur PV 1
Act PV 1
VG Size 250.00 GB
PE Size 4.00 MB
Total PE 63999
Alloc PE / Size 0 / 0
Free PE / Size 63999 / 250.00 GB
VG UUID orekvq-dWqZ-uXs8-gETe-WkyG-adTO-YHdHPh


--- Physical volumes ---
PV Name /dev/sdl1
PV UUID pw80TN-xYP2-FY4T-ASWF-PpIe-j6vo-WNQTtG
PV Status allocatable
Total PE / Free PE 63999 / 63999




On Tuesday 26 May 2009 21:30:40 Jonathan Brassow wrote:
> what happens if you remove the '--test' from your command?
>
> brassow
>
> On May 26, 2009, at 12:01 PM, jose nuno neto wrote:
> > HI
> >
> > I'm running into some problems with lvm on redhat.
> > I'm trying to create a snapshot but gives always a error
> > " Aborting. Failed to activate snapshot exception store."
> >
> > Also when I try to create a new volume and create new logical
> > volumes I get the same error
> >
> > This is the output of the lvcreate -s and vgdisplay
> > Any ideas/hints are apreciated
> >
> > Thanks
> > Jose Nuno Neto
> >
> >
> >
> > lvcreate --test -L 504M -n SnapTest -i2 -s /dev/vgdb/lvdb02
> > Test mode: Metadata will NOT be updated.
> > Using default stripesize 64.00 KB
> > Rounding size (63 extents) up to stripe boundary size (64 extents)
> > Aborting. Failed to activate snapshot exception store.
> >
> >
> >
> > --- Volume group ---
> > VG Name vgdb
> > System ID
> > Format lvm2
> > Metadata Areas 5
> > Metadata Sequence No 126
> > VG Access read/write
> > VG Status resizable
> > MAX LV 0
> > Cur LV 2
> > Open LV 2
> > Max PV 0
> > Cur PV 5
> > Act PV 5
> > VG Size 249.96 GB
> > PE Size 8.00 MB
> > Total PE 31995
> > Alloc PE / Size 30976 / 242.00 GB
> > Free PE / Size 1019 / 7.96 GB
> > VG UUID FqqBnv-EKiI-TXA2-GR3C-b4i0-XTeq-xPxpVa
> >
> > --- Logical volume ---
> > LV Name /dev/vgdb/lvdb01
> > VG Name vgdb
> > LV UUID 0F2fNt-m2n5-MpJ8-dMNS-Xwzb-QsvS-LyHefm
> > LV Write Access read/write
> > LV Status available
> > # open 1
> > LV Size 2.00 GB
> > Current LE 256
> > Segments 1
> > Allocation inherit
> > Read ahead sectors auto
> > - currently set to 256
> > Block device 253:4
> >
> > --- Logical volume ---
> > LV Name /dev/vgdb/lvdb02
> > VG Name vgdb
> > LV UUID 7Q038a-7FfX-AhBo-djfL-chFO-MI3N-vzdcbo
> > LV Write Access read/write
> > LV Status available
> > # open 1
> > LV Size 240.00 GB
> > Current LE 30720
> > Segments 3
> > Allocation inherit
> > Read ahead sectors auto
> > - currently set to 256
> > Block device 253:5
> >
> >
> >
> > --- Physical volumes ---
> > PV Name /dev/sdh1
> > PV UUID 13EWPc-BeSd-w1ub-wbhM-c3Ff-pi7U-KWDkxr
> > PV Status allocatable
> > Total PE / Free PE 6399 / 0
> >
> >
> >
> > PV Name /dev/sdi1
> > PV UUID 14OQ42-xq0w-xln5-z9ts-PHKF-goXA-X9qzTE
> > PV Status allocatable
> > Total PE / Free PE 6399 / 255
> >
> >
> >
> > PV Name /dev/sdj1
> > PV UUID U3h5F6-g6Wt-MNMb-AHyy-BP2R-BWf1-6LNm55
> > PV Status allocatable
> > Total PE / Free PE 6399 / 255
> >
> >
> >
> > PV Name /dev/sdk1
> > PV UUID qkpbY5-dvGg-Z1Xb-3cEM-sidS-frbr-pCe8Bk
> > PV Status allocatable
> > Total PE / Free PE 6399 / 255
> >
> >
> >
> > PV Name /dev/sdb1
> > PV UUID WtDVja-1Q9u-Tgr8-bCU3-qlqS-lahj-m1p2cU
> > PV Status allocatable
> > Total PE / Free PE 6399 / 254
> >
> >
> >
> >
> > --
> > This message has been scanned for viruses and
> > dangerous content by MailScanner, and is
> > believed to be clean. _______________________________________________
> > linux-lvm mailing list
> > linux-lvm@redhat.com
> > https://www.redhat.com/mailman/listinfo/linux-lvm
> > read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/



--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean. --Boundary-00=_lRpHK6VP3LwS8o+--