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.
Here's the output of "vinum l -v":
4 drives:
Drive data1: Device /dev/ad4s1g
Created on depot at Thu Sep 13 01:58:14 2001
Config last updated Sun Sep 16 03:28:31 2001
Size: 10737418240 bytes (10240 MB)
Used: 10737162752 bytes (10239 MB)
Available: 255488 bytes (0 MB)
State: up
Last error: none
Active requests: 0
Maximum active: 0
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 data2: Device /dev/ad6s1e
Created on depot at Thu Sep 13 02:02:33 2001
Config last updated Sun Sep 16 03:28:31 2001
Size: 10737418240 bytes (10240 MB)
Used: 10737162752 bytes (10239 MB)
Available: 255488 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)
State: up
Last error: none
Active requests: 0
Maximum active: 0
2 volumes:
Volume data: Size: 21474054144 bytes (20479 MB)
State: up
Flags:
1 plexes
Read policy: round robin
Volume home: Size: 80388569600 bytes (76664 MB)
State: up
Flags:
1 plexes
Read policy: round robin
2 plexes:
Plex data.p0: Size: 21474054144 bytes (20479 MB)
Subdisks: 2
State: up
Organization: striped Stripe size: 279 kB
Part of volume data
Plex home.p0: Size: 80388569600 bytes (76664 MB)
Subdisks: 2
State: up
Organization: striped Stripe size: 279 kB
Part of volume home
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)
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)
> 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.
John
>
> Greg
> --
> When replying to this message, please take care not to mutilate the
> original text.
> For more information, see http://www.lemis.com/email.html
> See complete headers for address and phone numbers
_______________________________________________________
Send a cool gift with your E-Card
http://www.bluemountain.com/giftcenter/
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
