linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bill Davidsen <davidsen@tmr.com>
To: Jonathan Gazeley <jonathan.gazeley@bristol.ac.uk>
Cc: linux-raid@vger.kernel.org
Subject: Re: Unsure of changes to array
Date: Wed, 17 Oct 2007 16:50:03 -0400	[thread overview]
Message-ID: <4716757B.9030609@tmr.com> (raw)
In-Reply-To: <47161684.7010604@bristol.ac.uk>

Jonathan Gazeley wrote:
> Dear all,
>
> This is hopefully a simple question for you to answer, but I am fairly 
> new to RAID and don't want to risk losing my data!
>
> My setup is as follows:
> - I have four 500GB disks. Each disk is split into a 5GB partition, 
> and a 495GB partition.
> - The four 5GB partitions are in a RAID-5 array, md0. CentOS is 
> installed on this 15GB partition.
> - The four 495GB partiions are in a RAID-5 array, md1. This partition 
> holds my user data.
>
> However, I have decided I no longer wish to two arrays across the 
> disks. I've added a fifth disk on which I have installed the OS 
> without RAID, meaning the old md0 is currently unused. Can I simply 
> remove the four 5GB partitions, and resize the four 495GB partitions 
> to fill the entire disk? Will this break anything?

Not unless you make a mistake in typing, or your hardware or power fails 
during the process. Of course in that case you will possibly lose 
everything.
>
> Before anybody tells me off for having the OS on a non-RAID disk, this 
> is a home server and therefore high availability is not an issue. But 
> keeping my data safe against disk failures is important to me.

Having your o/s and swap on RAID reduces your chances of losing your 
data. If it were me and reliability were the goal, I would have the o/s 
mirrored on the first two drives (as seen by the BIOS) so you boot if 
one fails hard, then put swap RAID-10 in the little 5GB partition on the 
other three drives, then convert the raid-5 to raid-6 using the rest of 
the added fifth drive.

Anything which reduces the chances of an unclean shutdown improves the 
chances of keeping your data. A decent UPS is a big help in that regard. 
Disk failures on the data drives are not the only threat to your data!

-- 
bill davidsen <davidsen@tmr.com>
  CTO TMR Associates, Inc
  Doing interesting things with small computers since 1979


      parent reply	other threads:[~2007-10-17 20:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-17 14:04 Unsure of changes to array Jonathan Gazeley
2007-10-17 14:53 ` Nagilum
2007-10-17 20:50 ` Bill Davidsen [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=4716757B.9030609@tmr.com \
    --to=davidsen@tmr.com \
    --cc=jonathan.gazeley@bristol.ac.uk \
    --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 NNTP newsgroup(s).