linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Piergiorgio Sartor <piergiorgio.sartor@nexgo.de>
Cc: Piergiorgio Sartor <piergiorgio.sartor@nexgo.de>,
	linux raid mailing list <linux-raid@vger.kernel.org>
Subject: Re: RAID without superblock
Date: Mon, 20 Apr 2009 20:10:45 +0200	[thread overview]
Message-ID: <20090420181045.GA4236@lazy.lzy> (raw)
In-Reply-To: <1240178252.31728.12.camel@cichlid.com>

Hi,

first of all thanks a lot for all the suggestions,
it is really nice to have this support!

While reading the answers, I realized that I did
not make the "requirements" really clear. My bad.

The "primary" disk is an external one, which 90%
of the time is connected to the same Linux PC.
But, it could happen it is removed and connected
somewhere else, where no "md" is available.

My idea was, in order to have some protection, to
use it in RAID-1 "superblockless" configuration
on the "default" PC, and use it as a normal disk
whenever (or wherever) necessary.
Of course, the bitmap resync will not work, when
updating the disk directly, without "md" layer.

On the other hand, if the full-resync is always
done from this disk to the local mirror, there
would be no problem, except time.

The reason to do this kind of backup is that this
disk is encrypted, so a "block device copy" will
keep the data encrypted, while a backup of the
mounted disk will not. Unless done to another
encrypted disk/partition, of course.

Clearly, any suggestion is still really appreciated!

Thanks again,

bye,

-- 

piergiorgio

  reply	other threads:[~2009-04-20 18:10 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-19 11:47 RAID without superblock Piergiorgio Sartor
2009-04-19 20:44 ` NeilBrown
2009-04-19 21:04   ` Piergiorgio Sartor
2009-04-19 21:57     ` Andrew Burgess
2009-04-20 18:10       ` Piergiorgio Sartor [this message]
2009-04-20 18:17         ` Christopher Chen
2009-04-19 23:33     ` John Robinson
2009-04-20  5:13     ` Tapani Tarvainen

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=20090420181045.GA4236@lazy.lzy \
    --to=piergiorgio.sartor@nexgo.de \
    --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).