Help with Vinum disk crash...
Greg 'groggy' Lehey
grog at FreeBSD.org
Sun Feb 22 20:27:45 PST 2004
On Thursday, 19 February 2004 at 1:04:29 +1100, Tony Frank wrote:
> On Wed, Feb 18, 2004 at 01:15:18PM +0100, Danny Carroll wrote:
>> Quoting Tony Frank <tfrank at optushome.com.au>:
>>> So you have a subdisk down which means Vinum can still read from the plex
>>> but has to manually calculate the missing subdisk data.
>> But I assume it cant write till I replace it..
> I believe it should function for both read & write in degraded mode.
> Any reads will have to be rebuilt hence there will be a big hit in
No, only reads of the missing disk need to be rebuilt. There's a
detailed discussion of how RAID-5 works in degraded mode at
>>> Another option would be to force the particular subdisk down and try the
>>> above steps again.
>> Something like:
>> vinum down data.p0.s0 ???
> The command would be "vinum stop data.p0.s0"
> In my case I had to do "vinum stop -f data.p0.s0"
I'm not sure what would happen here, but it could be dangerous. The
object is already inaccessible. The different states are maintained
for two main reasons:
1. It tells the user how they got like that.
2. It tells Vinum whether the data on the object, if accessible, is
still up to date. "Crashed" and "down" mean that the data is up
to date, so a 'start' can complete immediately. "Obsolete" and
"stale" mean that the data is no longer up to date.
If you change the state of a subdisk from "stale" to "down" and then
issue a start command, Vinum assumes that the object still contains
the correct data, so it sets it "up" with no change. This will result
in severe data corruption of the kind that you're seeing.
> However this should not have any impact to your situation. The
> volume is working at the Vinum level (although degraded) The problem
> here is that the data on the vinum volume appears to be somehow
Correct. I'm wondering if this happened as the result of something
else, possibly finger trouble. The answer might be in the missing
information asked for at
When replying to this message, please copy the original recipients.
If you don't, I may ignore the reply or reply to the original recipients.
For more information, see http://www.lemis.com/questions.html
Note: I discard all HTML mail unseen.
Finger grog at FreeBSD.org for PGP public key.
See complete headers for address and phone numbers.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 187 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-questions/attachments/20040223/66d6a0f2/attachment.bin
More information about the freebsd-questions