From: Hannes Reinecke <hare@suse.de>
To: "Stefanie Leisestreichler (Febas)"
<stefanie.leisestreichler@peter-speer.de>,
linux-raid@vger.kernel.org
Subject: Re: RAID 1 | Changing HDs
Date: Wed, 3 Sep 2025 14:35:39 +0200 [thread overview]
Message-ID: <c4fcc07a-eeaa-4307-8a5a-973c6df69bcd@suse.de> (raw)
In-Reply-To: <5c8e3075-e45a-410e-a23a-cbf0e86bdfa6@peter-speer.de>
On 9/3/25 13:55, Stefanie Leisestreichler (Febas) wrote:
> Hi.
> I have the system layout shown below.
>
> To avoid data loss, I want to change HDs which have about 46508 hours of
> up time.
>
> I thought, instead of degrading, formatting, rebuilding and so on, I could
> - shutdown the computer
> - take i.e. /dev/sda and do
> - dd bs=98304 conv=sync,noerror if=/dev/sda of=/dev/sdX (X standig for
> device name of new disk)
>
Why would you do that?
In the end, you will have to transfer data from the entire disk
(to a new disk). And that will be the main drag, at it'll take ages.
And there it doesn't matter if you use 'dd' or md resync; both will
be taking roughly the same time.
> Is it save to do it this way, presuming the array is in AA-State?
>
I would not recommend it.
Replacing drives is _precisely_ why RAID was created in the first place,
so really there is no difference between replacing a faulty drive or
replacing a non-faulty drive.
So I would strongly recommend to use MD tools to replace the drive;
it will serve as a nice exercise on what to do in case of a real
fault :-)
Cheers,
Hannes
--
Dr. Hannes Reinecke Kernel Storage Architect
hare@suse.de +49 911 74053 688
SUSE Software Solutions GmbH, Frankenstr. 146, 90461 Nürnberg
HRB 36809 (AG Nürnberg), GF: I. Totev, A. McDonald, W. Knoblich
next prev parent reply other threads:[~2025-09-03 12:35 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-03 11:55 RAID 1 | Changing HDs Stefanie Leisestreichler (Febas)
2025-09-03 12:19 ` Reindl Harald
2025-09-03 13:20 ` Stefanie Leisestreichler (Febas)
2025-09-03 14:00 ` Reindl Harald
2025-09-03 14:26 ` Stefanie Leisestreichler (Febas)
2025-09-03 21:59 ` Reindl Harald
2025-09-04 17:04 ` Stefanie Leisestreichler (Febas)
2025-09-03 12:35 ` Hannes Reinecke [this message]
2025-09-03 12:49 ` Stefanie Leisestreichler (Febas)
2025-09-03 15:45 ` Roman Mamedov
2025-09-03 16:58 ` Michael Reinelt
2025-09-03 17:28 ` Roman Mamedov
2025-09-03 17:47 ` Stefanie Leisestreichler (Febas)
2025-09-03 17:57 ` Pascal Hambourg
2025-09-03 19:19 ` Stefanie Leisestreichler (Febas)
2025-09-03 19:50 ` Wol
2025-09-04 17:06 ` Stefanie Leisestreichler (Febas)
2025-09-03 15:59 ` anthony
2025-09-04 17:13 ` Stefanie Leisestreichler (Febas)
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=c4fcc07a-eeaa-4307-8a5a-973c6df69bcd@suse.de \
--to=hare@suse.de \
--cc=linux-raid@vger.kernel.org \
--cc=stefanie.leisestreichler@peter-speer.de \
/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