serious vinum bug in 4-10 RELEASE?

[Steve Shorter]

On Mon, Jul 12, 2004 at 06:40:01AM +0930, Greg 'groggy' Lehey wrote:
> >
> > 	I get the following incorrect configuration. Notice that
> > drives data0 and data1 are missing and drives data2 and data3 are
> > duplicated where data0 and data1 should be.
> 
> I see no drives.

	Not sure what you mean see below
> 
> > 	Ideas?
> 
> http://www.vinumvm.org/vinum/how-to-debug.html

	I recreated a simpler situation with just 2 mirrored
drives.

	After reboot the vinum lv -r -v reports (*missing *)
drives. But before reboot they are there. 


this is the initial vinum lv -r -v. drives data0 and data1 are
clearly listed as mq0.p0.s0 and mq0.p1.s0

Volume mq0:	Size: 18341345792 bytes (17491 MB)
		State: up
		Flags: 
		2 plexes
		Read policy: round robin
Plex mq0.p0:	Size:	18341345792 bytes (17491 MB)
		Subdisks:        1
		State: up
		Organization: concat
		Part of volume mq0

Plex mq0.p1:	Size:	18341345792 bytes (17491 MB)
		Subdisks:        1
		State: up
		Organization: concat
		Part of volume mq0

Subdisk mq0.p0.s0:
		Size:      18341345792 bytes (17491 MB)
		State: up
		Plex mq0.p0 at offset 0 (0  B)
		Drive data0 (/dev/da0d) at offset 135680 (132 kB)

Subdisk mq0.p1.s0:
		Size:      18341345792 bytes (17491 MB)
		State: up
		Plex mq0.p1 at offset 0 (0  B)
		Drive data1 (/dev/da1d) at offset 135680 (132 kB)


this is the vinum lv -r -v. after reboot drives data0 and data1 are
listed as (*missing*)
	
	
Volume mq0:	Size: 18341345792 bytes (17491 MB)
		State: up
		Flags: 
		2 plexes
		Read policy: round robin
Plex mq0.p0:	Size:	18341345792 bytes (17491 MB)
		Subdisks:        1
		State: up
		Organization: concat
		Part of volume mq0

Plex mq0.p1:	Size:	18341345792 bytes (17491 MB)
		Subdisks:        1
		State: up
		Organization: concat
		Part of volume mq0

Subdisk mq0.p0.s0:
		Size:      18341345792 bytes (17491 MB)
		State: up
		Plex mq0.p0 at offset 0 (0  B)
		Drive  (*missing*) at offset 135680 (132 kB)

Subdisk mq0.p1.s0:
		Size:      18341345792 bytes (17491 MB)
		State: up
		Plex mq0.p1 at offset 0 (0  B)
		Drive  (*missing*) at offset 135680 (132 kB)

	
	Here is the on disk configuration, as per your
online script.



IN VINOq0data0 at 7@^<Evolume mq0 state up
plex name mq0.p0 state up org concat vol mq0 
plex name mq0.p1 state up org concat vol mq0 
sd name mq0.p0.s0 drive data0 plex mq0.p0 len 35822941s driveoffset 265s state up plexoffset 0s 
sd name mq0.p1.s0 drive data1 plex mq0.p1 len 35822941s driveoffset 265s state up plexoffset 0s 

IN VINOq0data1 at Z@g<Evolume mq0 state up
plex name mq0.p0 state up org concat vol mq0 
plex name mq0.p1 state up org concat vol mq0 
sd name mq0.p0.s0 drive data0 plex mq0.p0 len 35822941s driveoffset 265s state up plexoffset 0s 
sd name mq0.p1.s0 drive data1 plex mq0.p1 len 35822941s driveoffset 265s state up plexoffset 0s 


	Also, this seems wierd if, I do vinum rm -rf mq0 and or
vinum resetconfig. vinum still detects the volumes mq0 on reboot.
if I do 

	dd </dev/zero >/dev/da0d count=300

vinum no longer detects any volumes, vinum lv is blank, BUT
your script to read the vinum config on disk shows the same
vinum config above. If I change the fstype from vinum to 4.2BSD
and newfs the partition its still there. Is this possible?

	Also on boot vinum  reports

vinum: loaded
vinum: no drives found
vinum_scandisk() returned 2vinum: no drives found
** no drives found **: no such file or directory


	Any other info required, just ask.


	-steve




	"The age of the Internet has a right to its own music"


		http://www.linuxsuite.org