Re: serious vinum bug in 4-10 RELEASE?-solved?

[Sven Willenberger]

Steve Shorter wrote:
On Mon, Jul 12, 2004 at 06:40:01AM +0930, Greg 'groggy' Lehey wrote:
I see no drives.

	Ideas?

I have concluded that this is the result of somekind
of vinum/hardware incompatibility. The problem in question
occured during the upgrade to faster disks, specifically,
Seagate Cheetah ST318453LC on a DELL 2450. If I swap back
the old Quantum Atlas 36G disk, the problem entirely
disappears. The new disks function ok with UFS partitions
but not vinum. It is 100% repeatable.
Don't know why.
We have had issues with Cheetah U320 harddrives (at least the 10K 80-pin 
varieties on our Supermicro boxes) with a high percentage of drive 
failures ( > 10%) and communications errors across the scsi bus. These 
errors disappear when we reverted back to IBM/Hitachi drives. The 
Seagate issues occur with both FreeBSD 4.x and 5.x series so there is 
something in the Seagate firmware (I believe) that is interacting poorly 
with FreeBSD. We have experienced these issues with vinum setups and 
other configurations where the there are either multiple Seagate drives 
or multiple drives where one of them is a Seagate. Firmware updates did 
not help. I have not had this problem where there is only one drive and 
it occupies da0.

Sven
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: serious vinum bug in 4-10 RELEASE?-solved?

[Steve Shorter]

On Mon, Jul 12, 2004 at 06:40:01AM +0930, Greg 'groggy' Lehey wrote:
> I see no drives.
> 
> > Ideas?
> 

I have concluded that this is the result of somekind
of vinum/hardware incompatibility. The problem in question
occured during the upgrade to faster disks, specifically,
Seagate Cheetah ST318453LC on a DELL 2450. If I swap back
the old Quantum Atlas 36G disk, the problem entirely
disappears. The new disks function ok with UFS partitions
but not vinum. It is 100% repeatable.

Don't know why.

thanx - steve
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: 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 [EMAIL PROTECTED]@^/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

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"