From: Li Nan <linan666@huaweicloud.com>
To: Gandalf Corvotempesta <gandalf.corvotempesta@gmail.com>,
Linux RAID Mailing List <linux-raid@vger.kernel.org>
Subject: Re: New device added but i did a mess
Date: Sat, 27 Jan 2024 14:43:42 +0800 [thread overview]
Message-ID: <144ad5ee-e24b-3d77-63c9-d911f3589134@huaweicloud.com> (raw)
In-Reply-To: <CAJH6TXjrmVRBpP-vr1io0unxqKZ_QE464G9R6G4Ekct3ShVx6g@mail.gmail.com>
在 2024/1/25 22:49, Gandalf Corvotempesta 写道:
> Ok, i think i did a mess.
> I have a 3 way mirror with 3 drives on it
> All drives are working, not failed.
> I would like to replace one of these drive (because it's very old)
> with a new drive.
> I would like to to the add and replace in the same phase, without
> reducing the redundancy level
> I did this multiple times before, during the sync, the array is a 4 way mirror
>
> BUT this time i think i did an issue, i've just run this:
>
> $ mdadm /dev/md0 --add /dev/sdd1 --replace /dev/sda1 --with /dev/sdd1
It is right.
>
> sda was marked failed immediately, and sdd1 is marked as active sync.
> Less than 1 second.
>
> Is this ok or i've just added a blank drive and forced the removal of
> a working one ?
>
> Honestly, and this is something that comes to mind right now, the
> partition is very very small, like 64MB so 1 second sync (on a SSD)
> could be ok.
>
> but:
> 1. which is the right command to run to add-sync-remove a not-failed disk > 2. how can I ensure that sdd is working as expected and data were
> synced properly?
you can check dmesg. The following means the beginning and ending of
recovery:
md: recovery of RAID array md0
md: md0: recovery done.
Also, you can get more information with 'mdadm -D /dev/md0'
syncing:
Number Major Minor RaidDevice State
0 8 0 0 active sync /dev/sda
3 8 48 0 spare rebuilding /dev/sdd
1 8 16 1 active sync /dev/sdb
2 8 32 2 active sync /dev/sdc
sync success:
Number Major Minor RaidDevice State
3 8 48 0 active sync /dev/sdd
1 8 16 1 active sync /dev/sdb
2 8 32 2 active sync /dev/sdc
0 8 0 - faulty /dev/sda
--
Thanks,
Nan
prev parent reply other threads:[~2024-01-27 6:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-25 14:49 New device added but i did a mess Gandalf Corvotempesta
2024-01-26 10:46 ` Gandalf Corvotempesta
2024-01-26 18:39 ` Pascal Hambourg
2024-01-27 6:43 ` Li Nan [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=144ad5ee-e24b-3d77-63c9-d911f3589134@huaweicloud.com \
--to=linan666@huaweicloud.com \
--cc=gandalf.corvotempesta@gmail.com \
--cc=linux-raid@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).