linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Andrew Gideon <ag2827189@tagmall.com>
To: linux-lvm@redhat.com
Subject: Re: [linux-lvm] Q: LVM over RAID, or plain disks? A:"Yes" = best of both worlds?
Date: Tue, 30 Nov 2010 15:41:21 +0000 (UTC)	[thread overview]
Message-ID: <id35v0$32d$1@taco.int.tagonline.com> (raw)
In-Reply-To: AANLkTing5ApAXM2o0M+pxNvg01mHewNgGGBiUXM3aLzZ@mail.gmail.com

On Tue, 30 Nov 2010 14:34:05 +0700, hansbkk wrote:

> So here's a summary of steps, please confirm:
>   - create a snapshot of a given volume - create a new RAID1 mdN between
>   that and a physical partition (blank?) - let that get sync'd up -
>   break the RAID (fail the partition?), remove the drive - delete the
>   snapshot

I'm having some difficulty following this thread, so perhaps I've missed 
some other aspect to this.  But the above makes it seem like you simply 
wish to transport snapshots.  Why not use something as straightforward as 
dd for this rather than RAID1?  RAID1 tools (mdadm, drbd, etc.) have the 
benefit of keeping volumes in sync over time.  But the above process 
describes a synchronization over a single instant (the instant of the 
snapshot being taken).  So why bother with the extra work/capability/
complexity?

I'm also puzzled by something you wrote in your very first message on 
this thread: "the hard-linked filesystems on FILER-B require full 
filesystem cloning with block-level tools rather than file-level copying 
or sync'ing."  Why?  rsync -H handles cloning of hard links (though at a 
performance cost).

	- Andrew

  parent reply	other threads:[~2010-11-30 15:41 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <AANLkTimTYse7vnqZydc1Z5z60vNuQw3juj7J_W7+bQEm@mail.gmail.com>
2010-11-28 15:31 ` [linux-lvm] Q: LVM over RAID, or plain disks? A:"Yes" = best of both worlds? hansbkk
2010-11-29 16:27   ` Lars Ellenberg
2010-11-29 17:00     ` hansbkk
2010-11-29 18:57   ` Nataraj
2010-11-30  5:20     ` hansbkk
2010-11-30  7:14       ` Nataraj
2010-11-30  7:34         ` hansbkk
2010-11-30 13:13           ` Phil Turmel
2010-11-30 15:39             ` hansbkk
2010-11-30 16:56               ` Phil Turmel
2010-12-01  4:45                 ` hansbkk
2010-12-01 12:50                   ` Phil Turmel
2010-12-01 19:47                     ` hansbkk
2010-11-30 15:41           ` Andrew Gideon [this message]
2010-11-30 15:53             ` hansbkk
2010-11-30 15:54               ` hansbkk
     [not found] ` <2D.98.07087.690A2FC4@cdptpa-omtalb.mail.rr.com>
2010-11-29 11:01   ` [linux-lvm] " hansbkk
2010-11-29 15:29     ` Keld Jørn Simonsen

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='id35v0$32d$1@taco.int.tagonline.com' \
    --to=ag2827189@tagmall.com \
    --cc=linux-lvm@redhat.com \
    /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).