From: Xen <list@xenhideout.nl>
To: linux-lvm@redhat.com
Subject: Re: [linux-lvm] creating DD copies of disks
Date: Sat, 17 Sep 2016 16:53:14 +0200 [thread overview]
Message-ID: <8ebe6d1f9dc01bf7bfa843d8dcf3a0b8@dds.nl> (raw)
In-Reply-To: <8340e33605f0a84b10ed1d626cfecfbe@dds.nl>
Xen schreef op 17-09-2016 16:16:
> I just won't be able to use the old system until I change it back.
> Time to test, isn't it.
Indeed both Linux and Windows have no issues with the new disk, I think.
I was making a backup onto a bigger-sized disk, but neither Windows nor
Linux have an issue with it. They just see the old partition table of
the old disk and are fine with that.
Now I only need to know if the Linux system will run with the new disk,
but I'm sure there won't be issues there now. The system is not actually
*on* that disk.
Call it a data disk for an SSD system.
So perhaps you can see why I would want to have the two disks loaded at
the same time:
- if they work, I can copy data even after the DD (perhaps, to make some
rsync copy as you indicate) but now I already have all the required
structures (partition tables...) without any work.
- I wasn't actually yet done with the old disk. This was also just
research. Better make a backup first before you finalize things. I want
to do more work on the "old" system before I finalize things. But having
a backup sitting there that I can use is a plus. Having to not be able
to use both disks at the same time is a huge detriment. It is also not
that hard now to change the system back but I still don't know how I can
manually change the UUIDs that a VG/LV references. It is a huge plus if
I can just exchange one PV with another at will.
next prev parent reply other threads:[~2016-09-17 14:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <368387847.156920.1474117496841.ref@mail.yahoo.com>
2016-09-17 13:04 ` [linux-lvm] creating DD copies of disks matthew patton
2016-09-17 14:16 ` Xen
2016-09-17 14:53 ` Xen [this message]
2016-09-17 15:18 ` Michael D. Setzer II
2016-09-17 15:40 ` Xen
2016-09-17 7:29 Xen
2016-09-17 13:49 ` Lars Ellenberg
2016-09-17 14:40 ` Xen
2016-09-17 18:02 ` Lars Ellenberg
2016-09-20 8:04 ` Zdenek Kabelac
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=8ebe6d1f9dc01bf7bfa843d8dcf3a0b8@dds.nl \
--to=list@xenhideout.nl \
--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 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.