Greg Lehey wrote in message ID
[EMAIL PROTECTED]:
Again, news for me. You can stop a revive and restart it at a later
time; the state information includes the revive pointer. But the only
real answer to this one would be to see the statistics.
Well, I deleted the plex and tried again:
Hi Greg,
I've got a question or two about vinum, and how to work it.
I'm trying to upgrade the storage on my home computer, and while I was
transitioning my old disks out, I only managed to get one of the new
ones online to copy data onto it. Now I want to mirror that volume
onto a 2nd plex.
On Sunday, 26 December 1999 at 19:03:27 -0500, Gary Palmer wrote:
Hi Greg,
I've got a question or two about vinum, and how to work it.
I'm trying to upgrade the storage on my home computer, and while I was
transitioning my old disks out, I only managed to get one of the new
ones online to
Greg Lehey wrote in message ID
[EMAIL PROTECTED]:
Did you forget the 'setupstate' keyword?
How would that apply? The 2nd disk was not consistant as it was added
after the data was copied onto the first and the old disks removed.
Or should I have dd'd the contents of the first disk onto the
On Sunday, 26 December 1999 at 20:54:17 -0500, Gary Palmer wrote:
Greg Lehey wrote in message ID
[EMAIL PROTECTED]:
Did you forget the 'setupstate' keyword?
How would that apply? The 2nd disk was not consistant as it was added
after the data was copied onto the first and the old disks
Greg Lehey wrote in message ID
[EMAIL PROTECTED]:
It occurs to me that it is, in fact, correct to read from a volume
being revived. The data is consistent up to the point where the
revive has progressed, so the system can read from this area.
Why would it be reading from the reviving plex?
On Sunday, 26 December 1999 at 21:24:15 -0500, Gary Palmer wrote:
Greg Lehey wrote in message ID
[EMAIL PROTECTED]:
It occurs to me that it is, in fact, correct to read from a volume
being revived. The data is consistent up to the point where the
revive has progressed, so the system can
