From: Ram Ramesh <rramesh2400@gmail.com>
To: Ethan Wilson <ethan.wilson@shiftmail.org>
Cc: linux-raid <linux-raid@vger.kernel.org>
Subject: Re: Can I replace raid6 disk using dd?
Date: Tue, 19 Aug 2014 08:42:59 -0500 [thread overview]
Message-ID: <53F35463.50204@gmail.com> (raw)
In-Reply-To: <53F313FA.5040106@shiftmail.org>
On 08/19/2014 04:08 AM, Ethan Wilson wrote:
> On 19/08/2014 09:09, Killian De Volder wrote:
>> No need to remove the bitmap.
>> But be very careful that the disk is exactly the same size (or bigger).
>> I recently had a disk that was slightly smaller then advertised !
>>
>> But if it's a raid6 why not just jank a disk ?
>> It's still going to be redundant, but only on 1 disk.
>>
>> Killian De Volder
>> Megasoft bvba
>> killian.de.volder@megasoft.be
>>
>
> I think it would not be accepted by MD if the size was smaller than
> needed. At least with --replace. With the dd thing I don't know: it
> might trust the metadata and bypass the check.... I'd be careful in
> that case indeed.
> --
> To unsubscribe from this list: send the line "unsubscribe linux-raid" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
Thank you all. I think many feel dd is risky although doable. I felt the
same way too. Let me look for alternate/safe ways.
I wanted to experiment because the real data in the array is small and
I had good backups. Still, I do not think it is worth risking the chance
of trashing the array. I am more worried of the what if scenario, where
there is corruption, but not detected until my backup is no longer up to
date - I am not fond of Murphy :-)
Ramesh
prev parent reply other threads:[~2014-08-19 13:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-18 19:26 Can I replace raid6 disk using dd? Ram Ramesh
2014-08-19 2:30 ` Ethan Wilson
2014-08-19 2:49 ` Ram Ramesh
2014-08-19 7:09 ` Killian De Volder
2014-08-19 9:08 ` Ethan Wilson
2014-08-19 13:42 ` Ram Ramesh [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=53F35463.50204@gmail.com \
--to=rramesh2400@gmail.com \
--cc=ethan.wilson@shiftmail.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.