From: jon+lvm@silicide.dk
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] [Q] LVM snapshot volume extendable?
Date: Sun Jan 12 07:09:04 2003 [thread overview]
Message-ID: <20030112130943.GA12078@gw.silicide.dk> (raw)
In-Reply-To: <010901c2ba33$d3e5daf0$0f00a8c0@COMPAQ>
On Sun, Jan 12, 2003 at 09:12:07PM +0900, Sean Oh wrote:
> Hi
>
> I am using LVM 1.0.6, kernel 2.4.20 and XFS (from linux-2.4-xfs CVS).
>
> My question is that is the snapshot volume extendable?
yes, just use lvextend.
> My environment is as follows:
>
> /dev/vg01/lv01 ---> XFS, 2G
> /dev/vg01/lv01_snap --> 256M, snapshot for /dev/vg01/lv01, mounted under
> /snap with ro,nouuid,usrquota,grpquota,noatime
>
> Now I have wrote a small shell scripts that if lv01_snap is more than 50%
> full, automatically increase the lv01_snap. But it seems to me that it does
> not work well..
I wrote one too, but rather than 50% used, i used XX MB free space.
> What I did in the shell scripts are 'lvextend -L+256M /dev/vg01/lv01_snap'
> with/without 'xfs_growfs /snap'.
you dont need to grow the filesystem on the snapshot.
> After umounting the /snap and trying to remount /snap, it complaints as
> below
you dont need to unmount it
A LVM snapshot works by allocating a new "PE table". This means.
(# is allocated, - is not, and | is the end)
LV: |-#################--##---#####-|
snapshot: |---|
so, you change something in the LV
LV: |-#############+###--##---#####-|
snapshot: |#--|
Only the block that is actualy changed is moved to the snapshot.
If you need alot of changes your snapshot should be big, if you dont
change alot, you can use a much smaller snapshot.
JonB
next prev parent reply other threads:[~2003-01-12 7:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-12 6:11 [linux-lvm] [Q] LVM snapshot volume extendable? Sean Oh
2003-01-12 7:09 ` Alasdair G Kergon
2003-01-12 7:09 ` jon+lvm [this message]
2003-01-12 7:29 ` Sean Oh
2003-01-12 11:16 ` jon+lvm
2003-01-12 22:37 ` Sean Oh
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=20030112130943.GA12078@gw.silicide.dk \
--to=jon+lvm@silicide.dk \
--cc=linux-lvm@sistina.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