From: Molle Bestefich <molle.bestefich@gmail.com>
To: linux-lvm@redhat.com
Subject: [linux-lvm] Fwd: LVM snapshots: guess *that's* not how it's done
Date: Sat, 12 Nov 2005 07:37:39 +0000 [thread overview]
Message-ID: <62b0912f0511112337q7d94fe1ajd48941d8391af28d@mail.gmail.com> (raw)
In-Reply-To: <62b0912f0511110516gf83b91eta2098d137f456d51@mail.gmail.com>
Moderator requested 83kB of screenshots be scrapped. Now it is.
(It's still in this original mail in the dm-devel archives.
---------- Forwarded message ----------
From: Molle Bestefich <molle.bestefich@gmail.com>
Date: Fri, 11 Nov 2005 14:16:22 +0100
Subject: LVM snapshots: guess *that's* not how it's done
To: dm-devel@redhat.com, linux-lvm@redhat.com
Good day,
I just bought a shiny big new box.
Contemplating using Xen + dm snapshots + unionfs + nbd to do various
fun things with it.
Since Fedora Core 4 has a couple of those things already in the
distro, I went with that.
I did this:
1. Install Fedora Core 4
2. Create a snapshot of the root volume with lvcreate
Seems the snapshotting did not go after plan - see attached screenshot....
Is that a serious bug in device-mapper or lvm, or is it just me that's
doing something wrong?
After the lvcreate, nothing works. A couple things like 'df' does,
but otherwise there's dialogs complaining about missing ELF headers
and non-executable binary files no matter what I click or try to run.
This is the disk layout:
2x300GB SATA with 3 MD RAID1 partitions:
md0: 512MB ext3 --> /boot
md1: 8GB swap
md2: 250GB LVM --> VolGroup0
Dom0Vol: 20GB ext3 LV on VolGroup0
FC4_Install: 10GB snapshot LV of Dom0Vol
Both disks were burn-in tested twice before starting.
next parent reply other threads:[~2005-11-12 7:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <62b0912f0511110516gf83b91eta2098d137f456d51@mail.gmail.com>
2005-11-12 7:37 ` Molle Bestefich [this message]
2005-11-12 18:40 ` [linux-lvm] Re: LVM snapshots: guess *that's* not how it's done Molle Bestefich
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=62b0912f0511112337q7d94fe1ajd48941d8391af28d@mail.gmail.com \
--to=molle.bestefich@gmail.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).