Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 17 Sep 2001 12:04:27 +0930
From:      Greg Lehey <grog@FreeBSD.org>
To:        john_wilson100@excite.com
Cc:        freebsd-hackers@freebsd.org
Subject:   Re: VINUM PANIC ON -STABLE
Message-ID:  <20010917120427.M3782@wantadilla.lemis.com>
In-Reply-To: <24460926.1000670447361.JavaMail.imail@doby.excite.com>; from john_wilson100@excite.com on Sun, Sep 16, 2001 at 01:00:41PM -0700
References:  <24460926.1000670447361.JavaMail.imail@doby.excite.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On Sunday, 16 September 2001 at 13:00:41 -0700, john_wilson100@excite.com wrote:
>
> On Sun, 16 Sep 2001 11:42:38 +0930, Greg Lehey wrote:
>
>>> 6) Supply an extract of the file /var/log/messages.
>>>
>>> Sep 12 14:06:10 depot login: ROOT LOGIN (root) ON ttyv0
>>> Sep 12 14:07:29 depot login: ROOT LOGIN (root) ON ttyv1
>>> Sep 13 01:58:14 depot /kernel: vinum: loaded
>>> Sep 13 01:58:15 depot /kernel: vinum: drive data1 is up
>>> Sep 13 01:58:15 depot /kernel: vinum: drive home1 is up
>>> Sep 13 01:58:15 depot /kernel: vinum: drive home2 is up
>>> Sep 13 01:58:15 depot /kernel: vinum: removing 499 blocks of partial
> stripe at the end of data.p0
>>> Sep 13 01:58:15 depot /kernel: vinum: data.p0 must have equal sized
> subdisks
>>> Sep 13 01:58:15 depot /kernel: Correcting length of data.p0: was
> 20970756, is 20970757
>>
>>  I suspect that this is the problem.  I've seen isolated cases where
>>  the stripe size didn't get fixed correctly, leaving holes in the
>>  volume.  Could you send me the output of 'vinum l -v', please?  And
>>  please don't wrap log output, it makes it a pain to read.
>
> Hmm, I don't think I wrapped anything, if you go to
>
>    http://docs.freebsd.org/mail/current/
>
> (or wherever the last week's messages are), you'll see that the log
> output is not wrapped.   It must be your own mailer that wraps it
> on receipt.

Did you read the URL I quoted?  Many MUAs wrap text without telling
you.  mutt, which I use, isn't one of them, and the MTA definitely
doesn't.  It arrived that way.

> Here's the output of "vinum l -v":

> 4 subdisks:
> Subdisk data.p0.s0:
> 		Size:      10737027072 bytes (10239 MB)
> 		State: up
> 		Plex data.p0 at offset 0 (0  B)
> 		Drive data1 (/dev/ad4s1g) at offset 135680 (132 kB)
>
> Subdisk data.p0.s1:
> 		Size:      10737027072 bytes (10239 MB)
> 		State: up
> 		Plex data.p0 at offset 285696 (279 kB)
> 		Drive data2 (/dev/ad6s1e) at offset 135680 (132 kB)

OK, look at these two: they're both the same size, like they should
be.

> Subdisk home.p0.s0:
> 		Size:      40822392320 bytes (38931 MB)
> 		State: up
> 		Plex home.p0 at offset 0 (0  B)
> 		Drive home1 (/dev/ad4s1h) at offset 135680 (132 kB)
>
> Subdisk home.p0.s1:
> 		Size:      39566177280 bytes (37733 MB)
> 		State: up
> 		Plex home.p0 at offset 285696 (279 kB)
> 		Drive home2 (/dev/ad6s1f) at offset 135680 (132 kB)

These ones, though, are different.  That's a bug in Vinum.  You didn't
say, but I assume that it was the newfs of home that caused the crash.

This is directly related to the fact that your two partitions are of
different size:

Drive home1:	Device /dev/ad4s1h
		Created on depot at Thu Sep 13 01:58:14 2001
		Config last updated Sun Sep 16 03:28:31 2001
		Size:      40822630912 bytes (38931 MB)
		Used:      40822528000 bytes (38931 MB)
		Available:      102912 bytes (0 MB)
		State: up
		Last error: none
		Active requests:	0
		Maximum active:		0

Drive home2:	Device /dev/ad6s1f
		Created on depot at Thu Sep 13 02:02:33 2001
		Config last updated Sun Sep 16 03:28:31 2001
		Size:      39566415872 bytes (37733 MB)
		Used:      39566312960 bytes (37733 MB)
		Available:      102912 bytes (0 MB)

You should really repartition your physical drives (spindles) to have
only one Vinum drive each.  Then make sure that both subdisks are of
the same size, and you shouldn't have any more problems.  Yes, this
doesn't fix the bug, but I'll work on that.

>>  Agreed.  You're collateral damage.  But I can't find that out
>>  until I hear about it.  I've opened the server for you.
>
> I'm not sure I like being called "collateral damage", but thanks
> anyway.

You're not supposed to.  But you're really the first person from
excite who wanted to contact me.

Greg
--
See complete headers for address and phone numbers

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010917120427.M3782>