Linux RAID subsystem development
 help / color / mirror / Atom feed
From: "John Stoffel" <john@stoffel.org>
To: Moritz Rosin <moritz.rosin@itrosinen.de>
Cc: linux-raid@vger.kernel.org
Subject: Re: Recover data from accidentally created raid5 over raid1
Date: Tue, 11 Apr 2023 15:47:46 -0400	[thread overview]
Message-ID: <25653.47458.489415.933722@quad.stoffel.home> (raw)
In-Reply-To: <c0a9e08b91e86c86038be889907f0796@itrosinen.de>

>>>>> "Moritz" == Moritz Rosin <moritz.rosin@itrosinen.de> writes:

> Hey there,
> unfortunately I have to admit, that I learned my lesson the hard way 
> dealing with software raids.

> I had a raid1 running reliable over month using two 4TB HDDs.
> Since I ran short on free space I tried to convert the raid1 to a raid5 
> in-place (with the plan to add the 3rd HDD after converting).
> That's where my incredibly stupid mistake kicked in.

> I followed an internet tutorial that told me to do:
> mdadm --create /dev/md0 --level=5 --raid-devices=2 /dev/sdX1 /dev/sdY1

Please share the link to the tutorial so we can maybe shame that
person into fixing it.  Or removing it.  

> I learned that I re-created a raid5 array instead of converting the 
> raid1 :-(

Yeah, I think you're out of luck here.  What kind of filesystem did
you have on your setup?  Were you using MD -> LVM -> filesystem stack?
Or just a raw filesystem on top of the /dev/md?  device?

> Is there any chance to un-do the conversion or restore the data?
> Has the process of creation really overwritten data or is there
> anythins left on the disk itself that can be rescued?

If you have any information on your setup before you did this, then
you might be ok, but honestly, I think you're toast.

John

  reply	other threads:[~2023-04-11 19:47 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-11 18:11 Recover data from accidentally created raid5 over raid1 Moritz Rosin
2023-04-11 19:47 ` John Stoffel [this message]
2023-04-12  0:18   ` Wol
2023-04-12  0:26     ` Phil Turmel
2023-04-12 10:15       ` Moritz Rosin
2023-04-13  6:10         ` Moritz Rosin
2023-04-13 12:10           ` Phil Turmel
2023-04-12 10:22     ` Reindl Harald
2023-04-12 12:21       ` Phil Turmel
2023-04-12 20:22         ` Mark Wagner
2023-04-13  8:05           ` Wols Lists
2023-04-13 12:12             ` Phil Turmel
2023-04-13 14:58               ` Wols Lists
  -- strict thread matches above, loose matches on Subject: below --
2023-04-11 18:12 Moritz Rosin

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=25653.47458.489415.933722@quad.stoffel.home \
    --to=john@stoffel.org \
    --cc=linux-raid@vger.kernel.org \
    --cc=moritz.rosin@itrosinen.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