From: Denny Schierz <linuxmail@4lin.net>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: [linux-lvm] Strange snapshots behavior in dev/<vg>/
Date: Sat, 17 Nov 2007 00:54:16 +0100 [thread overview]
Message-ID: <473E2DA8.6000502@4lin.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 4360 bytes --]
hi,
to manage backups from Xen DomUs, I create snapshots from every guest.
They're all running under Debian Etch. No problem at all, normally, but
... see yourself:
My script creates only snapshots and mounts them, nothing more.
-----
root@henrietta ~ # /usr/local/bin/snap-mount.sh
Logical volume "angelica-disk-snap" successfully removed
Logical volume "hitomi-disk-snap" successfully removed
Logical volume "rico-disk-snap" successfully removed
Logical volume "triela-disk-snap" successfully removed
Logical volume "zoe-disk-snap" successfully removed
Logical volume "angelica-disk-snap" created
/dev/neko/angelica-disk
Logical volume "hitomi-disk-snap" created
/dev/neko/hitomi-disk
Logical volume "rico-disk-snap" created
/dev/neko/rico-disk
Logical volume "triela-disk-snap" created
/dev/neko/triela-disk
Logical volume "zoe-disk-snap" created
/dev/neko/zoe-disk
root@henrietta ~ # ls /media/backup/angelica-disk/dev/neko/
hitomi-disk
----
So, first question, why i have the name from a different volume
(hitomi-disk) in the dev from angelica?
root@henrietta ~ # ls /media/backup/hitomi-disk/dev/neko
ls: /media/backup/hitomi-disk/dev/neko: Input/output error
Why i get here an error?
any suggestions?
root@henrietta ~ # uname -a
Linux henrietta 2.6.16.33-xen #1 SMP Mon Jan 8 14:39:02 GMT 2007 i686
GNU/Linux
root@henrietta ~ # dpkg -l | grep lvm
ii lvm-common 1.5.20 The Logical
Volume Manager for Linux (common
ii lvm2 2.02.06-4 The Linux
Logical Volume Manager
root@henrietta ~ # dpkg -l | grep udev
ii udev 0.105-4 /dev/ and
hotplug management daemo
LV display:
--- Logical volume ---
LV Name /dev/neko/hitomi-disk
VG Name neko
LV UUID Tes7KH-pnv5-IGNt-vdf5-yCni-wSTo-dBd8ul
LV Write Access read/write
LV snapshot status source of
/dev/neko/hitomi-disk-snap [active]
LV Status available
# open 1
LV Size 1.00 GB
Current LE 256
Segments 1
Allocation inherit
Read ahead sectors 0
Block device 253:2
--- Logical volume ---
LV Name /dev/neko/hitomi-disk-snap
VG Name neko
LV UUID DIeQ81-Oeao-j9gt-RoRL-4G5L-0xko-Z5W9vN
LV Write Access read/write
LV snapshot status active destination for /dev/neko/hitomi-disk
LV Status available
# open 1
LV Size 1.00 GB
Current LE 256
COW-table size 1.00 GB
COW-table LE 256
Allocated to snapshot 0.07%
Snapshot chunk size 8.00 KB
Segments 1
Allocation inherit
Read ahead sectors 0
Block device 253:25
--- Logical volume ---
LV Name /dev/neko/angelica-disk
VG Name neko
LV UUID 72Ibgz-WlBX-x0G2-6HlQ-MgB2-UOd2-n3aXSq
LV Write Access read/write
LV snapshot status source of
/dev/neko/angelica-disk-snap [active]
LV Status available
# open 1
LV Size 4.00 GB
Current LE 1024
Segments 1
Allocation inherit
Read ahead sectors 0
Block device 253:10
--- Logical volume ---
LV Name /dev/neko/angelica-disk-snap
VG Name neko
LV UUID fclDHb-U9Xb-wWQc-ptFH-jrNg-mNou-qzinbe
LV Write Access read/write
LV snapshot status active destination for /dev/neko/angelica-disk
LV Status available
# open 1
LV Size 4.00 GB
Current LE 1024
COW-table size 1.00 GB
COW-table LE 256
Allocated to snapshot 0.09%
Snapshot chunk size 8.00 KB
Segments 1
Allocation inherit
Read ahead sectors 0
Block device 253:21
cu denny
--
Stoppt den Überwachungswahn - Stoppt den Schäuble Katalog:
http://www.nopsis.de
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 252 bytes --]
next reply other threads:[~2007-11-16 23:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-16 23:54 Denny Schierz [this message]
2007-11-17 2:27 ` [linux-lvm] Strange snapshots behavior in dev/<vg>/ Stuart D. Gathman
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=473E2DA8.6000502@4lin.net \
--to=linuxmail@4lin.net \
--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.