Linux LVM users
 help / color / mirror / Atom feed
From: Brian McCullough <bdmc@buadh-brath.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] Copying a raw disk image to LVM2
Date: Sat, 9 Jul 2016 16:25:03 -0400	[thread overview]
Message-ID: <20160709202503.GB5404@bdmcc-us.com> (raw)
In-Reply-To: <CAEmTpZGkbJQ9-j8k2rMqTw0JKiuAiOz4JvioK4H6keUJkO-BTw@mail.gmail.com>

On Sat, Jul 09, 2016 at 10:33:51PM +0500, ???????? ?????????????????? wrote:
> One note: `sync` does not syncs written data, since it affects only
> data, written through filesystem. You should use `dd ....
> conv=fdatasync` instead.

Thank you both.

This is essentially the answer that I got from the Xen group, as well,
so I went ahead and tried it.  No problems.


Brian

  reply	other threads:[~2016-07-09 20:25 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-08 15:52 [linux-lvm] Copying a raw disk image to LVM2 Brian McCullough
2016-07-09 12:23 ` Марк Коренберг
2016-07-09 17:00 ` Digimer
2016-07-09 17:33   ` Марк Коренберг
2016-07-09 20:25     ` Brian McCullough [this message]
2016-07-10 22:02     ` emmanuel segura
2016-07-11  7:32       ` Xen

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=20160709202503.GB5404@bdmcc-us.com \
    --to=bdmc@buadh-brath.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