From: "Linda A. Walsh" <lvm@tlinx.org>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: [linux-lvm] what use is virtualsize -- or how is it to be used?
Date: Thu, 07 Jul 2011 22:22:54 -0700 [thread overview]
Message-ID: <4E16942E.9070204@tlinx.org> (raw)
I just saw it in the man page, and first thing I tried was creating a
logical volume
by just giving a --virtualsize, arg -- thinking it would 'auto-extend
it' as needed.
Nep.
Next was looking on the net and seeing an example that gave it some
small size (-L 1G),
with a virtual size of 2G. So what is that supposed to do?
I just now thought to copy a bunch of files ( that differed from
yesterday to today) to a tmp
partition) but had it fail miserably when it REALLY failed upon reaching
the physical
limit -- not the virtual limit!)....
I was trying to use rsync to copy from a snap from yesturday of /home
that was mounted on
/ohome to 'home.diff' (the partition that I used 'virtual size' with,
... I gave it a real
size of 1G, and a virtual size of 1T.
Using rsync, I had --compare-dest=/ohome (where I mount yesturday's
snap) and copied
from /home to /home.diff (the virtual partition).... Well the diffs
were > 1G, so had
hoped /home.diff would expand to it's virtual size... Anyway, got I/O
errors, after I
ran out of space. Ok, so *that*'s not what virtual size is for...either!
Anyway, I unmounted the now 'corrupt' /home.diff, and tried to remove it...
Got all sorts of i/o errors using lvremove Home.diff. (-f didn't work
either).
Got it to remove with lvremove -f /dev/PV/Home.diff
That gave I/O errors too, but successfully completed...
So what's virtual size good for, anyway?
next reply other threads:[~2011-07-08 5:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-08 5:22 Linda A. Walsh [this message]
2011-07-08 23:17 ` [linux-lvm] what use is virtualsize -- or how is it to be used? adultsitesoftware@gmail.com
2011-07-09 0:51 ` Mike Snitzer
2011-07-10 17:30 ` Linda A. Walsh
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=4E16942E.9070204@tlinx.org \
--to=lvm@tlinx.org \
--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.