From: Du <eduardo@minicom.com.br>
To: linux-lvm@redhat.com
Subject: [linux-lvm] A problem (probably conceptual) with snapshot
Date: Mon, 03 Jul 2006 16:19:08 -0300 [thread overview]
Message-ID: <44A96DAC.5090202@minicom.com.br> (raw)
Today I needed to install Oracle and some other things on my PC, but I
realize that it would be better to make a snapshot and then reboot Linux
with this snapshot mounted instead of root.
Ok, I did that and changed fstab to mount my snapRoot instead root,
ok...I saw with 'df' command that it worked.
And I've installed all what I wanted, some garbage too...by the way,
this snapRoot doesnt means nothing to me, just for testing. And then I
changed the fstab again to mount the root original. But after it, all
the changes I made on snapshot was made on my root LV too. And the
lvdisplay command shows something strange now, about these two LV's. The
output is:
--- Logical volume ---
LV Name /dev/dutcheVG/root
VG Name dutcheVG
LV UUID aAN6BH-GqW3-zhtr-KeIt-BW4m-qEyw-RypMit
LV Write Access read/write
LV snapshot status source of
/dev/dutcheVG/snap_root [INACTIVE]
LV Status available
# open 0
LV Size 9.27 GB
Current LE 2372
Segments 1
Allocation inherit
Read ahead sectors 0
Block device 254:5
--- Logical volume ---
LV Name /dev/dutcheVG/snap_root
VG Name dutcheVG
LV UUID cj2PD2-4OYX-eCzw-kG5y-r071-icK0-dq7FBr
LV Write Access read/write
LV snapshot status INACTIVE destination for /dev/dutcheVG/root
LV Status NOT available
LV Size 9.27 GB
Current LE 2372
COW-table size 2.00 GB
COW-table LE 512
Snapshot chunk size 8.00 KB
Segments 1
Allocation inherit
Read ahead sectors 0
I donno what is really happening, does anybody can explain me? Plz!!
Thanks in advance
next reply other threads:[~2006-07-03 19:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-03 19:19 Du [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-07-06 20:44 [linux-lvm] A problem (probably conceptual) with snapshot Du
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=44A96DAC.5090202@minicom.com.br \
--to=eduardo@minicom.com.br \
--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.