-
Notifications
You must be signed in to change notification settings - Fork 1.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
manually replaced drive with, now new drive = unavail, corrupted data #3215
Comments
Anybody have any ideas on this? I have another system that is very similar to this one that now has a bad drive in it (when scrubbing it comes up with 225 READ errors and 291 WRITE errors) yet the spare was not pulled in to replace it and all drives etc. are ONLINE. I'd like to replace the drive but I don't want to run into the same thing as before. Maybe I shouldn't use the spare at all? Should I do:
Maybe the last two lines need to be switched? Thanks, Steve |
Am I submitting this to the wrong place? |
Resolved on the #xfsonlinux IRC. The answer to the main problem was to just do:
it resilvered and put the spare back as a spare. Thanks @DeHackEd. The answer to the general question of how to replace a drive in-place seems to be:
Depending on the environment there may be some steps between putting the new drive in and the replace command in order to have the new_disk_name be appropriate (using vdev_id.conf and/or multipath for instance) and it might be the same name as "disk_name". For instance mine are vdev-id's like 1-2 indicating enclosure 1, slot 2. The down-side to this is that it degrades the array. A safer way to do it is to use a spare disk but first you need to remove the spare from the pools. My spare is called 1-44. So I would do:
then once it is done I'm assuming 1-2 would be unassigned. I think I'd do:
Then either make the new drive the spare or replace 1-44 with the new drive that is in 1-2 in order to keep things consistent and balanced out, in my case with SAS cards and four backplanes. |
I had a drive (vdev id = 1-2) that was showing read errors. The OEM sent me a drive so I decided to manually replace the drive with the hot-spare (vdev id = 1-44) I had set up. zpool history shows:
Now the status looks like:
I have tried replacing 1-44 with 1-2 again:
and I even tried removeing 1-2:
I'm not sure what to do now. The goal is to get the new 1-2 to take over and put 1-44 back in its role as a hot spare. Can anyone advise?
Thanks,
Steve
The text was updated successfully, but these errors were encountered: