Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 1 Feb 2004 14:16:05 -0600
From:      Hari Bhaskaran <subscr@spider.netmails.net>
To:        freebsd-questions@freebsd.org
Subject:   Re: Vinum or HD error?
Message-ID:  <20040201201605.GA65577@poecilotheria.netmails.net>
In-Reply-To: <000801c3e8fc$32770790$0200a8c0@satellite>
References:  <20040201184231.GA57453@poecilotheria.netmails.net> <000801c3e8fc$32770790$0200a8c0@satellite>

next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Feb 01, 2004 at 02:47:16PM -0500, dave wrote:
> Hello,
>     Can you tell me about your vinum setup? Are you using IDE or scsi
> drives? What raidlevel are you using? And, do you have your root partition

Two IDE drives, 120G each (1 WD, 1 maxtor), although this particular volume
in Q is *not* mirrored at all - it is only on one drive. This volume doesn't
contain any critical data and I am not trying to recover any data out of it.
I am just trying to figure out what happened for my own knowledge and to know
whether to replace the HD etc. I thought those error code (in my earlier
mail) might say something. The output of vinum list is given below

No, the root partition is not raided - that wasn't possible in 4.7 (yes, there
is an inactive copy, but no thru vinum)

# vinum list
2 drives:

D regalis               State: up       Device /dev/ad0s1e      Avail: 0/110374 MB (0%)
D formosa               State: up       Device /dev/ad1s1e      Avail: 0/113143 MB (0%)

11 volumes:
V varbase               State: up       Plexes:       2 Size:       3072 MB
V varlog                State: up       Plexes:       2 Size:       1024 MB
V vartmp                State: up       Plexes:       2 Size:       1024 MB
V tmp                   State: up       Plexes:       2 Size:       3072 MB
V usrbase               State: up       Plexes:       2 Size:       3072 MB
V usrhome               State: up       Plexes:       2 Size:       3072 MB
V fs1                   State: up       Plexes:       2 Size:       2048 MB
V fs2                   State: up       Plexes:       2 Size:         25 GB
V fs3                   State: up       Plexes:       2 Size:         40 GB
V fs4                   State: up       Plexes:       1 Size:         26 GB
V fs5                   State: down     Plexes:       1 Size:         29 GB

20 plexes:
P varbase.p0          C State: up       Subdisks:     1 Size:       3072 MB
P varbase.p1          C State: up       Subdisks:     1 Size:       3072 MB
P varlog.p0           C State: up       Subdisks:     1 Size:       1024 MB
P varlog.p1           C State: up       Subdisks:     1 Size:       1024 MB
P vartmp.p0           C State: up       Subdisks:     1 Size:       1024 MB
P vartmp.p1           C State: up       Subdisks:     1 Size:       1024 MB
P tmp.p0              C State: up       Subdisks:     1 Size:       3072 MB
P tmp.p1              C State: up       Subdisks:     1 Size:       3072 MB
P usrbase.p0          C State: up       Subdisks:     1 Size:       3072 MB
P usrbase.p1          C State: up       Subdisks:     1 Size:       3072 MB
P usrhome.p0          C State: up       Subdisks:     1 Size:       3072 MB
P usrhome.p1          C State: up       Subdisks:     1 Size:       3072 MB
P fs1.p0              C State: up       Subdisks:     1 Size:       2048 MB
P fs1.p1              C State: up       Subdisks:     1 Size:       2048 MB
P fs2.p0              C State: up       Subdisks:     1 Size:         25 GB
P fs2.p1              C State: up       Subdisks:     1 Size:         25 GB
P fs3.p0              C State: up       Subdisks:     1 Size:         40 GB
P fs3.p1              C State: up       Subdisks:     1 Size:         40 GB
P fs4.p0              C State: up       Subdisks:     1 Size:         26 GB
P fs5.p0              C State: faulty   Subdisks:     1 Size:         29 GB

20 subdisks:
S varbase.p0.s0         State: up       PO:        0  B Size:       3072 MB
S varbase.p1.s0         State: up       PO:        0  B Size:       3072 MB
S varlog.p0.s0          State: up       PO:        0  B Size:       1024 MB
S varlog.p1.s0          State: up       PO:        0  B Size:       1024 MB
S vartmp.p0.s0          State: up       PO:        0  B Size:       1024 MB
S vartmp.p1.s0          State: up       PO:        0  B Size:       1024 MB
S tmp.p0.s0             State: up       PO:        0  B Size:       3072 MB
S tmp.p1.s0             State: up       PO:        0  B Size:       3072 MB
S usrbase.p0.s0         State: up       PO:        0  B Size:       3072 MB
S usrbase.p1.s0         State: up       PO:        0  B Size:       3072 MB
S usrhome.p0.s0         State: up       PO:        0  B Size:       3072 MB
S usrhome.p1.s0         State: up       PO:        0  B Size:       3072 MB
S fs1.p0.s0             State: up       PO:        0  B Size:       2048 MB
S fs1.p1.s0             State: up       PO:        0  B Size:       2048 MB
S fs2.p0.s0             State: up       PO:        0  B Size:         25 GB
S fs2.p1.s0             State: up       PO:        0  B Size:         25 GB
S fs3.p0.s0             State: up       PO:        0  B Size:         40 GB
S fs3.p1.s0             State: up       PO:        0  B Size:         40 GB
S fs4.p0.s0             State: up       PO:        0  B Size:         26 GB
S fs5.p0.s0             State: crashed  PO:        0  B Size:         29 GB

> raided?
> Thanks.
> Dave.
> 

--
Hari Bhaskaran



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