Date: Fri, 30 Aug 2002 12:38:26 +0200 From: "Patrick O'Reilly" <bsd@perimeter.co.za> To: "FreeBSD Question List" <freebsd-questions@freebsd.org> Subject: Vinum - easy question for someone who knows :) Message-ID: <000d01c25011$61c85420$b50d030a@PATRICK>
next in thread | raw e-mail | index | archive | help
Hi all.
I have just noted the following:
---
# vinum list
2 drives:
D d1 State: up Device /dev/ad1s1e Avail:
0/39079 MB (0%)
D d2 State: up Device /dev/ad2s1e Avail:
0/39079 MB (0%)
1 volumes:
V vm1 State: up Plexes: 2 Size: 38
GB
2 plexes:
P vm1.p0 C State: up Subdisks: 1 Size: 38
GB
P vm1.p1 C State: faulty Subdisks: 1 Size: 38
GB
2 subdisks:
S vm1.p0.s0 State: up PO: 0 B Size: 38
GB
S vm1.p1.s0 State: stale PO: 0 B Size: 38
GB
#
---
For some reason one of the plexes is "faulty", and the subdisk is
"stale". I would like to revive the stale subdisk, but without
interrupting current processing on the server.
If I understand the man page correctly, the corect command would be:
# vinum start -i x -S y vm1.p1.s0
This should "revive" the subdisk and eventually return the subdisk and
plex to the "up" state.
Perhaps someone could also recommend reasonable values for x and y? I
thought of:
# vinum start -i 100 -S 65536 vm1.p1.s0
Does that look OK?
Regards,
Patrick O'Reilly.
___ _ __
/ _ )__ __ (_)_ __ ___ _/ /____ __
/ __/ -_) _) / ~ ) -_), ,-/ -_) _)
/_/ \__/_//_/_/~/_/\__/ \__/\__/_/
http://www.perimeter.co.za
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?000d01c25011$61c85420$b50d030a>