All of lore.kernel.org
 help / color / mirror / Atom feed
From: Adam Goryachev <adam@websitemanagers.com.au>
To: "Ralf Müller" <ralf@bj-ig.de>
Cc: Linux RAID <linux-raid@vger.kernel.org>
Subject: Re: Howto avoid full re-sync
Date: Wed, 12 Sep 2012 22:52:18 +1000	[thread overview]
Message-ID: <50508582.3070501@websitemanagers.com.au> (raw)
In-Reply-To: <C0796F33-32E4-4F28-B6FB-469AF438C545@bj-ig.de>

On 11/09/12 00:12, Ralf Müller wrote:
> Besides all the stuff about fix your server, a raid is not a backup and you risk your data - simply add a write intent bitmap:
>
> mdadm /dev/md2 --grow --bitmap=internal
I've added this across a number of my systems now, and it seems to work
really well (Thank You), especially one system which has a RAID1 with an
external USB drive + internal drive which normally take over 2 days for
a full resync.

Can you suggest if there is any dis-advantage to using the bitmap (maybe
write performance will suffer), or disk space is reduced, or ....

While I can see the benefits, I'm just wondering if it might be too good
to be true, or what I am missing....

Thanks again for your assistance.

Regards,
Adam

-- 
Adam Goryachev
Website Managers
Ph: +61 2 8304 0000                            adam@websitemanagers.com.au
Fax: +61 2 8304 0001                            www.websitemanagers.com.au

--
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

  reply	other threads:[~2012-09-12 12:52 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-07  4:41 Howto avoid full re-sync Adam Goryachev
2012-09-07  9:41 ` Ralf Müller
2012-09-07 12:41   ` Phil Turmel
2012-09-09 23:11   ` Adam Goryachev
2012-09-10  1:02     ` NeilBrown
2012-09-10 14:12     ` Ralf Müller
2012-09-12 12:52       ` Adam Goryachev [this message]
2012-09-12 13:28         ` John Robinson

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=50508582.3070501@websitemanagers.com.au \
    --to=adam@websitemanagers.com.au \
    --cc=linux-raid@vger.kernel.org \
    --cc=ralf@bj-ig.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 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.