linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Janek Kozicki <janek_listy@wp.pl>
To: linux-raid@vger.kernel.org
Subject: Re: very degraded RAID5, or increasing capacity by adding discs
Date: Tue, 9 Oct 2007 16:42:52 +0200	[thread overview]
Message-ID: <20071009164252.790a35c0@absurd> (raw)
In-Reply-To: <470AB496.5010406@msgid.tls.msk.ru>

Michael Tokarev said:     (by the date of Tue, 09 Oct 2007 02:52:06 +0400)

> Janek Kozicki wrote:
> > Hello,
> > 
> > Recently I started to use mdadm and I'm very impressed by its
> > capabilities. 
> > 
> > I have raid0 (250+250 GB) on my workstation. And I want to have
> > raid5 (4*500 = 1500 GB) on my backup machine.
> 
> Hmm.  Are you sure you need that much space on the backup, to
> start with?  Maybe better backup strategy will help to avoid
> hardware costs?  Such as using rsync for backups as discussed
> on this mailinglist about a month back (rsync is able to keep
> many ready to use copies of your filesystems but only store
> files that actually changed since the last backup, thus
> requiring much less space than many full backups).

yes, exactly. I am using rsnapshot, which is based on rsync and
hardlinks. It works exceptionally well - to my knowledge it's the
best backup solution I have ever seen. With plugin scripts I am even
mounting an lvm-snapshot of the drive being backupped.

from command 'rsnapshot du' I can see how many space is used (but
each directory tree is a full backup (made with hardlinks)):

278G    /backup/.sync
454M    /backup/hourly.0/
515M    /backup/hourly.1/
527M    /backup/daily.0/
30G     /backup/daily.1/
21G     /backup/daily.2/
561M    /backup/daily.3/
1.6G    /backup/daily.4/
3.0G    /backup/daily.5/
594M    /backup/daily.6/
1.4G    /backup/weekly.0/
11G     /backup/weekly.1/
9.3G    /backup/weekly.2/
23G     /backup/weekly.3/
33G     /backup/monthly.0/
3.7G    /backup/monthly.1/
415G    total


> It's definitely not possible with raid5.  Only option is to create a
> raid5 array consisting of less drives than it should contain at the
> end, and reshape it when you get more drives, as others noted in this
> thread.  But do note the following points:

<..snip..>

yes, I am aware of all those problems you listed. The data I'm
talking about is already a backup. While the real data is on my
workstation (a different linux box - albeit only the newest version
of my data). Only losing both of them simultaneoulsy will be
catastrophic for me. 

So I am inclined to do some experiments with the backup drives
configuration, while still doing my best at not losing it. An
exercise, you know :)

> > is it just a pipe dream?
> 
> I'd say it is... ;)

oh well. But I learnt a lot from your answers, thanks a lot!


PS: I'm receiving some mailing list posts twice, anybody knows why?
I'm used to mailman but looks like majordomo is being configured in a
different way - I cannot find a configure page. (I just subscribed).

-- 
Janek Kozicki                                                         |

      parent reply	other threads:[~2007-10-09 14:42 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-08 19:13 very degraded RAID5, or increasing capacity by adding discs Janek Kozicki
2007-10-08 19:17 ` Justin Piszcz
2007-10-08 19:26 ` Richard Scobie
2007-10-08 20:08   ` Guy Watkins
2007-10-08 22:25   ` Janek Kozicki
2007-10-08 22:46     ` Janek Kozicki
2007-10-09  1:53       ` Guy Watkins
2007-10-09  3:32       ` Neil Brown
2007-10-09 14:44         ` Janek Kozicki
2007-10-09 14:56         ` Mr. James W. Laferriere
2007-10-09 21:52           ` Neil Brown
2007-10-08 22:52 ` Michael Tokarev
2007-10-09  3:24   ` Neil Brown
2007-10-09  9:48     ` Michael Tokarev
2007-10-22  9:03       ` Louis-David Mitterrand
2007-10-23 22:41         ` Bill Davidsen
2007-10-09 14:42   ` Janek Kozicki [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=20071009164252.790a35c0@absurd \
    --to=janek_listy@wp.pl \
    --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).