Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 20 Sep 1999 20:34:42 -0500
From:      river <river@theriver.nu>
To:        'Greg Lehey' <grog@lemis.com>
Cc:        questions@freebsd.org
Subject:   RE: VINUM (MORE)
Message-ID:  <21DC5E98AE1FD311B1290020AFDB6C6E63FC@cx288885-b.okcs1.ok.home.com>

next in thread | raw e-mail | index | archive | help
I resent that.....

I read the documentation front to back.....thats the problem....the
documentation is hard to follow and doesnt provide the steps that are
needed.

I read all your emails, followed what you said (without any snide comments
about your lack of communication skills) and this is where I am.

All I did was ask for your help with this functional/non-functional
software.

-----Original Message-----
From: Greg Lehey [mailto:grog@lemis.com]
Sent: Monday, September 20, 1999 7:56 PM
To: river
Cc: questions@freebsd.org
Subject: Re: VINUM (MORE)


On Monday, 20 September 1999 at  6:52:12 -0500, river wrote:
> I had already tried to init the mirror:

I don't think there's any point in continuing with this.  You don't
read the documentation, you don't read my messages, and you send back
text which I can't read.

Greg

> vinum -> init -v -w mirror.p1
> vinum[53957]: initializing subdisk /dev/vinum/rsd/mirror.p1.s0
> vinum[53957]: can't write subdisk /dev/vinum/rsd/mirror.p1.s0:
Input/output
> error
> child 53957 exited with status 0x1
> vinum[53954]: couldn't initialize plex mirror.p1, 1 processes died
> vinum -> start mirror.p1.s0
> Can't start mirror.p1.s0: Invalid argument (22)
> vinum ->
>
> when I rebooted, this is the output that I got.....the second slice of the
> mirror changed to faulty:
>
> D drive1                State: up       Device /dev/da1e        Avail:
> 17/117 MB (14%)
> D drive2                State: referenced       Device  Avail: 0/0 MB
>
> V mirror                State: up       Plexes:       2 Size:        100
MB
>
> P mirror.p0           C State: up       Subdisks:     1 Size:        100
MB
> P mirror.p1           C State: faulty   Subdisks:     1 Size:        100
MB
>
> S mirror.p0.s0          State: up       PO:        0  B Size:        100
MB
> S mirror.p1.s0          State: crashed  PO:        0  B Size:        100
MB
>

> From: Greg Lehey [mailto:grog@lemis.com]
> Sent: Sunday, September 19, 1999 11:30 PM
> To: river
> Cc: FreeBSD Questions
> Subject: Re: VINUM (MORE)
>
>
> [Format recovered--see http://www.lemis.com/email/email-format.html]
>
> On Sunday, 19 September 1999 at 23:09:18 -0500, river wrote:
>> I think I have it setup correctly now
>
> Looks reasonable.
>
>> I did a test mirror (100m each) and was able to newfs and mount it.  I
was
>> curious if it is supposed to say State:emply on S mirror.p1.s0 ?
>>
>> vinum -> list
>> Configuration summary
>>
>> Drives:         2 (4 configured)
>> Volumes:        1 (4 configured)
>> Plexes:         2 (8 configured)
>> Subdisks:       2 (16 configured)
>>
>> D drive1                State: up       Device /dev/da1s1e      Avail:
> 17/117 MB (14%)
>> D drive2                State: up       Device /dev/da2s2e      Avail:
> 17/117 MB (14%)
>>
>> V mirror                State: up       Plexes:       2 Size:        100
> MB
>>
>> P mirror.p0           C State: up       Subdisks:     1 Size:        100
> MB
>> P mirror.p1           C State: initializing     Subdisks:     1 Size: 100
> MB
>>
>> S mirror.p0.s0          State: up       PO:        0  B Size:        100
> MB
>> S mirror.p1.s0          State: empty    PO:        0  B Size:        100
> MB
>
>> From vinum(8):
>
>            setupstate
>
>                                When creating a multi-plex volume, assume
> that
>                                the contents of all the plexes are
> consistent.
>                                This is normally not the case, and
correctly
>                                you should use the init command to first
> bring
>                                them to a consistent state.  In the case of
>                                striped and concatenated plexes, however,
it
>                                does not normally cause problems to leave
> them
>                                inconsistent: when using a volume for a
file
>                                system or a swap partition, the previous
con-
>                                tents of the disks are not of interest, so
> they
>                                may be ignored.  If you want to take this
> risk,
>                                use this keyword.  It will only apply to
the
>                                plexes defined immediately after the volume
> in
>                                the configuration file.  If you add plexes
to
> a
>                                volume at a later time, you must integrate
>                                them.
>
> You can fix this with 'start mirror.p1.s0'.  You should also look at
> the 'mirror' command.
>
> Greg
> --
> When replying to this message, please copy the original recipients.
> For more information, see http://www.lemis.com/questions.html
> See complete headers for address, home page and phone numbers
> finger grog@lemis.com for PGP public key

--
When replying to this message, please copy the original recipients.
For more information, see http://www.lemis.com/questions.html
See complete headers for address, home page and phone numbers
finger grog@lemis.com for PGP public key


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




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