2012-05-11 14:22, Jim Klimov wrote:
What conditions can cause the reset of the resilvering
process? My lost-and-found disk can't get back into the
pool because of resilvers restarting...
FOLLOW-UP AND NEW QUESTIONS
Here is a new piece of evidence - I've finally got something
out of fmdump -
2012-05-12 15:52, Jim Klimov wrote:
2012-05-11 14:22, Jim Klimov wrote:
What conditions can cause the reset of the resilvering
process? My lost-and-found disk can't get back into the
pool because of resilvers restarting...
Guess I must assume that the disk is dying indeed, losing
connection
On May 12, 2012, at 4:52 AM, Jim Klimov wrote:
2012-05-11 14:22, Jim Klimov wrote:
What conditions can cause the reset of the resilvering
process? My lost-and-found disk can't get back into the
pool because of resilvers restarting...
FOLLOW-UP AND NEW QUESTIONS
Here is a new piece of
Thanks for staying tuned! ;)
2012-05-12 18:34, Richard Elling wrote:
On May 12, 2012, at 4:52 AM, Jim Klimov wrote:
2012-05-11 14:22, Jim Klimov wrote:
What conditions can cause the reset of the resilvering
process? My lost-and-found disk can't get back into the
pool because of resilvers
2012-05-12 7:01, Jim Klimov wrote:
Overall the applied question is whether the disk will
make it back into the live pool (ultimately with no
continuous resilvering), and how fast that can be done -
I don't want to risk the big pool with nonredundant
arrays for too long.
Here lies another
Jim,
This makes sense.
fmdump -eV reported that your original drive was experiencing repeated
fread failures ( scsi command code 0x28)
Steve
- Original Message -
Well, I decided to bite the bullet and kick the original
disk from the pool after replacing it with the spare,
