* [linux-lvm] bug: raid1 sub-devices are scanned too
@ 2002-02-22 19:55 Erkki Seppala
2002-02-23 4:47 ` Heinz J . Mauelshagen
0 siblings, 1 reply; 5+ messages in thread
From: Erkki Seppala @ 2002-02-22 19:55 UTC (permalink / raw)
To: linux-lvm
Whether the bugzilla is publicly open is unclear to me, atleast there
didn't seem to be a link there in sistina.com/lvm - or I didn't find
it.
Actually I'm not sure if there is a real reason to fix this, as it
would need making vgscan understand more about the raid-stuff, but it
sure does look confusing. Perhaps a generic facility to "blind out"
devices from it? Perhaps this kind of capability should be in the
kernel, not just for LVM..
I recently had a problem with a volume group reusing an existing
logical volume number, but I resolved that, as vgscan suggested, with
vgexport/vgimport. However, this bug appeared:
vgscan -- reading all physical volumes (this may take a while...)
vgscan -- found active volume group "mirror"
vgscan -- found active volume group "ibm9"
vgscan -- found active volume group "archive"
vgscan -- found inactive volume group "mirrorPV_EXP"
vgscan -- ERROR: VG "mirrorPV_EXP" reuses an existing VG number; please vgexport/vgimport that VG or use option -f
vgscan -- "/etc/lvmtab" and "/etc/lvmtab.d" successfully created
vgscan -- WARNING: This program does not do a VGDA backup of your volume groups
I imagine this is because /dev/md/1 is raid1 and consists of
/dev/ide/host0/bus1/target1/lun0/part1 and
/dev/ide/host0/bus0/target1/lun0/part1. Output of pvscan:
pvscan -- reading all physical volumes (this may take a while...)
pvscan -- ACTIVE PV "/dev/md/1" of VG "mirror" [55.91 GB / 13.89 GB free]
pvscan -- inactive PV "/dev/ide/host0/bus1/target1/lun0/part1" is in EXPORTED VG "mirror" [55.91 GB / 13.89 GB free]
pvscan -- inactive PV "/dev/ide/host0/bus0/target1/lun0/part1" is in EXPORTED VG "mirror" [55.91 GB / 13.89 GB free]
pvscan -- total: 6 [311.82 GB] / in use: 5 [290.79 GB] / in no VG: 1 [21.03 GB]
(some lines removed)
I run kernel 2.4.16 and LVM-tools from today's CVS.
Btw, during the original repairing I saw a situation where one of my
volume groups (archive) was twice in /proc/lvm/global. That's not
healthy, is it? I imagine it had something to do with the fact that
after scanning volume group "archive" it failed to scan volume group
"mirror" (due to the reuse-problem), and I kept trying different
stuff..
--
_____________________________________________________________________
/ __// /__ ____ __ Erkki Sepp�l�\ \
/ /_ / // // /\ \/ //ircnet Modeemi Ry\ /
/_/ /_/ \___/ /_/\_\@modeemi.fi http://www.modeemi.fi/~flux/
^ permalink raw reply [flat|nested] 5+ messages in thread* Re: [linux-lvm] bug: raid1 sub-devices are scanned too
2002-02-22 19:55 [linux-lvm] bug: raid1 sub-devices are scanned too Erkki Seppala
@ 2002-02-23 4:47 ` Heinz J . Mauelshagen
2002-02-23 4:55 ` Heinz J . Mauelshagen
0 siblings, 1 reply; 5+ messages in thread
From: Heinz J . Mauelshagen @ 2002-02-23 4:47 UTC (permalink / raw)
To: linux-lvm
Erkkhi,
this is a bug in 1.0.3 with exported VGs.
If you import your VG "mirror" again, you should be fine.
Rather than imprting, "vgscan -f" should work as well.
Will look into it.
Regards,
Heinz -- The LVM Guy --
On Sat, Feb 23, 2002 at 03:55:05AM +0200, Erkki Seppala wrote:
> Whether the bugzilla is publicly open is unclear to me, atleast there
> didn't seem to be a link there in sistina.com/lvm - or I didn't find
> it.
>
> Actually I'm not sure if there is a real reason to fix this, as it
> would need making vgscan understand more about the raid-stuff, but it
> sure does look confusing. Perhaps a generic facility to "blind out"
> devices from it? Perhaps this kind of capability should be in the
> kernel, not just for LVM..
>
> I recently had a problem with a volume group reusing an existing
> logical volume number, but I resolved that, as vgscan suggested, with
> vgexport/vgimport. However, this bug appeared:
>
> vgscan -- reading all physical volumes (this may take a while...)
> vgscan -- found active volume group "mirror"
> vgscan -- found active volume group "ibm9"
> vgscan -- found active volume group "archive"
> vgscan -- found inactive volume group "mirrorPV_EXP"
> vgscan -- ERROR: VG "mirrorPV_EXP" reuses an existing VG number; please vgexport/vgimport that VG or use option -f
> vgscan -- "/etc/lvmtab" and "/etc/lvmtab.d" successfully created
> vgscan -- WARNING: This program does not do a VGDA backup of your volume groups
>
> I imagine this is because /dev/md/1 is raid1 and consists of
> /dev/ide/host0/bus1/target1/lun0/part1 and
> /dev/ide/host0/bus0/target1/lun0/part1. Output of pvscan:
>
> pvscan -- reading all physical volumes (this may take a while...)
> pvscan -- ACTIVE PV "/dev/md/1" of VG "mirror" [55.91 GB / 13.89 GB free]
> pvscan -- inactive PV "/dev/ide/host0/bus1/target1/lun0/part1" is in EXPORTED VG "mirror" [55.91 GB / 13.89 GB free]
> pvscan -- inactive PV "/dev/ide/host0/bus0/target1/lun0/part1" is in EXPORTED VG "mirror" [55.91 GB / 13.89 GB free]
> pvscan -- total: 6 [311.82 GB] / in use: 5 [290.79 GB] / in no VG: 1 [21.03 GB]
>
> (some lines removed)
>
> I run kernel 2.4.16 and LVM-tools from today's CVS.
>
> Btw, during the original repairing I saw a situation where one of my
> volume groups (archive) was twice in /proc/lvm/global. That's not
> healthy, is it? I imagine it had something to do with the fact that
> after scanning volume group "archive" it failed to scan volume group
> "mirror" (due to the reuse-problem), and I kept trying different
> stuff..
>
> --
> _____________________________________________________________________
> / __// /__ ____ __ Erkki Seppälä\ \
> / /_ / // // /\ \/ //ircnet Modeemi Ry\ /
> /_/ /_/ \___/ /_/\_\@modeemi.fi http://www.modeemi.fi/~flux/
>
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@sistina.com
> http://lists.sistina.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://www.sistina.com/lvm/Pages/howto.html
*** Software bugs are stupid.
Nevertheless it needs not so stupid people to solve them ***
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Heinz Mauelshagen Sistina Software Inc.
Senior Consultant/Developer Am Sonnenhang 11
56242 Marienrachdorf
Germany
Mauelshagen@Sistina.com +49 2626 141200
FAX 924446
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
^ permalink raw reply [flat|nested] 5+ messages in thread* Re: [linux-lvm] bug: raid1 sub-devices are scanned too
2002-02-23 4:47 ` Heinz J . Mauelshagen
@ 2002-02-23 4:55 ` Heinz J . Mauelshagen
2002-02-24 16:17 ` Erkki Seppala
0 siblings, 1 reply; 5+ messages in thread
From: Heinz J . Mauelshagen @ 2002-02-23 4:55 UTC (permalink / raw)
To: linux-lvm
On Sat, Feb 23, 2002 at 11:47:12AM +0100, Heinz J . Mauelshagen wrote:
>
> Erkkhi,
>
> this is a bug in 1.0.3 with exported VGs.
>
> If you import your VG "mirror" again, you should be fine.
> Rather than imprting, "vgscan -f" should work as well.
>
> Will look into it.
Are /dev/ide/host0/bus1/target1/lun0/part1 and
/dev/ide/host0/bus0/target1/lun0/part1 really the ones making up /dev/md/1 ?
Regards,
Heinz -- The LVM Guy --
>
> Regards,
> Heinz -- The LVM Guy --
>
>
> On Sat, Feb 23, 2002 at 03:55:05AM +0200, Erkki Seppala wrote:
> > Whether the bugzilla is publicly open is unclear to me, atleast there
> > didn't seem to be a link there in sistina.com/lvm - or I didn't find
> > it.
> >
> > Actually I'm not sure if there is a real reason to fix this, as it
> > would need making vgscan understand more about the raid-stuff, but it
> > sure does look confusing. Perhaps a generic facility to "blind out"
> > devices from it? Perhaps this kind of capability should be in the
> > kernel, not just for LVM..
> >
> > I recently had a problem with a volume group reusing an existing
> > logical volume number, but I resolved that, as vgscan suggested, with
> > vgexport/vgimport. However, this bug appeared:
> >
> > vgscan -- reading all physical volumes (this may take a while...)
> > vgscan -- found active volume group "mirror"
> > vgscan -- found active volume group "ibm9"
> > vgscan -- found active volume group "archive"
> > vgscan -- found inactive volume group "mirrorPV_EXP"
> > vgscan -- ERROR: VG "mirrorPV_EXP" reuses an existing VG number; please vgexport/vgimport that VG or use option -f
> > vgscan -- "/etc/lvmtab" and "/etc/lvmtab.d" successfully created
> > vgscan -- WARNING: This program does not do a VGDA backup of your volume groups
> >
> > I imagine this is because /dev/md/1 is raid1 and consists of
> > /dev/ide/host0/bus1/target1/lun0/part1 and
> > /dev/ide/host0/bus0/target1/lun0/part1. Output of pvscan:
> >
> > pvscan -- reading all physical volumes (this may take a while...)
> > pvscan -- ACTIVE PV "/dev/md/1" of VG "mirror" [55.91 GB / 13.89 GB free]
> > pvscan -- inactive PV "/dev/ide/host0/bus1/target1/lun0/part1" is in EXPORTED VG "mirror" [55.91 GB / 13.89 GB free]
> > pvscan -- inactive PV "/dev/ide/host0/bus0/target1/lun0/part1" is in EXPORTED VG "mirror" [55.91 GB / 13.89 GB free]
> > pvscan -- total: 6 [311.82 GB] / in use: 5 [290.79 GB] / in no VG: 1 [21.03 GB]
> >
> > (some lines removed)
> >
> > I run kernel 2.4.16 and LVM-tools from today's CVS.
> >
> > Btw, during the original repairing I saw a situation where one of my
> > volume groups (archive) was twice in /proc/lvm/global. That's not
> > healthy, is it? I imagine it had something to do with the fact that
> > after scanning volume group "archive" it failed to scan volume group
> > "mirror" (due to the reuse-problem), and I kept trying different
> > stuff..
> >
> > --
> > _____________________________________________________________________
> > / __// /__ ____ __ Erkki Seppälä\ \
> > / /_ / // // /\ \/ //ircnet Modeemi Ry\ /
> > /_/ /_/ \___/ /_/\_\@modeemi.fi http://www.modeemi.fi/~flux/
> >
> > _______________________________________________
> > linux-lvm mailing list
> > linux-lvm@sistina.com
> > http://lists.sistina.com/mailman/listinfo/linux-lvm
> > read the LVM HOW-TO at http://www.sistina.com/lvm/Pages/howto.html
*** Software bugs are stupid.
Nevertheless it needs not so stupid people to solve them ***
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Heinz Mauelshagen Sistina Software Inc.
Senior Consultant/Developer Am Sonnenhang 11
56242 Marienrachdorf
Germany
Mauelshagen@Sistina.com +49 2626 141200
FAX 924446
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
^ permalink raw reply [flat|nested] 5+ messages in thread* Re: [linux-lvm] bug: raid1 sub-devices are scanned too
2002-02-23 4:55 ` Heinz J . Mauelshagen
@ 2002-02-24 16:17 ` Erkki Seppala
2002-02-25 3:52 ` Heinz J . Mauelshagen
0 siblings, 1 reply; 5+ messages in thread
From: Erkki Seppala @ 2002-02-24 16:17 UTC (permalink / raw)
To: linux-lvm
Hello, thanks for the reply.
The problem seems to have disappeared after a reboot, or then I've
tried the vgscan -f -stuff - vgscan now just seemed to work OK. I
could've sworn I tried that vgscan -f before without too much success,
but, all in all, I imagine it's not worth hunting a bug before one can
find an easily repeatible situation.
On Sat, Feb 23, 2002 at 11:55:29AM +0100, Heinz J . Mauelshagen wrote:
> > this is a bug in 1.0.3 with exported VGs.
> >
> > If you import your VG "mirror" again, you should be fine.
> > Rather than imprting, "vgscan -f" should work as well.
In the original situation vgscan -f was of no help, only the
export/import-trick (and a reboot) allowed me to access the mirror-vg.
> Are /dev/ide/host0/bus1/target1/lun0/part1 and
> /dev/ide/host0/bus0/target1/lun0/part1 really the ones making up /dev/md/1 ?
>
> Regards,
> Heinz -- The LVM Guy --
Yes:
md1 : active raid1 ide/host0/bus1/target1/lun0/part1[1] ide/host0/bus0/target1/lun0/part1[0]
58633216 blocks [2/2] [UU]
--
_____________________________________________________________________
/ __// /__ ____ __ Erkki Sepp�l�\ \
/ /_ / // // /\ \/ //ircnet Modeemi Ry\ /
/_/ /_/ \___/ /_/\_\@modeemi.fi http://www.modeemi.fi/~flux/
^ permalink raw reply [flat|nested] 5+ messages in thread* Re: [linux-lvm] bug: raid1 sub-devices are scanned too
2002-02-24 16:17 ` Erkki Seppala
@ 2002-02-25 3:52 ` Heinz J . Mauelshagen
0 siblings, 0 replies; 5+ messages in thread
From: Heinz J . Mauelshagen @ 2002-02-25 3:52 UTC (permalink / raw)
To: linux-lvm
On Mon, Feb 25, 2002 at 12:16:43AM +0200, Erkki Seppala wrote:
> Hello, thanks for the reply.
>
> The problem seems to have disappeared after a reboot, or then I've
> tried the vgscan -f -stuff - vgscan now just seemed to work OK. I
> could've sworn I tried that vgscan -f before without too much success,
> but, all in all, I imagine it's not worth hunting a bug before one can
> find an easily repeatible situation.
Yes, that's true.
In case you get it reproducable some day, I'ld really appreciate your
VGDA and setup information to drill that one down.
Regards,
Heinz -- The LVM Guy --
>
> On Sat, Feb 23, 2002 at 11:55:29AM +0100, Heinz J . Mauelshagen wrote:
>
> > > this is a bug in 1.0.3 with exported VGs.
> > >
> > > If you import your VG "mirror" again, you should be fine.
> > > Rather than imprting, "vgscan -f" should work as well.
>
> In the original situation vgscan -f was of no help, only the
> export/import-trick (and a reboot) allowed me to access the mirror-vg.
>
> > Are /dev/ide/host0/bus1/target1/lun0/part1 and
> > /dev/ide/host0/bus0/target1/lun0/part1 really the ones making up /dev/md/1 ?
> >
> > Regards,
> > Heinz -- The LVM Guy --
>
> Yes:
> md1 : active raid1 ide/host0/bus1/target1/lun0/part1[1] ide/host0/bus0/target1/lun0/part1[0]
> 58633216 blocks [2/2] [UU]
>
> --
> _____________________________________________________________________
> / __// /__ ____ __ Erkki Seppälä\ \
> / /_ / // // /\ \/ //ircnet Modeemi Ry\ /
> /_/ /_/ \___/ /_/\_\@modeemi.fi http://www.modeemi.fi/~flux/
>
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@sistina.com
> http://lists.sistina.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://www.sistina.com/lvm/Pages/howto.html
*** Software bugs are stupid.
Nevertheless it needs not so stupid people to solve them ***
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Heinz Mauelshagen Sistina Software Inc.
Senior Consultant/Developer Am Sonnenhang 11
56242 Marienrachdorf
Germany
Mauelshagen@Sistina.com +49 2626 141200
FAX 924446
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2002-02-25 3:52 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2002-02-22 19:55 [linux-lvm] bug: raid1 sub-devices are scanned too Erkki Seppala
2002-02-23 4:47 ` Heinz J . Mauelshagen
2002-02-23 4:55 ` Heinz J . Mauelshagen
2002-02-24 16:17 ` Erkki Seppala
2002-02-25 3:52 ` Heinz J . Mauelshagen
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox